In most situations, a user is associated with an organisation and has exactly one of five default roles within the organisation. The five default roles are cumulative, i.e. a Theme Manager can do everything a Data Manager can do:
- User (US): A user who can log in to the system and does not have a specific role in an organisation. Can typically only read public resources.
- Data Manager (DM): A user who can log in to the system and is responsible for uploading and maintaining data sets.
- Theme Manager (TM): A user who can log in to the system and manage themes, schemas and transformation projects.
- Superuser (SU): A user who can log in to the system and is responsible for an organisation.
- Administrator (AD): A user who can log in to the system and access all system functionality and resources. The Administrator's access is not defined through his organisational role.
The structure of organisations is hierarchical. Each organisational structure has a root organisation, such as in this example:
- State A
- County A1
- Municipality A1a
- Municipality A1b
- County A2
- Municipality A2a
- Municipality A2b
- Municipality A2c
- County A1
Usually, a user has exactly one role inside an organisation. The user gets access to resources and functions of the system via privileges defined for the role. Some privileges depend on the hierarchical structure of the organisations of the logged in user and the owner of a resource.
Example: You belong to «County A1» with role «Superuser». As a «Superuser», you can see the data sets belonging to your organisation «County A1», and the data sets belonging to any suborganisations associated with your root organisation. You can create new user accounts and suborganisations for your organisation, or for any of its suborganisations. You can create as many levels of suborganisations as you need.
When you create a new user as an administrator, the system enforces association of the user with an organisation and a role.