> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/projects/creating-a-new-project.md).

# Creating a New Project

In the Rhino Federated Computing Platform (FCP), a Project forms the core organizational unit that encapsulates a distinct data analysis or research initiative. To create a project, you'll need to ensure that you are logged into Rhino FCP, then enter the details of the project, including permissions.

## Prerequisites

Before you begin, complete the following.

* Ensure that you have a login for Rhino FCP.
* Optionally, review the site level and project level permission information (see the information later in this article) so that you'll know what to select when you create your project.

## Logging into Rhino FCP

To log into the Rhino FCP, navigate to the login page in your web browser. There are three ways to login to the FCP.

<figure><img src="/files/MY9kVE3cD4s41CsAKvBN" alt="" width="75%"><figcaption></figcaption></figure>

You can log into Rhino FCP using three different methods.

* To log in using a user name and password, enter the information in the login screen. If this is your first time logging into the platform, you will be required to change your password from the temporary one sent to you during onboarding.
* To log in using Google Single Sign-on (SSO), click the button and follow the prompts to log in with your Google credentials.
* To log in using Azure Single Sign-on (SSO), click the button and follow the prompts to log in with your Azure credentials.

{% hint style="info" %}
**If you have not received your credentials, are not prompted to change your password, or if you encounter other issues while attempting to login, please contact** [**support@rhinohealth.com**](mailto:support@rhinohealth.com)**.**
{% endhint %}

## Creating a New Project (Step-by-Step Instruction)

To create a new project, complete the following:

{% stepper %}
{% step %}

### Select Projects

Select **Projects** on the left side of the screen to open the Projects screen.

![](/files/d8f733fcad557f75e3a55b1c9fdaa07c40aa3bb0)
{% endstep %}

{% step %}

### Open the Create a New Project screen

Select the **Add New Project** button in the upper right corner of the screen to open the **Create a New Project** screen.

![](/files/8f46b9fb99c140d8306636fecf091601220d9aa7)
{% endstep %}

{% step %}

### Add project details

Add a name and a description.
{% endstep %}

{% step %}

### Expand Permissions Policy

Select **Permissions Policy** to expand the screen.

![](/files/83fc65f2641a21252c817ddd56f4fdc837d1961a)
{% endstep %}

{% step %}

### Configure permissions

Project leads configure permissions during project creation. There are two levels of project permissions:

* **Project-level permissions:** These are privacy settings and permissions configured at the project level for all participants. Rhino configures default project-level permissions, but the project lead can modify them.

Select the following expandable box to see project-level permission policy definitions.

<details>

<summary><strong>Project-Level Permission Definitions</strong></summary>

<table><thead><tr><th>Action</th><th width="223.66796875">Description</th><th>Default Policy</th></tr></thead><tbody><tr><td>Differential Privacy Setting</td><td>(Privacy filter) - Control the level of noise (if any) is added to data when calculating metrics:<br>- <strong>None</strong>: Noise is never added.<br>- <strong>Low</strong>: Noise is only added when calculating percentiles.<br>- <strong>Medium</strong>: Noise is added for percentiles and other standard metrics when the number of unique values is small.<br>- <strong>High</strong>: Noise is always added when calculating metrics.</td><td>Medium</td></tr><tr><td>K-Anonymization Parameter</td><td>(Privacy filter) - Subgroups smaller than K will be excluded from summary statistics</td><td>5</td></tr><tr><td>Download Model Parameters</td><td>Download model parameters for models trained as part of the project.</td><td>PLA, PLM</td></tr><tr><td>Hide Collaborators</td><td>Indicates whether to allow collaborators in this project to view information (e.g. names, activities) about other collaborators. Selecting No allows the collaborators to see each other's information. Selecting Yes, hides collaborator information from other collaborators, including what would be shown in the recent activities list, notifications, and the list of collaborators in the project. Note that if you hide collaborators, and you set other permissions to include CA and/or CM, you will see a message indicating that CA/CM cannot be used in permissions when the project is set to use hidden collaborators.</td><td>No</td></tr><tr><td>Manage Code Objects</td><td>Create, modify, and remove Code Objects.</td><td>PLA, PLM</td></tr><tr><td>Manage Code Runs</td><td>Modify and remove Code Runs associated with this site.</td><td>PLA, PLM</td></tr><tr><td>Manage Data Schemas</td><td>Create, modify, and remove Data Schemas in the project.</td><td>CA, CM, PLA, PLM</td></tr><tr><td>Require Confidential Computing</td><td>Setting this permission to Yes allows your code to run on a Rhino Client within a Trusted Execution Environment(s) (TEEs). For the list of supported confidential computing VMs, see <a href="/spaces/ydySyCBmy6F7NnGn4bPa/pages/bc39a5520032e20abb22dbf254538d042e76e1b9">Confidential Computing Supported Environments and Permission Settings</a>.</td><td>No</td></tr><tr><td>Run Code</td><td>Run code in the project.</td><td>PLA, PLM</td></tr></tbody></table>

