> 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/trusted-integrations/using-trusted-integrations.md).

# Using Trusted Integrations

Explains how to view, request, use, and manage Trusted Integrations in Rhino FCP.

## Overview

Rhino’s **Trusted Integrations (TI)** feature provides a controlled framework that allows Rhino Clients to securely connect to external tools—such as AI models or data repositories—without compromising the platform’s security architecture. &#x20;

{% hint style="warning" %}
Trusted Integrations connect to external services that **you select and contract with** directly.&#x20;

These services are NOT Rhino sub-processors. You are responsible for having appropriate agreements with the provider.
{% endhint %}

Trusted Integrations let code running in a Rhino Client **connect to an** **allow-listed external service** (one that has been added to the allow-list), such as a hosted AI model, cloud storage, or a clinical data system.&#x20;

By default, Rhino Clients are locked down – meaning they cannot transmit information to arbitrary websites or servers. They can only send data to allow-listed endpoints because Rhino Clients operate within highly restricted, secure environments.&#x20;

Since Trusted Integrations open a controlled path out, only workgroup administrators can initiate a request and **every request is reviewed** by Rhino FCP before it can be used. &#x20;

***

## Allowing Trusted Integrations

{% hint style="info" %}
**NOTE**: Trusted Integrations must be enabled **at the project-level** before projects can use them. See [#managing-project-level-trusted-access](#managing-project-level-trusted-access "mention"), below, for more information.
{% endhint %}

To allow projects to have access to allow-listed Trusted Integrations, do the following:

1. Select **Edit** from the three-dot menu on the right side of the Trusted Integration entry, then select **Apply to Projects**. &#x20;

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2F0XrfiRcF5D1oVozxdpO4%2Funknown.png?alt=media&amp;token=28f124fc-6ae6-49f4-9f01-2f1498830394" alt="" height="347" width="392">

2. Choose **Selected Projects**. &#x20;
3. Then, select the checkboxes for the projects you want to make the Trusted Integration available to.
4. When complete, select the **Apply to Projects** button at the bottom right corner of the screen.

***

## Viewing Trusted Integrations

To view available Trusted Integrations, complete the following steps.

1. Select the **Settings** (Profile) button at the left bottom corner of the screen. (It looks like a sprocket)

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FwKuzxh5OCuXJfhhdOcG6%2Funknown.png?alt=media&amp;token=0d75fdcc-3eb4-4566-a886-5596722d6a1d" alt="" height="103" width="22">

2. In the Settings menu, select **Trusted Integrations.** The Trusted Integrations screen appears.

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FZgUsJtpA775rQAP4P47J%2Funknown.jpeg?alt=media&amp;token=5391e3ef-4b0d-4342-b94a-0b74eef6f2c7" alt="" height="315" width="552">

3. You'll see the name of the Trusted Integration, target, port, status and a default for code (whether they are enabled or not).

{% hint style="warning" %}
If you do not see a Trusted Integration, it has either not been allow-listed or has not been activated for your project.&#x20;

Contact your Rhino Workgroup Administrator for help in submitting the Trusted Integration and/or making it available for your project.
{% endhint %}

***

## Requesting Trusted Integrations&#x20;

A new Trusted Integration starts as a **request**. Your workgroup administrator sends the request to a Rhino administrator (at Rhino FCP). It stays pending until the Rhino administrator finishes reviewing it.&#x20;

A Trusted Integration cannot be used in code unless it's status is allow-listed.

{% hint style="info" %}
**NOTE**: At run time, the Trusted Integration only connects on its owning workgroup’s site. &#x20;

If a run also goes to other sites, those sites are blocked from connecting through it, and the run fails at those sites with an error naming the blocked integration. &#x20;

For another site to use the same external service, that site’s admin must request its own Trusted Integration for the service. Once Rhino allow-lists it and the admin applies it to the project, the site connects through its own Trusted Integration during the run.
{% endhint %}

### Prerequisites

Before you request a new Trusted Integration, gather the following information.

* The kind of **service**: a hosted AI model, a clinical or research data system, cloud storage, or something else (Custom/Other).&#x20;
  * If you are not sure which type of Trusted Integration to choose, select Custom/Other.
* The **provider**, such as Amazon Bedrock or a FHIR server.
* The **target** domain name or IP address for the service.&#x20;
  * Rhino pre-fills a suggested domain for some providers, but it may not match your region. Check your provider's documentation for the correct domain.
* The **port**. Most services use port 443, which is the default.
* Which **Projects** should be able to use the integration.
* **Credentials** for the service, stored as secret parameters.&#x20;
  * Rhino does not manage your passwords, API keys, or tokens.

It is also helpful, but not required, for you to know which projects that you want to allow access to the integrations if they are allow-listed.&#x20;

Project access can also be granted after allow-listing has occurred.

### Submitting a Request

To submit the Trusted Integration request, complete the following steps.

1. Select the **Settings** (Profile) button at the left bottom corner of the screen. (It looks like a sprocket.)
2. In the Settings menu, select **Trusted Integrations.** The Trusted Integrations screen appears.
3. At the top of the Trusted Integrations screen, select the **Add Trusted Integrations** button in the top right corner of the screen. The Request Trusted Integration screen appears.<br>

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FOR0N05gSdYyBHJazshhF%2Funknown.png?alt=media&amp;token=8500ba36-ee19-4b78-a2da-4ac2365f1191" alt="" height="175" width="403">

4. Select the kind of **service** you want to connect to: either Hosted AI model, Clinical or research data system, Cloud Storage, or Custom/Other, then select Next.&#x20;
5. On the screen appears “Which provider are you using?”, select the button for the **provider** you are using, then select the Next button. Note that the following screen might look different depending on which providers are available.

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FhfY1jD2H8CqEyu50QJPe%2Funknown.png?alt=media&amp;token=c125dcb7-2157-47b6-bfb7-86172e75343a" alt="" height="161" width="438">

6. If you selected Clinical or Research Data or Cloud Storage, skip this step. Otherwise, supply the following information: Service **name, description, target** (whether it is a domain name or an IP address) and the **port**.  When complete, determine whether to enable the integration by default.&#x20;

   1. If you do this, the integration will be automatically turned on for all current and future code objects.
   2. If it is turned off, then users will need to manually choose to include the connection in each code object. &#x20;

   When finished, click **Next**.

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FxxM7buuB7dgT3odNokqz%2Funknown.png?alt=media&amp;token=7eaf0a14-04a1-4012-abda-ea76d2a964a1" alt="" height="282" width="392">

7. Select the Projects that you want to make the Trusted Integration available to. &#x20;

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FoSeRYBVGJGu3JqurnC72%2Funknown.png?alt=media&amp;token=54d192a0-88c9-473e-9062-4f28b4304681" alt="" height="337" width="382">

\
8\. Select one of the following options. \
When you’ve selected the projects you want, select the **Request Service** button.

<table><thead><tr><th width="217.421875">Option</th><th>Description</th></tr></thead><tbody><tr><td>Selected Projects</td><td>Choose this option to manually select the projects that can access this integration.  If you choose this option, you will need to select a project from the bottom half of the screen.  You can use the search projects field to manually type in the characters for project names or select an item from the drop down menu to view a subset of projects.  If a new project is added in the future, you will need to manually add it.</td></tr><tr><td>All Current Projects</td><td>Choose this option to make the Trusted Integration available to all current projects.  If a new project needs to be added in the future, you will need to manually add it.</td></tr><tr><td>All Projects</td><td>Choose this option to make the Trusted Integration available to all projects, including those that will be added in the future.</td></tr></tbody></table>

9\. Once submitted, your submission appears with a status of **Pending**.  \
A Rhino Administrator will review your submission and will either allow-list it or reject it.&#x20;

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FuGJWRK83RNj3AwA01ebZ%2Funknown.png?alt=media&amp;token=2984406a-7f92-40a1-ad86-5c994c85a011" alt="" height="51" width="582">

{% hint style="info" %}
**NOTE**: Because Trusted Integrations allow data to leave the Rhino client, a Rhino employee reviews each request before it is allow-listed or rejected.&#x20;

While this review confirms that the request is complete and appropriate for use on the Rhino platform, it is not a security assessment or endorsement of the external service.&#x20;

**You are responsible for evaluating the security, privacy, and regulatory suitability** of any service you connect to, and for having appropriate agreements in place with that provider.&#x20;

Contact your Rhino representative if you have questions about a request.
{% endhint %}

### Viewing Trusted Integration Status

Once submitted to Rhino FCP, the Trusted Integration is reviewed by a Rhino Administrator.  To view the status of the request, complete the following steps: <br>

1. Select the **Settings** (Profile) button at the left bottom corner of the screen.&#x20;
2. In the Settings menu, select **Trusted Integrations**. The Trusted Integrations screen appears. &#x20;
3. The statuses are:

* **Pending** - The Trusted Integration is under review for allow-listing or rejection.&#x20;
* **Allow-Listed** - The Trusted Integration request has been reviewed and it can now be used.
* **Rejected** - The Trusted Integration request has been reviewed and it has not been allow-listed for use.

***

## Editing Trusted Integration Details

You can edit some Trusted Integration details, such as the **service name, description, domain name** or **IP address,** and the **port**.  If you edit, the status will become pending and you’ll need to re-submit the changes for allow-listing before the integration is available for reuse. &#x20;

Note that pending Trusted Integrations can’t be selected in code objects. Also, if the code run was enabled at the time of run, but is now pending or disabled, running it again will return an error.&#x20;

Note that Trusted Integrations are **fixed** when a code run starts. If an integration is edited, disabled, or removed while a run is in progress, that run keeps going with the settings it started with. The change only applies to future runs. &#x20;

To **edit** the details, complete the following steps:

1. Select **Edit** from the three-dot menu on the right side of the Trusted Integration entry.

<img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FFHybIMLZzr7KN5okKqGx%2Funknown.png?alt=media&amp;token=b380f06b-aa9f-4a91-8e1c-ca7b00b85b70" alt="" height="92" width="224">

2. The Edit Trusted Integration screen appears.  Edit the information in the screen, then select the **Submit** button.
3. Once submitted, your submission appears with a status of Pending. A Rhino Administrator will review your submission and will either allow-list it or reject it. &#x20;

***

## Removing a Trusted Integration

To **remove** a Trusted Integration, complete the following steps:

1. Select **Edit** from the three-dot menu on the right side of the Trusted Integration entry, then select **Remove**.
2. You will be prompted. Respond to the prompt to remove the Trusted Integration.

Note that Trusted Integrations are set when a code run starts. If an integration is edited, disabled, or removed while a run is in progress, that run **keeps going** with the settings it started with. The change only applies to future runs.

***

## Managing Project-Level Trusted Access

You can block the use of all Trusted Integrations in a project or allow workgroups to manage them according to their own settings.

{% hint style="info" %}
**NOTE**: The Org Admin has the same Trusted Integration rights as the Workgroup Admin for its own workgroup.&#x20;
{% endhint %}

### Blocking All Trusted Integrations in a Project

Project Lead Admins can **block** all Trusted Integration connections in a project using the Project-Level Trusted Access switch:

1. Select **Administration** from the project’s main menu.
2. Select the **Trusted Integrations** tab to view your current status and listed integrations.
3. At the top of the screen, locate the **Project-Level Trusted Access** control and move the slider to the **left**.
4. Verify that the confirmation banner appears, indicating that Trusted Integrations are blocked for everyone on the project.

### Allowing Workgroup Settings for Trusted Integrations in a Project

To apply workgroup settings for Trusted Integrations you can enable the switch:

1. Select **Administration** from the project’s main menu.
2. Select the **Trusted Integrations** tab.
3. At the top of the screen, locate the **Project-Level Trusted Access** control and move the slider to the right.

{% hint style="info" %}
Re-enabling project access restores workgroup settings, but it will never turn on an integration that a workgroup has explicitly turned off.
{% endhint %}

**IMPORTANT**: Rhino does not manage your passwords, API keys, or security tokens. You are responsible for securing each integration and for the risks of any external connection you enable. Approve only endpoints that are trusted and necessary.

***

## Understanding Trusted Integration Access

The following tables show detailed permissions about which roles can request, manage view, edit, manage, and select Trusted Integrations. &#x20;

### Workgroup Role

For managing your workgroup's TIs

| Action                                   | Workgroup Admin / Org Admin | Workgroup Member |
| ---------------------------------------- | --------------------------- | ---------------- |
| View own workgroup's TIs                 | Yes                         | Yes              |
| Request a new TI                         | Yes                         | No               |
| Edit or remove a TI                      | Yes                         | No               |
| Choose which projects a TI is applied to | Yes                         | No               |

### Project Role

For controlling and using TIs in a project

| Action                                         | Project Lead Admin (PLA) | Project Lead Member (PLM) | Collaborator Admin (CA)  | Collaborator Member (CM) |
| ---------------------------------------------- | ------------------------ | ------------------------- | ------------------------ | ------------------------ |
| Turn the project TI switch on or off           | Yes                      | No                        | No                       | No                       |
| View another workgroup's TI                    | If shared to the project | If shared to the project  | If shared to the project | If shared to the project |
| Select own workgroup's TI in a code object     | Yes                      | Yes                       | Yes                      | Yes                      |
| Select another workgroup's TI in a code object | If shared to the project | If shared to the project  | If shared to the project | If shared to the project |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rhinofcp.com/trusted-integrations/using-trusted-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
