> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/connected-analytics/web-ui-access/h-projects/externally-managed-projects.md).

# Externally-managed Projects

Illumina software applications such as BaseSpace which do their own data management on Platform Core, store their resources and data in a project in the same way as manually created projects. These projects are considered **externally-managed projects.** There are additional **restrictions** on which actions you can perform from within Platform Core on externally-managed projects to prevent inconsistencies when these applications want to access their own project data.

* You **cannot delete or move externally-managed data**.
* You can **add** [**files**](/connected-analytics/project-web-ui/p-data.md) and data such as [samples](/connected-analytics/project-web-ui/p-samples.md) to externally managed projects. Separation of data is ensured by only allowing additional files at the **root level** or in **dedicated subfolders** which you can create in your projects. **Data which you have added can be moved and deleted** again.
* You can **add** [**bundles**](/connected-analytics/web-ui-access/h-bundles.md) to externally managed projects, provided those bundles do not come with additional restrictions for the project.
* You can **start** [**bench**](/connected-analytics/project-web-ui/p-bench.md) **workspaces** in externally-managed projects. The resulting data will be stored in the externally-managed project.
* Project administrators and tenant administrators can **disable** [**data sharing**](#create-new-project) on externally managed projects at **Projects > externally\_managed\_project > Project Settings > Details** to prevent data from being copied or extracted.

Projects are indicated as **externally-managed** in the projects overview screen by a project card with a **managed by app \<app name>** label or the “**managed by**” column, visible in the data list view.

### Data Transfer

If you have an externally-managed project and want to **move** the data to another project:

1. [Copy the data](/connected-analytics/project-web-ui/p-data.md#data-management) from the externally-managed project to the other (new) project.
2. From within your external application, delete the data which is stored in the externally-managed project in Platform Core.

### Notes

{% hint style="info" %}
When you create a folder with a name which already exists as an externally-managed folder, your project will have that folder twice; one Platform Core-managed and one externally-managed.
{% endhint %}

Tertiary modules such as [cohorts](/connected-analytics/project-web-ui/p-cohorts.md) are not supported for externally-managed projects.

Externally-managed projects protect their **notification subscriptions** to ensure no user can delete them. It is possible to add your own subscriptions to externally-managed projects, see [notifications](/connected-analytics/project-web-ui/p-notifications.md) for more information.


---

# 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://help.bioinsight.illumina.com/connected-analytics/web-ui-access/h-projects/externally-managed-projects.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.