> 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/getting-started/builder-getting-started/set-up-your-ninox-manually.md). # Set up your Ninox manually Repeat the Quickstart without the AI assistant to set up your organization, build your first app, add automations, and invite your team. Set up Ninox manually and learn the core building blocks behind app creation. This path walks you through your first organization and workspace, your first app, your first automations, and team access. Work through the chapters in order. Each chapter builds on the previous one. ## **Chapters**

Your first organization and workspace

Learn how Ninox structures organizations and workspaces, and create your first setup.

Your first organization and workspace

Your first app

Build your first app manually by creating tables, fields, and relationships.

Your first app

Your first automations

Add logic and automations so your app calculates values and keeps invoice data stable.

Your first automations

Invite your team and assign roles

Invite users at the right level and assign roles so everyone gets the right access.

Invite your team and assign roles
--- # 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/getting-started/builder-getting-started/set-up-your-ninox-manually.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.