> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/resources/errors-and-faqs/unable-to-access-a-project-or-see-files-uploaded-by-teammates.md). # Unable to access a project or see files uploaded by teammates If you cannot see a project or files that you expect to have access to, it is usually due to access settings or project context, not because the data is missing. #### Common reasons * You are logged in with a **different email ID**. * You have not been added as a member to the project. * You have limited permissions within the project. * You are looking at the **wrong project**. Projects are fully isolated from each other, files and outputs only appear inside the project they belong to. {% hint style="warning" %} Being part of the same organisation does not automatically grant access to all projects. {% endhint %} #### Project roles and visibility Each project member is assigned a role: * **Admin** – full access, including managing members and settings * **Write** – can upload/delete files and run tasks * **View** – read-only access Files uploaded to a project are shared with all members. #### How to resolve * Confirm you are logged in with the correct email ID. * Check that you are viewing the correct project. * Ask a project admin to verify your role or add you to the project. * Refresh the project view after access is updated. --- # 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.jurisphere.ai/resources/errors-and-faqs/unable-to-access-a-project-or-see-files-uploaded-by-teammates.md?ask=&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.