> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/manage-your-organization-and-workspace/manage-your-organization.md). # Manage your organization Manage settings, access, subscriptions, workspaces, and integrations at the organization level. Manage the parts of Ninox that apply across your whole organization. You can control organization settings, member access, billing, workspace administration, and integrations. Choose a topic to go straight to the task you need.
Manage organization settings
Change the organization name, review the internal name, and delete the organization when needed.		Manage organization settings
Manage organization access
Invite members, assign organization roles, and manage workspace custom roles.		Manage organization access
Manage connections
Create and manage organization-level connectors for external systems.		Manage organization-wide connections
Subscriptions and usage
Review your plan, manage billing, and track usage across the organization and its workspaces.		Subscriptions and usage
--- # 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.ninox.com/builder-hub/manage-your-organization-and-workspace/manage-your-organization.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.