Subdivisions are only enabled for dedicated organisations and allow the grouping of users (submitters and moderators) within the organisation, for example according to their department, institute or faculty. This makes it possible to manage rights more finely in the repository and decide who must receive notifications.
Create a subdivision
- Open the administration interface
- Open Administration > Subdivisions
- Add one and save
Associate a user to a subdivision
- Edit the user
- Add the field Subdivision if it is not present
- Type the name of the corresponding subdivision
Permissions within a subdivision
A subdivision narrows what you may edit, not what you may read.
- A submitter only ever submits deposits in their own subdivision.
- A moderator or administrator without a subdivision is not restricted at all: every deposit and every document of the organisation.
- A moderator or administrator with a subdivision reads every document of the organisation, but only edits those carrying their own subdivision. Deposits are narrower still: they see their own, plus those of their subdivision.
A document or a deposit that carries no subdivision at all is out of reach of anyone who has one. Give a subdivision to a user and they immediately lose the right to edit everything that was catalogued before subdivisions existed.
See Users and roles for the permissions that do not depend on subdivisions.
Notifications for deposits
The notifications are sent:
- for deposits in a subdivision:
- to all moderators of the same subdivision
- to all administrators
- for deposits not in a subdivision:
- to all moderators without subdivision
- to all administrators
If it exists in the deposit, the subdivision is indicated in the e-mail object.
Delete a subdivision
- Open the administration interface
- Open Administration > Subdivisions
- Select one and delete it
A subdivision cannot be deleted while it is still assigned to a user, a document or a deposit. Detach it everywhere first.