DocsOrganizations
Members
Manage INFRO organization members and roles in the console, owner, admin, developer and analyst access, plus SSO and SCIM from the Business plan.
INFRO is in private early access. Running these examples requires an early-access account, an active trial or subscription entitlement, and your own provider connection. Self-serve purchasing is not generally open. See Early access.
An organization owns its software subscription, billing contact, provider connections, projects, gateway keys and policies. Invite members and manage their roles through the signed-in console.
Organizations
One INFRO account can own or belong to any number of organizations. Each is fully separate: its own members, provider connections, keys, projects, usage, audit log, trial, subscription, billing contact and logo. Switch between them from the organization menu in the console; every screen then shows only the organization you switched to.
Signing up creates an account, not an organization. After verifying your email you name the organization and say how many people will use it: Just me makes an individual organization, any larger answer a company. The type is not fixed — inviting a teammate turns an individual organization into a company, and an owner or admin can switch it in Organization settings. Nothing is created while you fill this in or compare plans; the organization is written when you continue to checkout, and it appears in your organization list once its subscription starts. If you signed up from an invitation, accepting it takes you straight into the invited organization and no personal organization is created; when that organization's setup is unfinished and your role can do its next step, setup opens there.
Roles
| Role | Purpose |
|---|---|
| Owner | Exactly one per organization. Organization administration and billing — the only role that can set billing details, start a trial, subscribe or open the billing portal — plus membership, ownership transfer and access management. |
| Admin | Administrative management of the organization's profile, logo, members, invitations, projects, keys and policies, except the organization-wide spend limit and allowing unpriced traffic under blocking budgets, which are the owner's. Can view billing status but cannot purchase, change or cancel a plan, and cannot change or remove the owner. |
| Developer | Create, view and revoke gateway keys, call models, and read usage, request history, policies and the audit log. Cannot change policies, members or billing. |
| Analyst | Read usage, request history, policies and the audit log. Cannot create keys or call models. |
| Finance | Reads billing status and every cost figure, sets budgets — the monthly target, the budget cycle day, project and member spend limits and end-customer caps — maintains cost centers and their rules, closes and corrects monthly statements, and uploads customer revenue. Cannot set the organization-wide hard cap (the owner's), create keys, change providers, routes or other policies, or call the API. |
Project access
An owner or admin can limit a developer or analyst to some projects, from Project access in the member's row menu on Settings → Members. A member limited to projects reads those projects' requests, analytics, async jobs and findings, and manages the gateway keys in them: every key they create or move belongs to one of their projects. Everything organization-wide is closed to them, including budgets, provider and routing settings, policies, members, the audit log, the summary and the monthly report, the MCP gateway, and connection tests in the Playground. The gateway enforces this on every request, and a change applies to the member's next request.
Owners, admins and finance members always see the whole organization. A list kept for a member promoted to one of those roles stops applying, and applies again if they return to developer or analyst. An archived project stays in the list and matches nothing, so access never widens because a project went. The weekly summary and the monthly report are not sent to a member limited to projects, and AI assistants they connect through the MCP server are refused.
Invitations and offboarding
Use the console to invite a member, change a role, revoke a pending invitation or remove access. Review gateway keys and project ownership when a member leaves. Seat allowances include active members and outstanding invitations.
Ownership is never assigned through a role change. The owner transfers it from Settings → Members to an existing member with a verified email; in one step the new owner becomes owner and the previous owner becomes admin. The owner cannot leave until ownership has been transferred, and nobody — including admins — can remove or demote the owner. Any other member can leave an organization at any time.
Deleting an organization
Only the owner can delete an organization, from Settings → General → Delete organization. You type the organization's name to confirm, and if this session has not confirmed your identity in the last ten minutes the console asks for your password, authenticator code, recovery code or passkey first. Deletion is immediate and cannot be undone: projects, provider connections, routes, budgets, alerts, request history, members and invitations are removed, and the organization's gateway keys and management tokens stop working at once. The INFRO subscription is cancelled at the payment processor first; if that fails, nothing is deleted. Your provider accounts belong to you and are not touched — revoke the credentials you connected with each provider if you no longer need them. Every member is emailed. Deleting the organization does not reset the one free trial per person. An organization suspended by INFRO cannot be deleted from the console; contact support.
Authentication boundary
Organization management uses console sessions and the supported membership controls. The previously documented /v1/org/members and /v1/org/invites gateway-key APIs are not implemented. Do not send an INFRO inference key to those paths.
Directory integration
SAML/OIDC single sign-on and SCIM directory provisioning are included from the Business plan. See SSO and SCIM to set one up.
Budget and model policies are independent of sign-in method. See Spend controls, Model allowlists, and Billing.