> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# How projects work

> How a project gathers the skills, agents, and sources for one piece of work, and what sessions in it start with.

A project gathers the skills, agents, and sources for one piece of work, so every session in it starts with the right context. Start one for a launch, a codebase, or an account, link the context its sessions should begin with, and write the goal agents read first.

## What a project holds

| Part | What it is |
| - | - |
| **Goal** | What the project is for. Agents read it first in every session in the project. |
| **Linked context** | The skills, agents, tools, and lessons the project's sessions start with. Linking never copies or moves: each one stays in its workspace, and edits show up in the project. |
| **Sources** | Web links agents read before they start: docs, sheets, or repos. A project holds at most 32, linked by address, never copied. |

## Where projects live

A project lives in one workspace. Everyone in the workspace sees it, and their role in that workspace decides what they can do in it: a project has no member list or roles of its own. See [Roles and access](/administer/workspaces/references/roles-and-access) for the roles.

In the Brain's navigation, select **Projects** to open the list. It follows the scope you have open: every workspace's projects when the scope is the whole account, and one workspace's projects when you have opened that workspace. Each card shows the project's name, workspace, goal, sources, and when it was last updated, most recent activity first. The list separates **Active** and **Archived**.

## Create a project

1. In the Brain's navigation, select **Projects**, then **New project**. The button appears when you can create a project in a workspace you can reach.
2. Enter a **Name**. The app derives a handle from it and shows it under the field: the handle is what the project's address uses and what the CLI uses, and it can't change later.
3. Choose the **Workspace** the project lives in. The picker offers the workspaces you can start a project in, and everyone in the workspace will see the project.
4. Write the **Goal**, or leave it empty and write it later.
5. Select **Create project**. The project opens.

## Link context into a project

A project opens on its **Overview**: the goal, the linked context by kind with counts, the sources, and the five linked items that changed most recently, wherever they live.

Select **Link context** on the Overview, or **Link skills** on the Skills tab, to open the picker. It lists the project's own workspace's artifacts, one kind at a time, and marks what is already linked as **Already linked**. Select what you want, then select **Link** followed by the number you picked, such as **Link 2**: sessions in the project start with them.

A kind appears in the project's navigation under **Linked context** once the project holds one of it, with a count. Each tab lists its items with their **Origin** — **Created here** when the artifact was created in the project, **Linked** when it was linked in from the workspace — and when it was last updated. To remove one, open its actions menu and choose **Unlink from project**: the link goes, and the artifact stays in its workspace. You change a linked artifact where it lives; the project shows the change.

## Sources

On the **Sources** tab, paste a web link starting with `https://` or `http://` and select **Add**. A project holds at most 32 sources, and the tab counts how many are used. Remove a source from its row.

## Change or archive a project

On **Settings**, change the project's **Name** and **Goal**. The **Handle** is shown and never editable.

**Archive project** hides the project from the active list and keeps its history. Nothing linked into it is touched: every skill, agent, and source linked there stays where it lives. Archived projects are on the list's **Archived** tab.

## Example

A platform team starts **Q4 pricing launch** in their shared workspace. The goal says the project ships the pricing page, the FAQ, and the sales enablement kit. They link the SQL review skill and the data steward agent, and add the pricing model spreadsheet and the draft product brief as sources. A teammate opens the project and starts a session, and the session begins with the linked skills and the goal, so nobody pastes the same links into the prompt.

## What projects do not do

* **A project is not a second home for an artifact.** Linking never copies or moves it, and unlinking removes the link, never the artifact. It stays in its workspace.
* **A project grants no access.** It has no members or roles of its own: everyone in its workspace sees it, and their workspace role decides what they can do in it.
* **An archived project is not deleted.** Archiving hides it from the active list and keeps its history, with its links untouched.

## See also

* [How workspaces work](/registry/workspaces/index): The scope a project lives in and inherits.
* [How sessions and traces work](/concepts/how-sessions-and-traces-work): What a session records once it runs.
* [Choose where skills live](/registry/workspaces/how-tos/organize-artifacts): Decide the workspace before you publish.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.