Research Desk
Deal Center
Library
Corbis organizations let one admin buy a team subscription, invite users by email, and manage access from a single billing account.
This guide explains what happens when a team is created, how seats are counted, how invitations are accepted or declined, and what happens if an invited user already has a personal subscription.
If you want current plan details, see Plans & Pricing.
The organization admin is the billing owner for the team subscription.
In practice, that means the admin can:
Two important rules:
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 over time, 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 this off 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.
Organization admins can turn on Force zero data retention from Settings -> Team.
When this is on, covered AI requests made while the organization is active force Vercel AI Gateway request-level ZDR. This asks Gateway to route only to ZDR-compliant providers and fallbacks. The setting applies to active team members under that organization context, even if the workspace-level default is off.
Turning it off means the organization stops forcing the setting and covered requests use the app default. This does not verify BYOK or direct-provider requests outside AI Gateway. invokeSkill uses Anthropic-native code execution directly, so Corbis blocks that tool when the active organization forces zero data retention.
Pending team invitations show in Settings (Team tab). You may also see a reminder elsewhere in the app (for example, a one-time prompt when you sign in). If you lose the email, open Settings → Team to review and respond.
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. Corbis loads a preview of what joining means (organization name, plan context, and—if you have a personal subscription—what changes to your billing). Nothing is finalized until you confirm in that flow. Simply opening the link does not add you to the team.
Corbis treats this as a transition, not an instant swap.
Before you confirm, the preview explains that:
Corbis does not cancel your personal subscription the moment you click confirm—it is scheduled for period end as described.
Some organizations require single sign-on (SSO). You must complete SSO with an identity that satisfies the organization’s policy before acceptance can finish. If SSO is required but your session does not meet it, acceptance stays blocked until you sign in correctly (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.
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:
Once the personal billing period ends, you continue on the organization tier only.
If you lose organization access before the original personal billing period would have ended, Corbis attempts to restore the frozen personal state.
That restore path is designed to preserve the value of a personal plan that had already been paid for.
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:
The organization does not become usable until billing is active. Organizations still waiting on payment do not get team access until payment is confirmed.
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.
When a member is removed:
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 and usage.
If you belong to multiple organizations, check which one is active before doing work that should count against team usage.
No. The link opens Settings → Team and a preview. 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 may only see your own row. Admins still see the full list.
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.
For admins:
For invited users: