> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/tutorials/app-maker/getting-started/switching-organizations.md). # Switching Organizations You can be a member of more than one App Maker organization, and you work in one of them at a time. The organization you are working in decides what you see: its projects and builds, its Release Tracker, its users, roles and invitations, and what the [Command Palette](/tutorials/app-maker/getting-started/command-palette.md) finds. Its name is always shown at the left end of the header. ## The Organization Switcher The left end of the header shows the organization you are working in: its logo (or a placeholder) and its name. Click it to open the switcher. The switcher lists every organization you are a member of: * Active organizations come first, then inactive ones. * The organization you are working in has a check mark. * An organization that has been deactivated is marked **Inactive** and cannot be chosen. Click an organization to switch to it, and App Maker opens that organization's home page. From the keyboard, use the up and down arrows to move through the list, **Enter** to switch, and **Esc** to close the switcher without switching. ## Which Organization Opens * **Right after you sign in**, if you are a member of more than one active organization and have not chosen one in this browser yet, App Maker asks you to **Choose an organization** before it opens. Pick one. You can switch at any time from the header. See [Signing In](/tutorials/app-maker/getting-started/signing-in.md). * **Your choice is remembered in this browser.** When you open App Maker again, it opens the organization you last picked, from the sign-in question or from the switcher. While you are using App Maker, its home page takes you back to the organization you were last working in. * **If you were not asked**, because you signed in through a link that already named an organization, there is no choice of yours to remember yet. Until you pick one from the switcher, or answer the question at your next sign-in, App Maker's home page opens the first organization you joined that is still active. * **A link to an organization's page opens that organization**, whatever you picked before. A link a teammate shares always lands in the organization it was copied from, and following it does not change your remembered choice. ## Pages Outside an Organization Some pages belong to you rather than to an organization: your account pages (**Profile**, **Language Settings**, **Notification Settings**, **User Access Tokens**), **Plugins**, **Upgrade Helper** and **Public Keys**. On these pages the header keeps showing the organization you were working in, and the sidebar and the Command Palette keep pointing to it. The switcher works here too: choosing an organization, even the one already shown, takes you to its home page. ## When an Organization Cannot Be Opened * **You are not a member.** A link to an organization you do not belong to opens an **Authorization Error** page: "You are not authorized to view this page." The same page appears for a project you have no access to. Use its **go home** link to get back to your own organization. * **You have no active organization.** If none of the organizations you belong to is active, App Maker shows **Organization Required**: "You are not part of an organization. Please contact your administrator to access your content." ## Organizations in the CLI The App Maker CLI also works in one organization at a time (CLI 3.1.0 and later): * `appmaker login` keeps the default organization you saved before. With a single organization it uses that one. With several, it asks you to pick one. * `appmaker org switch` lists your active organizations and saves the one you pick as your default. * `appmaker org current` shows the organization the CLI is using and where that choice came from. `appmaker config show` shows the same. * `appmaker org list` lists the organizations you can switch to and marks your default. To run one command in another organization, pass `--organizationId ` or set the `APPMAKER_ORGANIZATION` environment variable. The CLI picks the organization in this order: 1. `--organizationId` 2. Inside a project directory, the organization that owns the project 3. `APPMAKER_ORGANIZATION` 4. Your saved default 5. Your only organization, when you have just one 6. Otherwise, it asks you to pick one An organization you are not an active member of fails the command instead of running somewhere else. The CLI never waits for an answer it cannot get: with no terminal, or with `CI=true`, a question fails the command instead and lists your organizations. In CI pipelines, set `APPMAKER_ORGANIZATION` or pass `--organizationId`. For every CLI command and option, see the AppMaker CLI documentation. --- # 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.akinon.com/tutorials/app-maker/getting-started/switching-organizations.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.