You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/onboarding.qmd
+24-5Lines changed: 24 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -112,21 +112,40 @@ Perform step 1 and 2 below
112
112
Perform step 1, 2(optional), and 3
113
113
:::
114
114
115
+
::: {.callout-tip}
116
+
## Security Best Practice
117
+
118
+
Only grant collaborators the permissions they need. Set an expiration date for memberships when inviting people to your collaboration. See our [tips for secure collaboration](responsible-use.qmd#collaboration-and-access-management) for more guidance.
119
+
:::
115
120
116
121
### 1. Invite a new collaborator
117
-
SRAM is used for access management for SURF Research Cloud. It is possible to [invite collaborators to your collaboration (project)](https://servicedesk.surf.nl/wiki/display/IAM/Invite+admins+and+members+to+a+collaboration)
122
+
SURF Research Cloud uses SRAM to control who can access your project's workspaces and resources.
123
+
124
+
Before someone can use workspaces in your collaboration, they must first be invited and accept the membership. Once they accept, they can log in to running workspaces but by default they cannot create, pause, or delete workspaces until you grant additional permissions. Inviting collaborators through SRAM ensures secure, traceable access management and lets you control exactly what each team member can do.
125
+
126
+
See this guide to [invite collaborators to your collaboration (project).](https://servicedesk.surf.nl/wiki/display/IAM/Invite+admins+and+members+to+a+collaboration)
118
127
119
128
::: {.callout-note collapse="true"}
120
129
## Who can I invite?
121
130
122
131
It is possible to invite anyone who has an email address to join your project. Students and employees from most Universities (and Universities of Applied Sciences) will be able to login to SRAM using their institution credentials. Collaborators from abroad or e.g. private sector can create an [eduID](https://eduid.nl/) first and then use that to login to SRAM and accept the invitation.
123
132
:::
124
133
125
-
### 2. Workspace admins
126
-
In SRAM there are [groups](https://servicedesk.surf.nl/wiki/display/IAM/Manage+groups+of+collaboration+members) that can be used to grant members of your collaboration to the right to [pause, resume and delete workspaces](https://servicedesk.surf.nl/wiki/display/WIKI/Sharing+control%3A+workspace+admin)
134
+
### 2. Grant Workspace Admins Rights
135
+
By default, only the person who creates a workspace can pause, resume, or delete it. This can be limiting when working in teams.
136
+
137
+
SRAM groups solve this by allowing you to share workspace management rights with other team members. By adding collaborators to the `src_ws_admin` group, you give them control over the workspaces in your collaboration without giving them access to the project budget. This is useful when multiple team members need to manage workspaces but shouldn't be able to create new resources or spend credits.
138
+
139
+
Follow the guides on how to [create and manage groups](https://servicedesk.surf.nl/wiki/display/IAM/Manage+groups+of+collaboration+members) and how to grant members of your collaboration the right to [pause, resume and delete workspaces](https://servicedesk.surf.nl/wiki/display/WIKI/Sharing+control%3A+workspace+admin)
140
+
141
+
### 3. Grant Wallet Access
142
+
By default, only collaboration admins can create new workspaces. This can slow down research when team members need to provision their own resources.
143
+
144
+
SRAM groups enable you to delegate workspace creation rights. By adding collaborators to the `src_co_wallet` group, you give them permission to create workspaces and storage volumes using the project's shared budget.
145
+
146
+
This is beneficial for collaborative research where multiple team members need autonomy to start their own workspaces, but should only be granted to trusted members since they'll be able to spend project credits.
127
147
128
-
### 3. Share your wallet
129
-
In SRAM there are [groups](https://servicedesk.surf.nl/wiki/display/IAM/Manage+groups+of+collaboration+members) that can be used to grant members of your collaboration to the right to [create new workspaces using the wallet of your project](https://servicedesk.surf.nl/wiki/display/WIKI/Access+to+project+wallet)
148
+
Follow the guides on how to [create and manage groups](https://servicedesk.surf.nl/wiki/display/IAM/Manage+groups+of+collaboration+members) and how to grant members of your collaboration the right to [create new workspaces using the wallet of your project](https://servicedesk.surf.nl/wiki/display/WIKI/Access+to+project+wallet)
130
149
131
150
## Next
132
151
When your collaboration and wallet is ready, see this page for [first steps](first-steps.qmd).
Copy file name to clipboardExpand all lines: docs/responsible-use.qmd
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -257,6 +257,17 @@ For cases where data is so sensitive that only a data manager or an external dat
257
257
258
258
There is also a variant of SANE in which the researcher is required to interact with the data 'blindly'.
259
259
260
+
## Collaboration and Access Management
261
+
262
+
When working with collaborators on Research Cloud, follow the principle of least privilege to maintain security:
263
+
264
+
-**Grant minimal permissions**: Only give collaborators the specific permissions they need for their role (see [Adding Collaborators](onboarding.qmd#add-collaborators-to-existing-project) for permission levels)
265
+
-**Set expiration dates**: Add an end date to memberships in SRAM when inviting collaborators. This ensures access automatically expires when people leave the project
266
+
-**Review access regularly**: Periodically review who has access to your collaboration in SRAM and remove members who no longer need access
267
+
-**Use groups wisely**: Use [SRAM groups](https://servicedesk.surf.nl/wiki/display/IAM/Manage+groups+of+collaboration+members) to organize permissions - don't give everyone full admin rights unless required.
268
+
269
+
Following these practices minimizes the risk of unauthorized access to your data and helps maintain compliance with data protection requirements.
270
+
260
271
## Security incidents
261
272
If you believe there has been (suspected) misuse or unauthorized use of login details and / or VRE, please report this to [CERT](https://www.uu.nl/en/organisation/information-and-technology-services-its/computer-emergency-response-team-cert-uu) or send an email to its.ris@uu.nl and "pause" your VRE using the SURF Research Cloud portal.
0 commit comments