Find a dashboard section
Share a balance in an organization
Every balance belongs to an organization. When you sign up, NagaAI creates your personal organization, named Personal, with you as its owner. It holds your own balance, API keys and logs, and you can rename it or invite colleagues into it. You can’t leave or close it while your account is open. A team organization has its own balance, workspaces, API keys and logs, separate from your personal one. A team can spend from one pot and see one request history. The account list in the sidebar’s switcher card moves you between your personal organization and your teams. The Playground spends from the one you picked. You can create up to 3 team organizations, and each can hold up to 100 members. Your personal organization doesn’t count toward that limit. Admins invite people by email under Organization → Members. An invitation works for 48 hours, and Organization → Invitations lists the pending ones with the time each has left. Admins also change a member’s role right in the members list.
Billing is for the person who pays. They add credits, open receipts, set the billing details on invoices and watch spending on Metrics, but can’t open API Keys, Logs or Privacy. When an admin gives someone the Billing role, the keys that person created stay enabled and pass to the admins. Members can’t see credits, provisioning keys or privacy settings, and see metrics and logs only of the workspaces they administer. On the API Keys page a member sees and changes the keys they created. In a workspace they administer, they see every key, as Choose who works in a workspace describes. Admins see and change every key of the organization, including keys created before November 3, 2026, which only admins see. Only the owner and admins invite people and change roles.
When a person leaves the organization or an admin removes them, NagaAI disables the keys they created in it, so they stop spending its balance. The keys stay in the admins’ list, and an admin can enable one that a service still needs. The person doesn’t get them back if they rejoin.
Let colleagues join by their email domain
A team can claim its company’s email domain, so colleagues reach it without an invitation each. Under Organization → General, an admin adds the domain in Verified domains. NagaAI then shows a TXT record: publish it at your DNS provider and select Verify. A domain belongs to one organization: the first to verify it keeps it. Personal organizations have no domains. After that, anyone who signs in with a verified email at the domain is matched to the team, new accounts and existing ones alike. The admin picks what happens for each domain. With Join automatically the person becomes a Member at sign-in. With Ask an admin a join request waits at the top of Organization → Members, where admins approve or decline it. The match happens once per person. If someone leaves, an admin removes them or declines their request, their next sign-in doesn’t add them again. Someone with a pending invitation keeps it instead. Removing a domain stops new matches and keeps the members it brought in.Group keys into workspaces
A workspace is a named group of an account’s API keys, for example one per product, environment or client. Your personal organization has workspaces just like a team. Every account has a Default workspace. It holds every key you haven’t put in another workspace. Default can’t be renamed or archived. The account API lists workspaces, creates and moves keys into them and reports spend per workspace, as Put keys in workspaces with the API shows. The switcher card at the top of the sidebar lists your accounts and then the current account’s workspaces. Below it, the sidebar always shows both groups. The workspace’s group holds Metrics, Logs, API Keys, Observability and Settings. The account’s holds Credits, Workspaces, Organization, Provisioning Keys, Privacy and Referrals. Metrics and Logs open on the workspace you are in. Their All workspaces tab shows the whole account, and This workspace goes back. A key’s history follows the key, so moving a key moves its past requests with it. Each workspace page has its own address, such asnaga.ac/dashboard/workspaces/default/api-keys for Default’s keys, with the workspace’s ID in place of default for the others. Share or bookmark it, and it opens that workspace for anyone in it; others get a 404. Opening one also makes it the workspace the Playground works in. The short addresses, such as naga.ac/dashboard/api-keys, open the workspace you picked last. Switching the workspace on a workspace page opens the same page of the new one. Your choice stays until you switch; switching to another account opens its Default.
On the Workspaces page you create workspaces and see how many keys each holds and how much they have spent. Select a workspace’s name to open it. A workspace’s Settings page changes its name, budget, members and routing strategy and archives it. Only the owner and admins manage workspaces, and each person switches between the workspaces they work in.
The Playground works in the workspace picked in the switcher card, which its sidebar shows too. Its requests show in that workspace’s Metrics and Logs and spend its budget, so switching to another workspace there moves the next request too. A key’s history moves with the key, but a Playground request stays in the workspace it was made in.
A new key goes to the workspace you are in. It belongs to the person who creates it and is disabled when they leave the organization. When the account has more than one person, admins pick the owner. It is Me, a Teammate who works in the workspace, or the Workspace itself. A workspace key has no person behind it, so a service that uses it keeps running when people come and go. Only the owner and admins move keys: Move to workspace in a key’s row menu, which members don’t see. A workspace changes nothing about how a key works on its own: the balance stays shared, and the key keeps its secret, limit and spend.
Archiving a workspace disables its keys and keeps them in it, along with its budget and spend history. Its keys can’t be turned back on there. To use one again, an admin moves it to a live workspace and enables it. The account API answers 400 to a request that enables a key in an archived workspace.
Cap spending with budgets
A budget caps what a workspace or a person spends, so you can hand keys to a team or a contractor without watching every request. It’s an amount in USD that resets every day, week or month, or never. Periods follow the same UTC calendar as a key’s limit. Once a budget is spent, paid requests with the keys it covers fail with403 credit_limit_exceeded until it resets or an admin raises it. Free models cost nothing and still work. A workspace’s budget covers the Playground in that workspace too. The balance and the keys stay as they were.
Admins set a workspace’s budget on its Settings page or from its row menu on the Workspaces page, Default included. It covers every key in the workspace. A person’s budget is set from their row menu under Members and covers every key that person created in the organization, in any workspace. Members can create keys in any workspace, so a person’s budget, not a workspace’s, is the way to cap one person. Members with the Billing role see every person’s budget, and everyone else sees their own. Only the owner sets the owner’s budget.
A request goes through only if no budget that covers its key is spent, and the key’s own credit limit still applies. Members can lower the limit on their own keys, but the budget an admin set for them holds anyway. Spend counts from the moment the budget is set, and changing its period starts the count at zero. As with a key’s limit, the check runs before each request. A request that starts with room left can take a budget past its amount, and so can several requests running at once. A new budget or a change reaches the gateway within 10 seconds.
When a budget reaches 50, 75 or 100 % of its current period, a notice at the top of every dashboard page names it. The notice shows what the budget has spent and, once it is spent, when it resets. Admins and Billing see every budget that has reached a threshold, and a member sees their own. The notice goes away when the period resets or an admin raises the budget.
Limit how long keys live
An admin can make every key of the organization expire. A leaked key, or one a departed contractor kept, then stops working on its own. Under Organization → General → API key lifetime, pick 7, 30, 90, 180 or 365 days. From then on, a key created in the organization, or given a new expiry, expires within that many days. A later or empty expiry is shortened to the limit, from the dashboard and the account API alike. The response shows the expiry the key got. Keys that already live without an expiry keep working until someone changes it. A workspace can have a shorter limit of its own, set with Set policy in its row menu on the Workspaces page. A key in that workspace expires within the shorter of the two limits. Moving a key into the workspace shortens its expiry to that limit too.Choose which models keys can use
An admin can let the organization’s keys call only the models it has approved. That keeps data with the vendors you have a contract with, or keeps a test workspace on cheap models. Under Organization → General → Model access, pick Only selected models and choose vendors, such as All Anthropic models, or single models. A vendor covers its models released later as well. The list also applies to the Playground. A workspace can narrow the list further with Set policy on its Settings page or in its row menu on the Workspaces page. A key in that workspace can call a model only when both lists allow it, so a workspace never opens a model the organization closed. The same holds for the Playground while it works there. Default has no list of its own and follows the organization. Admins of a workspace set its policy as well as the organization’s owner and admins. A request for a model outside the lists fails with403 model_not_allowed before it reaches any provider, and costs nothing. GET /v1/models called with the key lists only the models it may use. A change reaches the gateway within 10 seconds.
Choose who works in a workspace
The owner and admins of the account administer every workspace. Billing has no keys in any workspace and sees the spend of all of them on Account → Metrics. A member works in Default and in the workspaces an admin adds them to. The switcher, the API Keys page and the key form show a member only those. To add someone, open the workspace’s Settings and select Manage members, or use the same item in its row menu on Workspaces. Pick the person’s role there. Invite them to the organization first: everyone in it is listed, and the owner and admins show as administering it already.
A member who administers a workspace also opens Workspaces, Metrics and Logs, which show only the workspaces they administer. Only the owner and admins of the account create, rename and delete workspaces. Taking a person out of a workspace disables the keys they created there and passes them to its admins, as when someone leaves the organization.