> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/security/authentication-overview/switch-organizations-in-command.md).
# Switch Organizations
Learn how to switch between more than one organization in Verkada Command
When you are a part of multiple organizations, your user account is separate for each organization. This allows for more granular control of user accounts by Organization Admins, such as requiring 2-factor authentication.
***
## Specify an org's short name
An org's **short name** is a unique identifier used to specify which org you log in to.
{% hint style="warning" %}
If you are part of 2 or more orgs, when you log in to Verkada Command, you must specify the org's short name. Once logged in, if you have verified your email, you can switch between all organizations.
{% endhint %}
You can also use a [Login Link](/command/security/authentication-overview/login-links.md) to log in to all password-only orgs at once.
***
## Find your short name
### Via email
When you log in to Verkada Command, if you don't know the short name, click **Email me a list** to receive an email list with verification links for each org.
### While logged in
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}
{% step %}
**Under General > Organization, the short name is listed next to the Subdomain field.**
{% endstep %}
{% endstepper %}
***
## Switch between orgs
{% hint style="warning" %}
If you have created organizations in different regions, you will see separate lists for **United States**, **Europe**, and **Australia**.
{% endhint %}
{% stepper %}
{% step %}
**At the bottom left, select the organization icon to view all organizations where you have login access.**
{% endstep %}
{% step %}
**Select any organization listed to switch.**
{% endstep %}
{% endstepper %}
{% hint style="danger" %}
You are **required** to log in to other orgs when switching, unless you have authenticated recently within the org's session time limit.
{% endhint %}
***
## Unable to see all of your orgs
If not all orgs appear in the list, this can happen when your email is not verified in each org.
{% stepper %}
{% step %}
**At the bottom left, select the org name.**
{% endstep %}
{% step %}
**Check for a green checkmark next to your email. If you don't see it,** [**verify your email**](/command/security/authentication-overview/verify-your-verkada-command-account.md)**.**
{% endstep %}
{% endstepper %}
---
# 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.verkada.com/command/security/authentication-overview/switch-organizations-in-command.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.
