People and access reference¶
Look up the marks on a person's projects, who may name whom, and what the roles of your own can and cannot carry.
Marks beside a person's projects¶
Each project listed in See who can do what carries one mark.
| Mark | Means |
|---|---|
| Lead | They lead the project |
| Direct role | A role they hold themselves: on the project, its branch or the whole organisation |
| Via team | A team or branch they are on gives them the role |
Who names whom¶
- The owner holds every administration authority and is never named to one.
- An access administrator names branch access administrators and approves sensitive changes with the owner. A branch access administrator manages who works in one branch.
- An access administrator may also give branch roles, up to Branch manager, in every branch; a branch access administrator in their branch. Neither may give anyone a role across the organisation.
- From your former plan lists each person your former plan let act as an administrator, auditors included. Check each person's own role, then select End role on this one.
Roles of your own¶
- A team or a branch cannot hold a role that lets people manage access, share or deliver. A role a team or a branch holds is counted beside the people on the roles list, for example 2 people and 1 team or branch.
- When a change would add such a power to a role a team or branch holds, the summary says so before you save, for example 1 team role will stop working: …. Those roles stop working when the change is saved.
- A role you define never carries the owner's own acts, administering access or anything reserved to GISweaver's staff.
- On the People tab you can end a role, see What someone can do today or as of an earlier day, and download the assignments, the matrix and the policies under Export.
- Compare shows two roles side by side; See every role side by side shows every role against every permission.