Документация доступна только на английском языке.
Organizations
Members and roles, the Primary Owner, invitations and invite links, seats, signing someone out, requests for more usage, the team's activity, the organization's policy, the activity log, and exporting the organization's records.
Everything in the cloud belongs to an organization. Your sessions, keys, plan and usage are all part of one. Everyone starts with a personal organization. A team creates one organization and invites its members.
Roles
| Role | Can |
|---|---|
| Primary Owner | Everything owners can, and hand the organization over or export its records. Nobody can remove them or change their role |
| Owner | Everything admins can, for admins as well as members, and the money and the rules: the plan, seats and payment, budgets, members' requests for more usage, the organization's policy, and making someone an owner |
| Admin | Invite people; remove members, change their roles or sign them out everywhere; read the activity log and the team's activity |
| Member | Use the organization's plan and models, see their own usage, and ask the owners for more |
Every organization has one Primary Owner: whoever created it, until they hand it over. Other owners, admins and members can leave at any time. The Primary Owner hands the organization over first, before leaving it or deleting their account.
Handing the organization over
The Primary Owner will be able to hand the organization to another member, confirmed from their own email so that an open or stolen session alone can't give it away. This is coming soon.
Inviting people
Admins invite people under Account → Organization: type or paste one address or many, with commas, semicolons, spaces or new lines between them, pick a role, and invite. Each invitation shows in the pending list with its link: copy it and send it to the person yourself. It opens a page where they accept or decline; someone without an account creates one there, with the address the invitation went to. You can cancel a pending invitation at any time.
Everyone on the list needs a free seat. If there aren't enough, nothing is sent and the form says how many seats are missing; owners can add them from there.
On the Team plan every member is a seat, and billing follows the member count. Added seats are prorated. Removed seats come off at the next renewal.
Invite link
On Team and Enterprise, admins can make an invite link instead. Anyone who opens it joins as a member while there's a free seat: signed in, with one button; signed out, they're asked to sign in first. Someone without an account asks an admin for a personal invitation, which lets them create one. A link works for 90 days. New link stops the old one at once, and Turn off ends it. When someone finds the team full through the link, Account → Organization says so until there's room again.
Signing someone out everywhere
If a laptop is lost or someone leaves in a hurry, Sign out everywhere… in their row's menu ends their sign-ins on every device and browser, disconnects the computers they connected to this organization, and stops the API keys they made in it. Nothing on their computers is deleted. Admins can sign out members; owners can sign out anyone but the Primary Owner. The same person can be signed out this way only a few times an hour.
Requests for more usage
When owners give members a monthly budget for Nib models, a member who reaches it can ask for more: Request more usage on the limit card in a session, or under Account → Usage. They can add an amount and a note. Owners see waiting requests at the top of Account → Organization. Approve sets the member's new monthly budget, and Decline can say why. Members can always switch to their own provider keys instead.
Decided requests are kept for 1 year. The organization's policy can turn requests off.
The organization's library
Under Account → Policy → Library, owners choose whether members install anything from the Hub or only what the organization provides. With the library only, an item the organization doesn't provide shows Request in Customize: the member can add a note, and it reads Requested until an owner answers. Owners see these at the top of Customize and in Account → Organization → Requests: Add to library makes the item available for members to install, Decline can say why, and Block makes it unavailable, so nobody asks for it again. Owners can also add an item from its page in Customize, and change or remove items in the policy. Each change is a new version of the policy, and the member sees the answer in Customize.
Customize is where this applies today: it offers members the organization's items and Request for the rest. Members' computers don't check installs against the library yet, so an extension the agent proposes, or one added outside Customize, isn't held to it.
Members publish what they make to the organization from Customize → Publish, with Publish to Acme. Under Publishing to the organization, owners choose when it reaches members: never, after an owner reviews it, or straight away. With a review, the version waits in Account → Organization → Requests with its access grade and what the Hub's checks found: Read files shows what's in it, Add to library publishes it to the organization, and Ask for changes sends it back with a note. In every mode, a version the Hub's own checks hold or reject stays held or rejected, and owners see why.
Team activity
On Team and Enterprise, admins and owners see how the team works with the agent under Account → Usage → Activity: who was active, sessions, file edits and lines changed per member, and the commands used most, beside what the team spent. Members' computers report counts only, never code, prompts, file names or session titles, and commands someone wrote for their own project count together as one. Export activity downloads a CSV with one row per day and member. Counts are kept for 400 days. Owners can turn activity counts off in the policy; while they're on, members see so in Account → Organization.
Policy
Owners set what members can use under Account → Policy, and every member can read it. Each change saves at once as a new version, and History shows who changed what and can restore an earlier version.
- What members can use: Nib models (on, only through providers that keep nothing, or off), remote control from the web (the phone is coming soon), cloud sessions (coming soon), Nib Crew, web search (with any provider or key), and sharing artifacts by link. Turning sharing off stops new links; links already shared stay open until their owners close them. Turning web search off covers the agent's own search; search tools an extension adds (an MCP server) aren't covered by it.
- Code stays on our computers: no session content leaves the organization's computers, not even encrypted. Turning it on deletes what was synced before, and turns off cloud sessions and artifact links. Nib models then run only through providers that keep nothing, and remote control only if you allow it.
- Activity counts: whether members' computers report the team's activity. Turned off, they count and report nothing; earlier counts stay.
- Members' computers: the oldest version of Nib that can start work, and whether a computer checks the policy before work starts each time it starts. A computer that's too old, or that can't check the policy when it must, finishes what it's running and starts nothing new until it's updated or back online.
- Requests: whether members can ask for more usage, and for library items.
- Library: whether Customize offers members anything from the Hub or only what the organization provides, how members publish to the organization, and the organization's items, each available to install or not available (the organization's library).
Members' computers apply the policy too. They check it every hour and as soon as it changes, and keep applying the last policy they checked while they're offline.
When something is off because of the policy, the app says so and names what the organization turned off.
Activity log
Account → Organization → Activity log shows the organization's security events, newest first. It records who did each thing (a person, with an API key or not, or the payment service) and when:
- sign-ins;
- API keys, computers and device keys added or removed;
- invitations, people joining or leaving, and role changes;
- plan and billing changes, invoices and prepaid credit;
- policy changes, with what each changed;
- requests for more usage and their decisions;
- invite links, signing someone out everywhere, handing the organization over, and exports.
Owners and admins can read it. Export downloads it as JSON lines, for your own records or a SIEM. Plans show the last 30 days, and Enterprise shows every entry. Entries are kept for 1 year.
When a member deletes their account, the organization keeps a record that it happened, without their name, email or sign-in details.
Exporting the organization's records
The Primary Owner can download the organization's records under Account → Your data: Export prepares a zip, and its download appears there when it's ready. It downloads only from your own signed-in session, for 24 hours, and is then deleted. It holds the members and invitations, the policy and its history, budgets and requests, usage and activity, the activity log, and the computers, API keys and GitHub connections, never their secrets.
Members' sessions aren't in it: each member exports their own under Account → Your data. A member who turns on end-to-end encryption under Settings → Account syncs sessions the cloud can't read.