> 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/user-hub/ninox-basics/organizations-and-workspaces.md).

# Organizations and workspaces

Organizations and workspaces define where your team works in Ninox.

An organization is your team’s home in Ninox.\
A workspace sits inside an organization. It holds the apps, data, and setup for a specific team, project, or process. Many teams create separate workspaces for different departments or areas of work.

### How they fit together

The structure is simple:

* One organization contains one or more workspaces.
* Each workspace contains one or more apps.
* Each app contains the tables, views, and pages you use every day.

### What this means in daily work

You work inside the workspaces that are available to you. From there, you open the apps you need and work with records, views, and tasks. How many workspaces you use depends on how your organization is set up in Ninox and on the permissions granted by your organization admin.

Your access can vary across apps, tables, and views. You might be able to add records without seeing all data. You might have write access in one table, but no access to another. You can also work with dashboards when your permissions allow it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ninox.com/user-hub/ninox-basics/organizations-and-workspaces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.