> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/readme/secoda-as-an-admin/invite-teammates/joining-and-navigating-between-multiple-workspaces.md). # Joining and navigating between multiple workspaces You are able to join more than one Secoda workspace with the same email. Users can be part of multiple Secoda workspaces, using the same email. This might be relevant if your team is hoping to have different production and staging workspaces, or if you have multiple clients to extend the product to. Follow the instructions on [how to Invite Teammates to Secoda](/readme/secoda-as-an-admin/invite-teammates.md) to invite users to the desired workspace. If you are a user of more than one workspaces, you will be able to navigate between them by clicking on the workspace logo in the top left corner of your screen as demonstrated below: {% embed url="" %} --- # 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.secoda.co/readme/secoda-as-an-admin/invite-teammates/joining-and-navigating-between-multiple-workspaces.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.