> 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/technical-reference/identity-access-and-administration/folder-and-project-access.md).

# Folder and Project Access

Folder and project sharing control access to project content. Review the effective access after moving or sharing a project.

{% 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>" %}

## Before you begin

Permission to manage the relevant folder or project.

## Key concepts

| Term             | Definition                                                                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Folder           | A collection used to organize projects. A folder can also have access settings. Review effective access when sharing or moving a project.              |
| Project          | The saved agent or workflow and its related configuration. Its ID identifies the resource; it does not identify a particular run or published version. |
| Role             | A set of permissions assigned to a member or supported account. Inspect the permission matrix rather than inferring access from the role name.         |
| Inherited access | Access that comes through another shared container or membership relationship. Review the effective result when a project belongs to a shared folder.  |
| Authorization    | The decision whether a caller can perform an operation on a resource. Check roles, scopes, organization context, and sharing when access is denied.    |

## Grant folder and project access

1. Open its sharing settings and inspect existing access.

![Open Share to inspect the project’s sharing options; a copied link does not grant access.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/WX3tZlXr2tPFdsq9rosQ/assets/g006-g006-01-share-builder-link.png)

Open Share to inspect the project’s sharing options; a copied link does not grant access.

2. Add or change the intended person or group using the supported role.
3. Confirm access from the recipient’s account and review any inherited folder access.

The intended recipient can use the project at the assigned level.

## Behavior and limitations

A project URL does not grant access. Editing, running, sharing, and viewing analytics can require different permissions. Moving a project can affect its organization and access context. Connection permissions still apply to operations inside a shared project.

## Related resources

[Project sharing and permissions](https://docs.stackai.com/guides-and-quickstarts/workspace-and-discovery/project-sharing-and-permissions.md)

[Organization Roles and Permissions](https://docs.stackai.com/technical-reference/identity-access-and-administration/organization-roles-and-permissions.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/technical-reference/identity-access-and-administration/folder-and-project-access.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.
