> For the complete documentation index, see [llms.txt](https://docs.wayfound.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wayfound.ai/settings/organizations.md).

# Organizations

### Navigating Organizations (All Users)

An organization is an instance of the platform. Organizations can host multiple users, and every user in an organization can view and manage all of its agents. All users in an organization can also access the organization's currently active tools and integrations.

Customers may want to create multiple organizations on the platform in order to split users and/or agents. Customers can create multiple organizations with an Enterprise plan. To do so, contact Wayfound.

An individual user can also join multiple organizations on the Wayfound platform. If you belong to multiple organizations, you can switch between them without signing out. To do so, hover the mouse over your email at the bottom left corner of the screen. A menu of organizations will appear. Select the organization you wish to use. You can always check which organization you're in by mousing over your name and viewing the menu.

### Organizations settings (Admin only)

Users with admin permissions can view their organization details in the settings menu. In the organizations tab, you can update the company name and view your Customer Support ID, Wayfound Plan, and the amount of Credits used.


---

# 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.wayfound.ai/settings/organizations.md?ask=<question>&goal=<user_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.
