This article explains how to view your project's permissions policy. Rhino FCP's permissions are finely-grained, and indicate which roles can perform which actions in the project. For example, the permission policy might indicate that only the site administrator can manage datasets.
To view the permissions policy, complete the following steps.
- Select Collaborators from the menu in the upper left part of the window.
- The information for the Collaborators link (tab) appears by default. To see the permission policy information, select the Permission Policy link, which appears below the Collaborators heading.
- The Permissions Policy page shows a list of permission levels, actions, and personas that are signed to each action.
NOTE: This page is currently read-only. Project Permissions Policy must be defined while creating a new Project. Please refer to Specifying a Project's Permissions Policy for more information about defining project permissions when creating a project.
Let's take a deeper look at the items on this page.
Permission Levels
Permissions can be applied to a project (see the top half of the page) or the entire site (see the bottom half of the page).
Privacy Parameters
Privacy parameters show the differential privacy setting and the K-Anonymization Parameter.
Personas
User Personas define a set of predefined privileges and access rights that are assigned to a particular category of users within the Rhino FCP. These roles streamline permission management by grouping users based on their responsibilities, ensuring that each user has appropriate access levels to perform their tasks while maintaining security and data integrity.
| Persona | Description |
| PLA - Project Lead, Admin | The workgroup admin for the workgroup that created the project |
| PLM - Project Lead, Member | Every non-admin member of the workgroup that created the project |
| MA - My site, Admin | The workgroup admin for your workgroup (relevant only to site-level permissions) |
| MM - My site, Member | Every non-admin member from your workgroup (relevant only to site-level permissions) |
| CA - Collaborator, Admin | The workgroup admin for a workgroup that has been invited to collaborate on a project |
| CM - Collaborator, Member | Every non-admin member of a workgroup that has been invited to collaborate on a project |
Actions
Actions are things that people who have certain roles can do. In the following example, the PLA and PLM roles can manage code objects, code runs, data schemas, and also run code.
For the Actions, hover over the ⓘ icon for more information about exactly what each action means.
Project-level Permissions
Project-level permissions define who has the ability to perform certain actions within the Project. The Project Lead can enable and limit access to certain functions for specific personas in the Project. Actions included under the Project-level Permissions Policy are:
| Action | Description | Default Policy |
| Differential Privacy Setting (None, Low, Medium, High) |
(Privacy filter) - Control the level of noise (if any) is added to data when calculating metrics:
|
Medium |
| K-Anonymization Parameter | (Privacy filter) - Subgroups smaller than K will be excluded from summary statistics | 5 |
| Manage Code Objects | Create, modify, and remove Code Objects in the project | PLA, PLM |
| Manage Code Runs | Modify and remove Code Runs associated with this site, as well as download model weights created as part of this project | PLA, PLM |
| Manage Data Schemas | Create, modify, and remove Data Schemas in the project | CA, CM, PLA, PLM |
| Run Code | Run code in the project | PLA, PLM |
Site-level Permissions
Site-level permissions define what project participants may do with your site's resources. When the Project Lead creates the project, they also set the Site-level permissions for their site. Each invited Collaborator will be presented with the Site-level Permissions Policy suggested by the Project Lead, but they may also change their Site-level permissions policy before accepting the invitation. Actions included under the Project-level Permissions Policy are:
| Actions | Description | Default Policy |
| Manage This Site's Datasets | Import, export, modify, and remove Datasets associated with this site | MA, MM |
| Manage Secure Access Lists | Create, modify, and remove Secure Access Lists for Datasets from this site | MA, MM |
| Manage This Site's Code Runs | Modify and remove Code Runs associated with this site | MA, MM |
| Pre-approved Code Only | Only allow pre-approved code to be run on your site's data. You will be able to specify/update the pre-approved code on this page |
No |
| Run Code On This Site | Run code on Datasets from this site | MA, MM, PLA, PLM |
| Share Secure Access Lists | Share Secure Access Lists for Datasets from this site | MA, MM |
| View Client-Side Logs | View logs from code run on Datasets from this site | MA, MM, PLA, PLM |
| View Dataset Analytics | View aggregated analytics and metrics for Datasets from this site | MA, MM, PLA, PLM |
| View Datasets via Secure Access | Access data from this site via zero-footprint viewers (e.g. tabular data viewer, and interactive containers, OHIF) | MA, MM |