How each role in SRAM can use SRAM:
- Organisation admin: if an institution orders SRAM, SURF create an organisation in SRAM, and assign who within the institution is the admin for that organisation. This person can sign into SRAM, and configure some settings on organisational level.
- Organisation manager: larger organisations might want to allow more people within the organisation, like people in the research support department, to create collaborations, without giving them full organisation admin options. This is what the 'organisation manager' role is for.
- Unit manager: An organisation can have units, allowing an organisation admin to divide an organisation. Organisation managers can be assigned to only manage (e.g., approve requests for new collaborations) one or more of these organisation units, instead of the entire organisation. We call these Unit managers. Unit managers have the same powers as Organisation managers, scoped to their Units only.
- Collaboration admin: an institution that has ordered SRAM can start creating collaborations in SRAM, and invite the administrator of that collaboration. That admin can connect applicationss to the collaboration, invite members, create groups and assign members to groups and configure some settings on the collaboration level.
- Collaboration members: someone that accepts the invitation to become a member of a collaboration, needs to enroll in SRAM, after which they can use the applicationss connected to the collaboration.
- Applications admin: can view and, in the future, change to which organisations the applications is available, which collaborations have connected to the applications and, in the future, revoke permission from a collaboration in case permission is needed.
- Applications manager: can view all applications details and settings, approve or reject connection requests, and disconnect the applications from collaborations.