> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/workspace-and-discovery/project-sharing-and-permissions.md).

# Project sharing and permissions

Share folder access so colleagues can open the projects inside it. Send a project link after the recipient has the required access.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FEHXKM3VngKxlWVyyyiDP%2FG006.mp4?alt=media&token=84b12d04-3751-45db-8841-0e6e2d5ff6b6>" %}

## Copy the project link

Open the project’s **Share** dialog and select **Copy link to workflow builder**.

![Builder link in the project Share dialog](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/WX3tZlXr2tPFdsq9rosQ/assets/g006-g006-01-share-builder-link.png)

## Check the recipient’s access

The recipient must use an account in the correct organization. If the project is in a private folder, they also need access to that folder.

![Recipient account and organization access check](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/DUPxMsdXLrknO5YyHpwj/assets/g006-g006-02-second-session.png)

## Share a private folder

Open the folder menu and select **Settings**. Find **Share folder with other members**.

![Private folder sharing settings](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/zkOYlQZ9xiLek8yDXEOQ/assets/g006-g006-03-private-folder-settings.png)

Select **Add Members** and choose the members or groups that need access.

![Member and group selection for folder access](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/wqijMGJUqX4eqlkveihh/assets/g006-g006-04-add-member.png)

Select **Save Changes**.

![Save Changes for folder sharing](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/4wGdkvdCY25ZKOaNkj4S/assets/g006-g006-05-save-access.png)

## Open the shared project

The recipient can now open the project link with the authorized account.

![Recipient access to the shared project](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/aec4o365mG5jLtL3SNh0/assets/g006-g006-06-verify-second-account.png)

## Important behavior

A project link does not grant access by itself. The member’s organization role determines which actions they can perform after opening the project.

Access to a published interface is configured separately in the interface’s security settings.

## Next steps

If a recipient cannot find the folder, check [Roles and permissions](/guides-and-quickstarts/organization-administration/roles-and-permissions.md) with an administrator. To share the user-facing chat instead of the builder, use [Interface authentication and access](/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md) and [Publish a Chat Assistant](/guides-and-quickstarts/interfaces-and-end-user-experiences/publish-a-chat-assistant.md).


---

# 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.stackai.com/guides-and-quickstarts/workspace-and-discovery/project-sharing-and-permissions.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.