1.1.4. Roles
Roles are predefined templates that define in what way a user can use the corpus. This encompasses access rights, rights to change the content and the right to pass on all of these privileges. The following roles exist:
Archive Managers
To each user the role of Archive Manager can be assigned. This means that all possible rights are granted to this user such as accessing all resources and changing access rules. An archive manager can in turn appoint other archive managers. It goes without saying that this possibility should be used with care. It is the only role that is not bound to a domain.
Domain Curator
A domain curator:
is bound to a domain (i.e. has power over a node and its descendants).
can set and revoke rules on all of the nodes within that domain.
can create, remove and alter users and groups. Altering and removing only works for users/groups created by the domain curator.
can delegate his/her rights (except this delegation right itself) to a Domain Manager.
A domain can only have one Domain Curator.
Domain Manager
A Domain Manager cannot assign other domain managers. This is the only difference with a domain curator. So a domain manager can (for a given domain) set and revoke read rules, create and change those self-created users/groups.
Domain Editor
In contrast with the roles above a Domain Editor can add and remove corpus nodes and resources (again: for a specific domain). This right is closer related to LAMUS than AMS itself. Therefore one generally combines the Domain Editor role with that of Domain Manager or Curator. That way one user can both upload and change information in the corpus and set the access read rights afterwards.
![]() | Note |
|---|---|
The domain-based roles (curator, manager, editor) can only be accessed and set via the Node Authorization Management as these are dependant on a certain domain. The Archive Manager role applies to the whole corpus and thus can be selected when creating or editing a user/group. |
![[Note]](images/note.png)