Loading documentation
Research Desk
Deal Center
Library
Loading
Corbis organizations let one admin buy a team subscription, invite users by email, and manage access, policy, and billing from a single account.
This guide explains what happens when a team is created, how seats and credits are counted, how invitations are accepted or declined, how single sign-on and directory provisioning work, and what happens if an invited user already has a personal subscription.
For current plan details, see Plans & Pricing.
The organization admin is the billing owner for the team subscription. One account can administer up to 5 organizations.
In practice, the admin can:
Two important rules:
Team management lives at Settings → Team. Billing details for your own account live at Settings → Billing.
Academic organizations are billed on the Academic tier. Corporate organizations are billed on Basic or Pro. An organization cannot switch between the academic and corporate tier families in-app.
Admins have two ways to change billing:
A Switch to annual billing or Switch to monthly billing button appears next to the portal link when the organization pays by card and Corbis can read the current cadence. Changing cadence goes through that dedicated control rather than the plan selector, because a plan change and a cadence change are handled separately. Organizations billed by invoice (for example NET-30) cannot change plans or cadence through the hosted portal; those admins use the in-app controls instead.
Credit allowances are monthly regardless of billing cadence. An annual organization is refilled every month for twelve months rather than receiving a year of credits up front.
Admins can also Cancel subscription from Settings → Team. Cancelling schedules the subscription to end at the end of the paid period, and a Resume subscription button appears until that date passes.
Total capacity is the paid seat count plus any complimentary seats. Complimentary seats are granted by Agentic Assets and are not billed through Stripe; paid seats are the quantity on the Stripe subscription. Total capacity is between 1 and 250.
These count as occupied seats:
Sending an invitation reserves a seat for that person until they join, you remove the invitation, it expires, or they decline.
Declined invitations do not use a seat. Someone who declined may still appear on your team list so you can send a new invitation to the same address when you are ready. Expired invitations stop holding seats; Corbis cleans them up nightly, and you can invite that person again.
To reduce abuse, sending invitations is rate-limited per organization (up to 20 new invite or resend attempts per hour in the current product). If you hit the limit, wait a short time and try again.
Invitations are sent by email and expire after 7 days.
If an invitation is not accepted in time:
If someone declines:
By default, members can see the full team roster. The admin can turn off Show member list to team so that non-admin members only see their own row. Admins still see the full list. Use this when you want to limit visibility of who else is on the team.
An admin can hand off billing and team ownership without contacting support. In the member list, choose Make organization admin on an active member and confirm Transfer admin role?.
The transfer takes effect immediately. The previous admin keeps their seat and membership but loses billing and team management access, so make sure the new admin is the right person before confirming. If another change to the organization lands at the same time, the transfer is refused and you can retry.
Two organization-wide settings in Settings → Team apply to every active member working in that organization context.
When Force zero data retention is on, covered AI requests made while the organization is active force request-level zero data retention through Vercel AI Gateway, which asks Gateway to route only to compliant providers and fallbacks. This applies to active team members under that organization context even if the workspace-level default is off.
Two effects members will notice:
Turning it off means the organization stops forcing the setting and covered requests use the app default. This setting does not verify requests made outside AI Gateway.
When Force stable output is on, Corbis pins generation to its most repeatable setting for every member request in that organization, regardless of each member's own composer setting. Use this when your team needs answers to be as reproducible as possible across runs. Members can still see that stable output was applied on each response.
Admins can export two organization reports from Settings → Team. Both cover a date window of up to 180 days and export as CSV or JSON.
Both reports are scoped to each member's organization membership period, so they do not reach back before someone joined.
Corbis accounts can sign in with email and password, with Google, LinkedIn, or GitHub, or through your organization's identity provider. Organizations that need centralized control can add SAML single sign-on and SCIM user provisioning.
Setting up a connection is handled by the Agentic Assets team, not self-serve. Contact us to register your identity provider and the email domains that should route to it. Corbis supports service-provider-initiated SAML, which means sign-in starts from Corbis. A tile in your identity provider's dashboard should point at the Corbis SSO entry point rather than sending an unsolicited assertion.
Each email domain your provider asserts must be registered on the connection. If your provider asserts a subdomain (for example warrington.university.edu when users type university.edu), that subdomain needs to be registered too, or sign-in is refused.
Once configured, an organization is set to one of two enforcement modes:
SCIM lets your identity provider create, update, and deactivate Corbis members automatically. Admins manage it in Settings → Team: copy the SCIM base URL, generate or rotate a bearer token (shown once), and revoke it when needed. The organization must be active to issue a token.
Current scope, stated plainly:
Pending team invitations appear in several places:
If you lose the email, open Settings → Team to review and respond. You do not need a paid plan to see and respond to a pending invitation.
To accept successfully, all of the following must be true:
If any of those checks fail, you cannot accept until it is fixed.
Invitation links take you to Settings → Team and open a review dialog. Corbis loads a preview of what joining means: the organization name, plan context, and, if you have a personal subscription, what changes about your billing. Nothing is finalized until you confirm. Simply opening the link does not add you to the team.
Corbis treats this as a transition, not an instant swap. The confirmation step is required, and the button reads Join Team and End Personal Plan at Renewal.
Before you confirm, the preview explains that:
Corbis does not cancel your personal subscription the moment you confirm. It is scheduled for period end as described.
This confirmation also applies if your personal subscription is on a trial, past due, or unpaid, not only when it is fully paid and active.
Some organizations require single sign-on. You must complete SSO with an identity that satisfies the organization's policy before acceptance can finish. If SSO is required and your session does not satisfy it, acceptance stays blocked until you sign in through that provider. Your admin or IT team can confirm the expected provider.
You can decline a pending invitation from Settings → Team. If you decline:
This is the most nuanced part of organization billing, and Corbis handles it explicitly when you confirm joining from a paid personal account.
Corbis re-checks your live subscription state at the moment you confirm rather than trusting the earlier preview. If the two disagree, acceptance stops and asks you to review again rather than committing a change it cannot complete.
When a paid personal user confirms joining an organization:
The personal snapshot includes:
Until the personal subscription actually ends, you keep the higher tier of:
That means:
Chat usage during the overlap draws from the organization credit pool when the organization has one set up. Your frozen personal balance is held for a possible restore rather than spent.
Once the personal billing period ends, you continue on the organization tier only.
If you are already an active member and you are still paying for a personal plan alongside your seat, Settings → Billing offers an explicit action to end the personal plan at the end of its paid term while keeping your organization seat.
This action is available to any active member, including the person who created the organization. It confirms the exact personal subscription it is ending, it never touches your membership or seat, and your paid personal term runs to its normal end date.
If you lose organization access before the original personal billing period would have ended, Corbis attempts to restore the frozen personal state, so a personal plan you already paid for is not lost.
Restore is best effort, not guaranteed. If the restore cannot be completed cleanly, Corbis marks the membership as needing repair and alerts the team rather than silently leaving the account in a wrong state. Recovery in that case is handled by a person, not automatically, so contact your admin or Corbis support if you see a repair message.
In Corbis, these are related, but they are not always the same thing.
For most organization members:
For users in the personal-to-organization overlap window:
Only the admin sees the organization credit pool balance, on the Team tab. Every member sees their own usage on the Billing tab, which reflects the organization pool when the organization is paying.
The organization does not become usable until billing is active. Organizations still waiting on payment do not get team access until payment is confirmed, and invitations cannot be sent or accepted in that state.
If an active organization later has a payment failure, Corbis allows a short grace window while payment is retried. In the current implementation, that grace period is up to 7 days.
If the organization is cancelled but still has paid time remaining, members keep access through the paid-through date. Corbis then removes organization access after that grace window ends.
A suspended organization does not grant access and cannot add members. Contact Corbis support to resolve it.
When a member is removed:
The same applies when a member is deactivated through SCIM.
Yes, you can belong to more than one organization.
Corbis uses a preferred active organization so the app can decide which organization context to use for organization-based billing, usage, and policy.
If you belong to multiple organizations, check which one is active before doing work that should count against team usage. Organization policies such as forced zero data retention and forced stable output follow the active organization, so switching context can change which models you see.
Separately, one account can administer up to 5 organizations.
No. The link opens Settings → Team and a review dialog. You must confirm to join.
Yes. In Settings → Team, you can decline. You will not be added to the team.
Yes. A declined invitation does not count toward the team's seats.
Yes. The admin is an active organization member and counts toward the seat total.
Yes. A non-expired invitation that has been sent but not accepted reserves a seat until someone joins, you remove it, it expires, or the invitee declines.
No. The acceptance flow checks the invited email address directly.
Your organization's admin may have turned off the full roster for non-admins. In that case you see only your own row. Admins still see the full list.
Your organization may have turned on forced zero data retention, which limits selection to models that meet that policy.
No. If you already have a paid personal plan, Corbis schedules it to cancel at the end of the current billing period after you confirm joining.
You keep the higher personal tier until the personal billing period ends. After that, you continue on the organization tier.
Corbis attempts to restore the frozen personal state from when you joined the organization. If that restore cannot complete, Corbis flags the account for repair rather than leaving it in a wrong state.
With email and password, with Google, LinkedIn, or GitHub, or through your organization's identity provider if SSO is configured.
Yes. Both are supported today. Connection setup is handled by the Agentic Assets team rather than a self-serve configuration screen, so contact us to get started. Admins manage the SCIM token themselves once the connection exists.
Yes. An admin can transfer the admin role to any active member from Settings → Team. The change takes effect immediately.
Yes. Organizations can be billed monthly or annually, and card-paying admins can switch cadence from Settings → Team.
For admins:
For invited users:
Corbis organizations let one admin buy a team subscription, invite users by email, and manage access, policy, and billing from a single account.
This guide explains what happens when a team is created, how seats and credits are counted, how invitations are accepted or declined, how single sign-on and directory provisioning work, and what happens if an invited user already has a personal subscription.
For current plan details, see Plans & Pricing.
The organization admin is the billing owner for the team subscription. One account can administer up to 5 organizations.
In practice, the admin can:
Two important rules:
Team management lives at Settings → Team. Billing details for your own account live at Settings → Billing.
Academic organizations are billed on the Academic tier. Corporate organizations are billed on Basic or Pro. An organization cannot switch between the academic and corporate tier families in-app.
Admins have two ways to change billing:
A Switch to annual billing or Switch to monthly billing button appears next to the portal link when the organization pays by card and Corbis can read the current cadence. Changing cadence goes through that dedicated control rather than the plan selector, because a plan change and a cadence change are handled separately. Organizations billed by invoice (for example NET-30) cannot change plans or cadence through the hosted portal; those admins use the in-app controls instead.
Credit allowances are monthly regardless of billing cadence. An annual organization is refilled every month for twelve months rather than receiving a year of credits up front.
Admins can also Cancel subscription from Settings → Team. Cancelling schedules the subscription to end at the end of the paid period, and a Resume subscription button appears until that date passes.
Total capacity is the paid seat count plus any complimentary seats. Complimentary seats are granted by Agentic Assets and are not billed through Stripe; paid seats are the quantity on the Stripe subscription. Total capacity is between 1 and 250.
These count as occupied seats:
Sending an invitation reserves a seat for that person until they join, you remove the invitation, it expires, or they decline.
Declined invitations do not use a seat. Someone who declined may still appear on your team list so you can send a new invitation to the same address when you are ready. Expired invitations stop holding seats; Corbis cleans them up nightly, and you can invite that person again.
To reduce abuse, sending invitations is rate-limited per organization (up to 20 new invite or resend attempts per hour in the current product). If you hit the limit, wait a short time and try again.
Invitations are sent by email and expire after 7 days.
If an invitation is not accepted in time:
If someone declines:
By default, members can see the full team roster. The admin can turn off Show member list to team so that non-admin members only see their own row. Admins still see the full list. Use this when you want to limit visibility of who else is on the team.
An admin can hand off billing and team ownership without contacting support. In the member list, choose Make organization admin on an active member and confirm Transfer admin role?.
The transfer takes effect immediately. The previous admin keeps their seat and membership but loses billing and team management access, so make sure the new admin is the right person before confirming. If another change to the organization lands at the same time, the transfer is refused and you can retry.
Two organization-wide settings in Settings → Team apply to every active member working in that organization context.
When Force zero data retention is on, covered AI requests made while the organization is active force request-level zero data retention through Vercel AI Gateway, which asks Gateway to route only to compliant providers and fallbacks. This applies to active team members under that organization context even if the workspace-level default is off.
Two effects members will notice:
Turning it off means the organization stops forcing the setting and covered requests use the app default. This setting does not verify requests made outside AI Gateway.
When Force stable output is on, Corbis pins generation to its most repeatable setting for every member request in that organization, regardless of each member's own composer setting. Use this when your team needs answers to be as reproducible as possible across runs. Members can still see that stable output was applied on each response.
Admins can export two organization reports from Settings → Team. Both cover a date window of up to 180 days and export as CSV or JSON.
Both reports are scoped to each member's organization membership period, so they do not reach back before someone joined.
Corbis accounts can sign in with email and password, with Google, LinkedIn, or GitHub, or through your organization's identity provider. Organizations that need centralized control can add SAML single sign-on and SCIM user provisioning.
Setting up a connection is handled by the Agentic Assets team, not self-serve. Contact us to register your identity provider and the email domains that should route to it. Corbis supports service-provider-initiated SAML, which means sign-in starts from Corbis. A tile in your identity provider's dashboard should point at the Corbis SSO entry point rather than sending an unsolicited assertion.
Each email domain your provider asserts must be registered on the connection. If your provider asserts a subdomain (for example warrington.university.edu when users type university.edu), that subdomain needs to be registered too, or sign-in is refused.
Once configured, an organization is set to one of two enforcement modes:
SCIM lets your identity provider create, update, and deactivate Corbis members automatically. Admins manage it in Settings → Team: copy the SCIM base URL, generate or rotate a bearer token (shown once), and revoke it when needed. The organization must be active to issue a token.
Current scope, stated plainly:
Pending team invitations appear in several places:
If you lose the email, open Settings → Team to review and respond. You do not need a paid plan to see and respond to a pending invitation.
To accept successfully, all of the following must be true:
If any of those checks fail, you cannot accept until it is fixed.
Invitation links take you to Settings → Team and open a review dialog. Corbis loads a preview of what joining means: the organization name, plan context, and, if you have a personal subscription, what changes about your billing. Nothing is finalized until you confirm. Simply opening the link does not add you to the team.
Corbis treats this as a transition, not an instant swap. The confirmation step is required, and the button reads Join Team and End Personal Plan at Renewal.
Before you confirm, the preview explains that:
Corbis does not cancel your personal subscription the moment you confirm. It is scheduled for period end as described.
This confirmation also applies if your personal subscription is on a trial, past due, or unpaid, not only when it is fully paid and active.
Some organizations require single sign-on. You must complete SSO with an identity that satisfies the organization's policy before acceptance can finish. If SSO is required and your session does not satisfy it, acceptance stays blocked until you sign in through that provider. Your admin or IT team can confirm the expected provider.
You can decline a pending invitation from Settings → Team. If you decline:
This is the most nuanced part of organization billing, and Corbis handles it explicitly when you confirm joining from a paid personal account.
Corbis re-checks your live subscription state at the moment you confirm rather than trusting the earlier preview. If the two disagree, acceptance stops and asks you to review again rather than committing a change it cannot complete.
When a paid personal user confirms joining an organization:
The personal snapshot includes:
Until the personal subscription actually ends, you keep the higher tier of:
That means:
Chat usage during the overlap draws from the organization credit pool when the organization has one set up. Your frozen personal balance is held for a possible restore rather than spent.
Once the personal billing period ends, you continue on the organization tier only.
If you are already an active member and you are still paying for a personal plan alongside your seat, Settings → Billing offers an explicit action to end the personal plan at the end of its paid term while keeping your organization seat.
This action is available to any active member, including the person who created the organization. It confirms the exact personal subscription it is ending, it never touches your membership or seat, and your paid personal term runs to its normal end date.
If you lose organization access before the original personal billing period would have ended, Corbis attempts to restore the frozen personal state, so a personal plan you already paid for is not lost.
Restore is best effort, not guaranteed. If the restore cannot be completed cleanly, Corbis marks the membership as needing repair and alerts the team rather than silently leaving the account in a wrong state. Recovery in that case is handled by a person, not automatically, so contact your admin or Corbis support if you see a repair message.
In Corbis, these are related, but they are not always the same thing.
For most organization members:
For users in the personal-to-organization overlap window:
Only the admin sees the organization credit pool balance, on the Team tab. Every member sees their own usage on the Billing tab, which reflects the organization pool when the organization is paying.
The organization does not become usable until billing is active. Organizations still waiting on payment do not get team access until payment is confirmed, and invitations cannot be sent or accepted in that state.
If an active organization later has a payment failure, Corbis allows a short grace window while payment is retried. In the current implementation, that grace period is up to 7 days.
If the organization is cancelled but still has paid time remaining, members keep access through the paid-through date. Corbis then removes organization access after that grace window ends.
A suspended organization does not grant access and cannot add members. Contact Corbis support to resolve it.
When a member is removed:
The same applies when a member is deactivated through SCIM.
Yes, you can belong to more than one organization.
Corbis uses a preferred active organization so the app can decide which organization context to use for organization-based billing, usage, and policy.
If you belong to multiple organizations, check which one is active before doing work that should count against team usage. Organization policies such as forced zero data retention and forced stable output follow the active organization, so switching context can change which models you see.
Separately, one account can administer up to 5 organizations.
No. The link opens Settings → Team and a review dialog. You must confirm to join.
Yes. In Settings → Team, you can decline. You will not be added to the team.
Yes. A declined invitation does not count toward the team's seats.
Yes. The admin is an active organization member and counts toward the seat total.
Yes. A non-expired invitation that has been sent but not accepted reserves a seat until someone joins, you remove it, it expires, or the invitee declines.
No. The acceptance flow checks the invited email address directly.
Your organization's admin may have turned off the full roster for non-admins. In that case you see only your own row. Admins still see the full list.
Your organization may have turned on forced zero data retention, which limits selection to models that meet that policy.
No. If you already have a paid personal plan, Corbis schedules it to cancel at the end of the current billing period after you confirm joining.
You keep the higher personal tier until the personal billing period ends. After that, you continue on the organization tier.
Corbis attempts to restore the frozen personal state from when you joined the organization. If that restore cannot complete, Corbis flags the account for repair rather than leaving it in a wrong state.
With email and password, with Google, LinkedIn, or GitHub, or through your organization's identity provider if SSO is configured.
Yes. Both are supported today. Connection setup is handled by the Agentic Assets team rather than a self-serve configuration screen, so contact us to get started. Admins manage the SCIM token themselves once the connection exists.
Yes. An admin can transfer the admin role to any active member from Settings → Team. The change takes effect immediately.
Yes. Organizations can be billed monthly or annually, and card-paying admins can switch cadence from Settings → Team.
For admins:
For invited users: