This graphic illustrates a simple account and group setup. Click the links below for more information about each group.
| • | Admin group 1 was created by CitySprint with at least one client-based administrator. Admin group 1 has access to all the consol codes and accounts in the client and access to all menus for all accounts: (all), and . Only CitySprint's system administrator has permissions to do add more people to this group. |
| • | Anyone in Admin group 1 can create more admin or user groups, associate them with any of the accounts/consol codes in the client and pass on any of Admin group 1's settings to each group. |
| • | A member of Admin group 1 created Admin Group 2 and User Group A; therefore, anyone in Admin group 1 can access the settings and modify either group. User Group X and User Group Z User Group A |
| • | Members of Admin group 1 can use any of the accounts in the client to make bookings. |
| • | Members of Admin group 1 can view a list of individuals who are assigned to User Group X and User Group Z through the menu but cannot modify these groups in any way. |
|
| • | Admin Group 2 was created by a member of Admin group 1; therefore the group and its members continue to be administered by Admin group 1. Anyone in Admin group 1 can access the settings and modify Admin Group 2. |
| • | Admin Group 2 could have been given an exact copy of Admin group 1's privileges. But in this scenario, it has received a subset of Admin group 1's privileges, access to all the screens ( (all), and and admin privileges for three accounts: 1B, 2B and 3B. |
| • | A member of Admin Group 2 created User Group X and User Group Z; therefore anyone in Admin Group 2 can modify these user groups. |
| • | Anyone in Admin Group 2 can create more admin and/or user groups, associate them with any/all of accounts 1B, 2B or 3B and pass on any of Admin Group 2's own settings to each group. |
| • | Members of Admin Group 2 not only administer but can also use accounts 1B, 2B and 3B to make bookings. |
| • | Members of Admin Group 2 can view a list of individuals who are assigned to User Group A through the menu, but cannot modify the group in any way. |
|
| • | User Group A was created by a member of Admin group 1; therefore the group and its members continue to be administered by Admin group 1. Anyone in Admin group 1 can access the settings and modify User Group A. |
| • | User Group A has inherited a subset of Admin group 1 permissions, such as access to the (all),andscreens. |
| • | By definition, user groups do not have admin privileges and cannot create/access/manage other users or groups. |
| • | Members of Admin Group 2 can view a list of individuals who are assigned to User Group A through the menu, but cannot modify the group in any way. |
|
| • | User Group X and User Group Z were created by members of Admin Group 2. These groups and their members continue to be administered by Admin Group 2. Anyone in Admin Group 2 can access and modify these user groups. |
| • | User Group X and User Group Z have inherited a subset of Admin Group 2 permissions, such as access to the (all),andscreens. Each user group has access to a subset of accounts in Consol Code B. |
| • | By definition, user groups do not have admin privileges and cannot create/access/manage other users or groups. |
| • | Members of Admin group 1 can view a list of individuals who are assigned to User Group X and User Group Z through the menu but cannot modify these groups in any way. |
|
Note:
| • | A user/admin ID can only be assigned to one group at a time. |
| • | Accounts may be associated with one or more groups. |
| • | Administrators cannot add more people to their own group (the group to which they themselves belong). |
Related topics
