Creating Custom Project Roles
- Mojib Javadi
- Jonathan Gane
If the default project roles - Project Administrator, Project Collaborator, and Project Contributor (described in Understanding Project Roles) - do not fit the desired Project user access requirements or if users require access to Shared Folders in the Green Room or Core, Project Administrators can create custom project roles.
To create a custom role:
Navigate to the Project Members page and open the Roles & Permissions tab.
Click + New Role.
Enter a role name and optional description.
Click to select the checkboxes for each desired custom permission level corresponding to the desired folder location(s) listed in the left-most column in the Green Room and Core (See the table below for a description of the different permission levels).
Available folder locations include:A user’s own folder (created for every member when they are added to the Project).
All user folders within the zone.
Shared Folders (see Managing User and Shared Folders in a Project).
Under the Workspace Tools heading, toggle switches to Accessible status to give the new custom role permission to access JupyterHub and/or Guacamole (default setting is Inaccessible).
Review the selected permissions to ensure all dependencies and selections are accurate.
Click Save.
The saved role is now available for assignment to Project members (see https://indocconsortium.atlassian.net/wiki/spaces/JSDNXT/pages/4317710037).
Project Administrators can choose any combination of permissions in the Green Room or Core user folders and Shared Folders when defining a custom role. The following table describes the available permission levels and dependencies:
Activity | Description and dependencies |
|---|---|
View | View items in accessible folders within a zone. |
Upload | Upload items, from local or from a Workspace, to accessible folders within a zone (requires View permission). |
Edit | Create, move, rename, and annotate accessible items within a zone (requires View permission in source and destination and Upload permission in destination). |
Download | Download accessible items from a zone to a Workspace or to a client-side application (requires View permission). |
Trash Bin | Use a personal Trash Bin. Items in the Trash Bin will be retained for 30 days then automatically deleted from the platform. Users may recover or permanently delete items from the Trash Bin before the retention period expires (requires View permission to send items to Trash Bin and Upload permission in at least one destination to recover items)..) |
Copy-to-Core | Copy accessible items to an accessible destination in the Core zone (requires at least one folder accessible in Core). |
Request Copy-to-Core (Green Room only) | Request that accessible items be copied to an accessible destination in the Core zone by someone with the Copy-to-Core permission level (requires at least one folder accessible in Core). |
Workspace Tool | Description |
|---|---|
JupyterHub | A multi-user version of Jupyter Notebook that provides access to custom and pre-configured data science computational environments for your Project. |
Guacamole | A built-in remote desktop gateway for accessing Project Virtual Machines and facilitating workspace analyses. |