The Administrator access comes with a Birdview PSA and is designed to give unrestricted access to all system features and areas, as well as allow you to add users and set up access levels for them. Other administrative powers include adding custom fields to projects, activities and other entities that use both canned and custom field (e.g. time entries), or editing available activity categories, statuses, etc.
Unlike all other access level, preset or created by you, Administrator has no place among a project member’s access level. This is done by leaving all project member-related permissions in this access levels undefined. In practice, when an Administrator-role user creates a new project s/he is automatically assigned a Project Manager access level. The following rule applies. As each access level has an unique ID#, the system assigns roles in their ascending order. So if you have two roles Project Manager 1 (ID=2) and Project Manager 2 (ID=23), the former will be used when processing a project member with the Administrator access level. Similarly, when a project member is assigned an access level on a project, Administrator is not up for selection.