</details>

* **Site-level permissions:** These permissions are configured at the site level and can be reviewed and adjusted by each collaborator. Site-level permissions require approval before a collaborator can join the project. Project leads and other authorized personnel can create templates for site-level permissions.

  \
  Templates streamline the process of customizing site-level permissions. For example, a site might want to enforce k-anonymization with a k-parameter of 100. Including this setting in a template ensures consistency across new projects. You will know if you have templates available if an option for templates appears on the screen.&#x20;

  * If the expanded **Create a New Project** screen does not display template options, the default template is available, and you can modify project-level and site-level permission policies as needed.
  * If the expanded **Create a New Project** screen does display template options, select the desired permission policy template. The default template is displayed.

Select the following expandable boxes to see site-level permission policy definitions and notes.

<details>

<summary><strong>Site-Level Permission Definitions</strong></summary>

<table><thead><tr><th>Actions</th><th width="227.8046875">Description</th><th>Default Policy</th></tr></thead><tbody><tr><td>Manage This Site's Datasets</td><td>Import, export, modify, and remove Datasets associated with this site</td><td>MA, MM</td></tr><tr><td>Manage Data Mappings</td><td>Create, modify, and remove data mappings and vocabularies from this site.</td><td>PLA, PLM, MA, MM</td></tr><tr><td>Manage Secure Access Lists</td><td>Create, modify, and remove Secure Access Lists for Datasets from this site</td><td>MA, MM</td></tr><tr><td>Manage This Site's Code Runs</td><td>Modify and remove Code Runs associated with this site</td><td>MA, MM</td></tr><tr><td>Pre-approved Code Only</td><td>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</td><td>No</td></tr><tr><td>Run Code On This Site</td><td>Run code on Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>Share Secure Access Lists</td><td>Share Secure Access Lists for Datasets from this site</td><td>MA, MM</td></tr><tr><td>View Client-Side Logs</td><td>View logs from code run on Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>View Code Objects and Code Runs</td><td>Determines who can view workgroup code objects and code runs. Users without this permission only see code objects and code runs published to all project participants. See note below this table for more details.</td><td>CA, CM, MA, MM, PLA, PLM</td></tr><tr><td>View Datasets and Data Schemas</td><td>Allows you to view all workgroup Datasets and Data Schemas. Anyone without these permissions will only be able to view Datasets and Data Schemas that have been published to all project participants.</td><td>CA, CM, MA, MM, PLA, PLM</td></tr><tr><td>View Dataset Analytics</td><td>View aggregated analytics and metrics for Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>View Datasets via Secure Access</td><td>Access data from this site via zero-footprint viewers (e.g. tabular data viewer, and interactive containers, OHIF)</td><td>MA, MM</td></tr><tr><td>View Client Side Logs with Sensitive Data</td><td>View logs from code runs on sensitive datasets from this site. This is included because code runs could write sensitive data to logs.</td><td>MA, MM</td></tr><tr><td>View Sensitive Datasets via Secure Access</td><td>Access sensitive data from this site via zero-footprint viewers such as a tabular data viewer and OHIF or interactive containers. This also includes fields marked as 'local only'.</td><td>MA, MM</td></tr></tbody></table>

</details>

<details>

<summary><strong>Site-Level Permission Definitions Notes</strong></summary>

{% hint style="info" %}
NOTE: If the personas for the View Code Objects and Code Runs setting are the default (PLA, PLM, MA, MM, CA, CM), then all members of the workgroup can see code objects and code runs. If you initially remove personas from the list, all code object and run versions will start as unpublished and are only visible to the included personas. Code runs are only visible to users who can see the code object.

You can change personas as you would for any other permissions setting. The personas in the permission list must include an MA or MM persona so site members can view and publish their own objects and runs.

The workgroup of the code object is the primary workgroup of the person who created the code object.

The workgroup of the code run is the primary workgroup of the person who triggered the code run.

Note: Code Runs are only visible to users for whom the Code Object is also visible. One edge case in which this might not automatically happen, is when there is an unpublished Code Object created by Collaborator A, with “View Code Object/Run” permissions set to PLA, PLM, MA, MM (so without CA/CM). And then a user in the Project Lead workgroup (who can view the Code Object) runs the Code Object. If the Project Lead’s “View Code Object/Run” settings are set to full visibility, then the Code Run would be visible to everyone in the project. However, users from another collaborator won’t be able to see the Code Object since it’s unpublished, and thus aren’t allowed to see the Code Run.
{% endhint %}

</details>
{% endstep %}

{% step %}

### Create the project

Once you've adjusted the permission policies, click the **Create Project** button to create your project. The project appears on the **Projects** screen.
{% endstep %}
{% endstepper %}

## Editing Site-Level Permission Policies

To edit site-level permission policies, complete the following steps.

{% stepper %}
{% step %}

