> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/msp-multitenant-support.md). # MSP (Multitenant) Support dope.security supports Managed Service Providers (MSPs) that manage security for multiple customers. As an MSP, you can access and manage several customer tenants using a single admin identity, and switch between them without needing separate logins. ## How It Works Multi-tenant access is achieved by adding your MSP domain email address as an admin to each customer tenant you manage. Once added, that single email can be used to log in and access any tenant it has been granted admin rights to. ## Setting Up a Customer Tenant To onboard a new customer under your MSP: 1. **Create the tenant using the customer's domain.** Each customer tenant must be set up with the customer's own domain — not your MSP domain. 2. **Add your MSP admin email as an admin in the customer's tenant.** This grants your MSP admin account access to that tenant, alongside the customer's own admins. Repeat this process for each customer tenant you need to manage. ## Logging In and Switching Between Tenants When you log into [fly.dope.security](https://fly.dope.security/) using your MSP admin email, you'll be prompted to select which customer tenant you want to access for that session. If you need to switch tenants during a session: 1. Select the login icon in the top-right corner of the screen. 2. Choose the tenant you want to switch to from the list of tenants associated with your MSP admin email. All tenants you've been added to as an admin will appear in this list, letting you move between customer environments without logging out or using multiple credentials. --- # 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://inflight.dope.security/dope.console/msp-multitenant-support.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.