Roles are preconfigured templates that define in what way a user can manage the corpus. This encompasses access rights, rights to change the content of the nodes, and the right to pass on all of these privileges. Here is a list of the roles:

Archive Manager

The role of Archive Manager can be assigned to each user. 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:

A domain can only have one Domain Curator.

Domain Manager

A Domain Manager, like the Archive Manager, can appoint other Domain Managers. This is the only difference from a Domain Curator, which means that, like the him/her, a Domain Manager can (for a given domain) set and revoke reading rules, create users/groups and edit them.

Domain Editor

In contrast with the roles described above, a Domain Editor can add and/or remove corpus nodes and/or resources (again: for a specific domain). This right is closer related to LAMUS than to AMS itself. Therefore, one generally combines the role of Domain Editor with that of Domain Manager or Domain Curator. In this way one user can, at the same time, upload information in the corpus, change such information and, afterwards, set the access rights.

	Note
	The domain-based roles (curator, manager, editor) can only be accessed and set via the Node Authorization Management, as they are dependant on a certain domain. The Archive Manager role applies to the whole corpus and can be thus selected when creating or editing a user/group.