### In the project whose permissions you want to edit

Select **Collaborators** from the menu to the left.
{% endstep %}

{% step %}

### Select Permission Policy

Select **Permission Policy** option near the top of the page.

![](/files/649da09a0909a64f9e9aab7f0c5d043d84e66030)
{% endstep %}

{% step %}

### Select the down arrow next to the Site Level section

Select the down arrow next to the **Site Level** section, near the bottom of the page. Site-level permission policies appear.

![](/files/44f5f05510dc5ba3ec96c5d5318335cf83e3f55e)
{% endstep %}

{% step %}

### Select the Edit button

Select the **Edit** button.
{% endstep %}

{% step %}

### Make the changes

Make the changes to the Privacy Parameters and Actions, as needed.  If needed, review the permission policy details in the following expandable box.

<details>

<summary><strong>Site-Level Permission Definitions</strong></summary>

<table><thead><tr><th>Actions</th><th width="227.8046875">Description</th><th>Default Policy</th></tr></thead><tbody><tr><td>Manage This Site's Datasets</td><td>Import, export, modify, and remove Datasets associated with this site</td><td>MA, MM</td></tr><tr><td>Manage Data Mappings</td><td>Create, modify, and remove data mappings and vocabularies from this site.</td><td>PLA, PLM, MA, MM</td></tr><tr><td>Manage Secure Access Lists</td><td>Create, modify, and remove Secure Access Lists for Datasets from this site</td><td>MA, MM</td></tr><tr><td>Manage This Site's Code Runs</td><td>Modify and remove Code Runs associated with this site</td><td>MA, MM</td></tr><tr><td>Pre-approved Code Only</td><td>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</td><td>No</td></tr><tr><td>Run Code On This Site</td><td>Run code on Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>Share Secure Access Lists</td><td>Share Secure Access Lists for Datasets from this site</td><td>MA, MM</td></tr><tr><td>View Client-Side Logs</td><td>View logs from code run on Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>View Code Objects and Code Runs</td><td>Determines who can view workgroup code objects and code runs. Users without this permission only see code objects and code runs published to all project participants. See note below this table for more details.</td><td>CA, CM, MA, MM, PLA, PLM</td></tr><tr><td>View Datasets and Data Schemas</td><td>Allows you to view all workgroup Datasets and Data Schemas. Anyone without these permissions will only be able to view Datasets and Data Schemas that have been published to all project participants.</td><td>CA, CM, MA, MM, PLA, PLM</td></tr><tr><td>View Dataset Analytics</td><td>View aggregated analytics and metrics for Datasets from this site</td><td>MA, MM, PLA, PLM</td></tr><tr><td>View Datasets via Secure Access</td><td>Access data from this site via zero-footprint viewers (e.g. tabular data viewer, and interactive containers, OHIF)</td><td>MA, MM</td></tr><tr><td>View Client Side Logs with Sensitive Data</td><td>View logs from code runs on sensitive datasets from this site. This is included because code runs could write sensitive data to logs.</td><td>MA, MM</td></tr><tr><td>View Sensitive Datasets via Secure Access</td><td>Access sensitive data from this site via zero-footprint viewers such as a tabular data viewer and OHIF or interactive containers. This also includes fields marked as 'local only'.</td><td>MA, MM</td></tr></tbody></table>

</details>

<details>

<summary><strong>Site-Level Permission Definitions Notes</strong></summary>

{% hint style="info" %}
NOTE: If the personas for the View Code Objects and Code Runs setting are the default (PLA, PLM, MA, MM, CA, CM), then all members of the workgroup can see code objects and code runs. If you initially remove personas from the list, all code object and run versions will start as unpublished and are only visible to the included personas. Code runs are only visible to users who can see the code object.

You can change personas as you would for any other permissions setting. The personas in the permission list must include an MA or MM persona so site members can view and publish their own objects and runs.

The workgroup of the code object is the primary workgroup of the person who created the code object.

The workgroup of the code run is the primary workgroup of the person who triggered the code run.

Note: Code Runs are only visible to users for whom the Code Object is also visible. One edge case in which this might not automatically happen, is when there is an unpublished Code Object created by Collaborator A, with “View Code Object/Run” permissions set to PLA, PLM, MA, MM (so without CA/CM). And then a user in the Project Lead workgroup (who can view the Code Object) runs the Code Object. If the Project Lead’s “View Code Object/Run” settings are set to full visibility, then the Code Run would be visible to everyone in the project. However, users from another collaborator won’t be able to see the Code Object since it’s unpublished, and thus aren’t allowed to see the Code Run.
{% endhint %}

</details>
{% endstep %}

{% step %}

### Save the changes

When finished, select the **Save** button from the bottom right part of the screen to save the changes.
{% endstep %}
{% endstepper %}

## Getting Help

If you have received an error or run into any issues throughout the process, please reach out to <support@rhinohealth.com> for more assistance.