> 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/run-pre-approved-code-only.md).

# Run Pre-approved Code Only

This article explains how to set up your Site Permissions to limit collaborators to run pre-approved code only. See the video below for a guide through and below for a step by step description.

This Site-level permissions setting enables you to limit the code that Collaborators may run using your data. Once **Pre-approved Code Only** is set to **Yes,** you will be able to manage a list or container images that your collaborators can use.

To add or remove a container image from the pre-approved code list, follow these steps:

1. Make sure you know your Collaborator's workgroup name and the exact name of the container image they wish to run.
2. In your FCP project, navigate to the **Collaborators View** and click on the **Permissions Policy** tab.
3. Under your site's Site-level Permission section, click on the gear icon next to the pre-approved code permission:

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/7U2WplwGMIZMaH13l9wM/30755734139805)

4. Click the **+ Add Container Image** button

![](https://content.gitbook.com/content/ydySyCBmy6F7NnGn4bPa/blobs/26pzfE1NZjcoXMehpHMD/30755729373853)

5. A new row will be added to the table. Select your Collaborator's workgroup name, and type the Container Image name in the new row.
6. Click **Submit** to save changes. If the Container Image name does not exist in the collaborator's ECR, this step will fail.


---

# 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/projects/run-pre-approved-code-only.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.