> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/integration-gateway-platform-reference/permissions/organizations.md). # Organizations Organizations allow multi-tenant Integration Gateway environments to manage the data their customers have access to while sharing the same set of integrations. Members of an organization can view the run histories and [schedules](/integration-gateway-platform-reference/integration-scheduler.md) of all members of their organization, but cannot see the run histories generated by members of other organizations. Organizations do **not** impact the [integrations](/integration-gateway-platform-reference/permissions.md#integration-permissions) or [system permissions](/integration-gateway-platform-reference/permissions.md#user-permissions) a user has access to. Those permissions are still governed on a per-account basis, or any [groups](/integration-gateway-platform-reference/permissions.md#group-permissions) the account belongs to. *Organizations can only be created by Sandbox Banking staff at this time. If you are interested in creating an Organization, reach out to * --- # 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://glyue.docs.sandboxbanking.com/integration-gateway-platform-reference/permissions/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.