MEGA Administration : Administrator Guide : Managing Users : Managing Profiles and Business Roles : Profile Properties
   
Profile Properties
Creation of profiles enables definition of the same connection rights to a set of users:
• repository access rights
*See "Profile repository access rights".
• access rights restricted to certain products
*See "Products accessible on the license (Command Line)".
*If a user already has access rights restricted by the Command Line attribute on his/her Login (see "Viewing Login Characteristics"), the products accessible to this user are at the intersection of values of the Command Line attribute of the user login and profile.
• access rights to certain Web applications
• connection repository snapshot (available for a profile with repository reading access (example: HOPEX Explorer)
*See "Connection repository snapshot of the profile".
To manage profiles, see "Managing Profiles and Business Roles".
Name
The Name of a profile can comprise letters, figures and/or special characters.
Products accessible on the license (Command Line)
The Command Line field enables definition of products that can be accessed by users with the current profile.
Format of the command is:
/RW’<accessible Product A code>;<accessible Product B code>;<...>’
For example: You have licenses for products MEGA Process, MEGA Architecture: and other MEGA products. To authorize only MEGA Process and MEGA Architecture: modules to users that have this profile, enter: /RW’PRO;ARC’
*To determine the product code, see "Product Codes", page 384.
*If a user already has access rights restricted by the Command Line attribute on his/her Login (see "Viewing Login Characteristics"), the products accessible to this user are at the intersection of values of the Command Line attribute of the user login and profile.
 
 
 
Profile 1
Profile 2
 
Command
order
RW:/’Pro’
none
User A
RW:/’PRO;ARC’
user A has access to MEGA Process
user A has access to MEGA Process and MEGA Architecture:
User B
RW:/’PRO;ARC’
user B cannot access any product
user B has access to MEGA Architecture:
User C
none
user C has access to MEGA Process
user C can access all products
for which he/she has the license
(MEGA Process and MEGA Architecture:
Restrictions on products for users and profiles that have licenses for MEGA Process and MEGA Architecture:
Assignable
The Assignable attribute defines if the profile is assignable to a Login or not. Certain profiles are created to aggregate other profiles.
*This attribute enables filtering of profiles and improves visibility of profiles to be assigned.
*The default value is "No".
Administrator profile
Only the user whose current profile has the Administrator Profile attribute with value "Yes" can:
• grant administrator profile to another user.
• declare a profile as administrator.
That is, specify value "Yes" for the Administrator Profile attribute of any profile.
The default value of Administrator Profile is "No".
Profile status
The Profile Status attribute is used to define the profile as inactive if necessary.
_GUIName
The _GUIName attribute enables definition of the profile name display in the interface.
MetaPicture
The MetaPicture attribute enables customization of the icon representing the current profile.
Logins
The Logins frame lists all users connected to the current profile.
Profile repository access rights
At creation, a profile can access all repositories by default.
Profile user access rights to environment repositories can be restricted by the administrator. He can:
• authorize repository update (Read/Write)
• prohibit repository update (Read-only)
• prohibit repository access (Not accessible)
*If a user already has repository access rights restricted by those defined on his/her login, only the restricted access rights will be added to those defined on the profile.
*See "Defining Profile Repository Access Rights".
Connection repository snapshot of the profile
For a profile with reading access to the repository (example: Explorer Reader), the administrator can define a connection repository snapshot for users of the profile.
*See "Defining Connection Repository Snapshot for a Profile".