...
New permissions under the permission lists OU will be created by the CMs. In the description field of each permission the CMs will include short description, owner and Remedy ticket number for the request. CMs will also add teams or roles to these permissions. Permissions are for internal IS support, not for external access to IS developed products (see products).
...
Under products, CMs will be responsible for creating new Product directories and assigning the Admin Group for the new directory. The Admin group will be able to create new folders and permissions within the directory for which they are Admin. They will also be able to associate teams and roles to the permissions under their directories. Each Product directory will have an Admin group (role or team see below). The naming convention for products is slightly different than the other IS OUs. Because maintenance of products could move between CIT organizations, the IS portion of the name is removed in product permissions (see below).
Examples of Product Directories:
- Cit-is-products-Hosting
- Cit-is-products-hosting-perm1
- Cit-is-products-hosting-perm2
- Cit-is-products-PeopleSoft
- Cit-products-PeopleSoft-perm1
- Cit-products-Peoplesoft-perm2
- Cit-is-products-Launchpad
- Cit-is-products-Uportal
- Cit-is-products-Hosting
Teams and Roles are both groups of people. Both OUs will have an OU Admin group of IS Supervisors. This will allow all IS Supervisors to add and remove users from Teams and Roles.
...