nao Cloud

Documentation Index

Fetch the complete documentation index at: https://docs.getnao.io/llms.txt

Use this file to discover all available pages before exploring further.

nao Cloud is the hosted version of nao. It runs your analytics agent in our infrastructure and adds organization-level features that are not available in self-hosted deployments: multi-project organizations, team management, per-organization API keys, GitHub-connected context sync, and managed environment variables.

​

Organizations and projects

A Cloud account belongs to one or more organizations. Each organization owns one or more projects, and each project is the unit that hosts an agent, its context, its connected data sources, and its chats.

• Organization-level settings (billing, members, API keys) apply across every project in the organization.
• Project-level settings (data connections, context, chat behavior) are scoped to a single project.
• A user can belong to several organizations and switch between them from the workspace switcher.

To manage organization-wide settings, open Settings -> Organization.

​

Managing team members

Organizations and projects both have their own member lists. Organization members Open Settings -> Organization -> Members to:

• Invite a new member by email. They receive an invite link and become a member once they sign in.
• Change a member’s role (admin or member).
• Remove a member from the organization.

Admins can manage billing, API keys, members, and organization-wide settings. Members can use the projects they are added to. Project members Each project has its own member list under Settings -> Project -> Team. Add organization members to a project to give them access to that project’s chats, context, and data. A user must be in the organization before they can be added to one of its projects.

​

Per-organization API keys

API keys live at the organization level and are used to call the nao API from your own services, CI, or other integrations.

1. Open Settings -> Organization -> API Keys.
2. Click Create key, give it a name, and copy the key. It is shown only once.
3. Revoke a key from the same page when it is no longer needed.

Each key is scoped to its organization and can access every project the organization owns.

​

Connecting a GitHub repository for context

Cloud projects can sync their context folder from a GitHub repository instead of uploading files manually. Once connected, nao pulls the latest state of the repo on a schedule so the agent always sees the current context.

1. Open Settings -> Project -> Context -> Git sync.
2. Click Connect GitHub and authorize the nao GitHub app on the organizations you want to expose.
3. Pick the repository and branch that holds your nao_config.yaml and context folder.
4. Save. nao performs the first sync immediately and then refreshes on every push to the selected branch.

The repo picker only lists repositories the nao GitHub app has access to. If you do not see the repo you want, go back to GitHub and add it to the app’s installation.

​

Environment variables

Cloud projects expose an Environment variables section under Settings -> Project -> Environment. Use it to set credentials and other values referenced from nao_config.yaml without shipping them in your git repo.

• Add, edit, or remove variables from the UI.
• Variables are injected into the runtime for sync jobs and chat requests.
• Reference them in config the same way as on self-hosted: {{ env('MY_VAR') }}.

Secrets are encrypted at rest and are not displayed back in the UI after they have been saved.

​

What’s next