Logging in as an administrator

Top  Previous  Next

If you are using remote access to manipulate shared resources or accounts other than your own, you will need to log in as an administrator.

 

Logging in as an administrator of your own user group: In this situation, the administrator may manipulate:
oUser accounts in this user group
oResources of users in this user group
oResources in the .shared account for this user group
oSpecial: If the logged in user is listed in the "config editor" section of the .configs account, the user will be able to manipulate resources in the .config account for this user group.
oSpecial: If the logged in user is listed in the "config editor" section of an inherited group's  .configs account, the user will be able to manipulate resources in the .config account for that inherited user group as well

 

Logging in as the administrator of a shared user group: This should never occur.  There should be no user logins for a shared user group.  In order to manipulate a shared user group, a user should be created in a group that inherits from that shared user group.  That user should be added to the config editor section of the shared user group's .config account.

 

Logging in as a master administrator.  This option is only available for clients with Crash Magic installed on their own servers.  Clients that are hosted at Pd' Programming will not have such an account.  When logged in as a master administrator, with the "group administrator" permission enabled, the logged in user will have access to all groups and user accounts and all of their resources.  Be careful with this functionality.  In general, this means of accessing the system should only be needed by an application that creates and manages multiple user groups on the system.  When only managing one user group, always log in to that user group.
Special note: It is possible to create a master user that does not have the group administrator permission enabled