There are four key elements for managing users in 
      
SBM:
      
    
 
      - Roles 
        
A role is a set of application-related privileges. Roles are defined
          in 
          SBM Composer,
          and users and groups are assigned to roles in 
          SBM Application Administrator.
          For details, refer to 
          About Roles.
 
       
 
      - Groups 
        
A group is a set of users, to which you can assign roles, additional
          privileges, an initial set of preferences, and notification subscriptions. For
          details, refer to 
          About Group Accounts.
 
       
 
      - Users 
        
Each user must have an individual account that at a minimum includes
          a unique login ID, a user name, and a product-access level. You can then assign
          users to groups so they can inherit role assignments, privileges, and
          notification subscriptions. For details, refer to 
          About User Accounts.
 
       
 
      - Administrators 
        
You can have multiple administrators, each with varying amounts of
          responsibility and access. For details, refer to 
          Managing Administrators.
 
       
 
    
 
 
    To effectively manage user accounts, follow these basic steps.
 
     
      - In 
        SBM Composer,
        create roles for your applications to organize sets of privileges, and then: 
        
 
          - Assign appropriate application-related privileges to each role. 
          
 
 
          - Assign roles as values for 
            User, 
            Multi-User, and 
            Multi-Group fields in tables located in the 
            Data Design area. 
          
 
 
          - Assign primary and secondary owners to states in your workflows. 
          
 
 
          - Deploy your process app to make the roles available in 
            Application Administrator.
            
          
 
 
        
 
        For details on these steps, refer to the 
          SBM Composer Guide.
 
       
 
      - In 
        Application Administrator,
        create groups to organize sets of users, and then: 
        
 
          - Assign an appropriate product-access level to each group. This
            impacts which users can be members of the group, as well as which privileges
            apply to the group. For details, refer to 
            Product-Access Types. 
          
 
 
          - Assign roles to each group. 
          
 
 
          - Assign any non-application-related privileges to the group, such
            as the ability to modify user profile settings, and for administrators, the
            ability to perform configuration and administration tasks. 
          
 
 
          - Set an initial set of preferences and settings to members of the
            group. 
          
 
 
          - Subscribe the group to notifications. 
          
 
 
        
 
        For details on these steps, refer to 
          Working With Groups.
 
       
 
      - Use one of the methods described in 
        About User Accounts to
        establish user accounts for your system. If you choose to manually create user
        accounts, edit multiple user accounts in 
        Application Administrator,
        and then: 
        
 
          - Assign a product-access level based on the groups to which you
            will assign the users. 
          
 
 
          - Assign users to applicable groups. They will inherit their role
            assignments, notification subscriptions, and additional privileges from these
            groups. 
          
 
 
          - Modify password settings for the users, if applicable. 
          
 
 
        
 
       
 
      - Optionally, set default values for 
        User, 
        Multi-User, and 
        Multi-Group fields in workflows or projects in 
        Application Administrator.
        Possible values are determined by the roles assigned to the field in 
        SBM Composer,
        and the users and groups assigned to the roles in 
        Application Administrator.
        
      
 
 
    
 
   
 
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.