Difference between revisions of "Assign Security Classifications to Organization Roles"
(New page: == Assigning Security Groups to Organization Roles == Assigning security to roles rather than individual users will make it easier to create and update security settings. A consistent nam...) |
|||
| Line 1: | Line 1: | ||
| − | == Assigning Security Groups to Organization Roles == | + | ==Assigning Security Groups to Organization Roles== |
| + | ===Concepts=== | ||
| − | Assigning security to roles rather than individual users will make it easier to create and update security settings. | + | '''Security Classifications''' can be used to grant the same security to a group of users such as all users with the same role. Assigning security to roles rather than individual users will make it easier to create and update security settings. The consultant and client should work together to define the roles within the organization taking care not to combine roles. Security classifications can then be created for each role. |
| − | + | '''Security Gates''' are at the organizational level and simply control whether a function can be resticted or not. | |
| + | |||
| + | '''Security Codes''' can be assigned to a user or classification and allow users with that classification to pass through the corresponding security gate. | ||
| + | |||
| + | For example if the gate <printchart> is <on>, only users assigned the corresponding security code can <print charts>. If the gate is off than all users can <print charts>. | ||
| + | |||
| + | |||
| + | ===High Level Process:=== | ||
| + | # Define organization roles | ||
| + | # Decide which security gates will be turned on for the organization | ||
| + | # Create a security classification for each role | ||
| + | # Add appropriate security codes to the classification | ||
| + | # Turn on the security gates | ||
| + | |||
| + | ===Detailed Steps=== | ||
Revision as of 17:46, 30 April 2008
Assigning Security Groups to Organization Roles
Concepts
Security Classifications can be used to grant the same security to a group of users such as all users with the same role. Assigning security to roles rather than individual users will make it easier to create and update security settings. The consultant and client should work together to define the roles within the organization taking care not to combine roles. Security classifications can then be created for each role.
Security Gates are at the organizational level and simply control whether a function can be resticted or not.
Security Codes can be assigned to a user or classification and allow users with that classification to pass through the corresponding security gate.
For example if the gate <printchart> is <on>, only users assigned the corresponding security code can <print charts>. If the gate is off than all users can <print charts>.
High Level Process:
- Define organization roles
- Decide which security gates will be turned on for the organization
- Create a security classification for each role
- Add appropriate security codes to the classification
- Turn on the security gates