Organizations, Billing Groups, and Pro Seats
How organization rosters, roles, invitations, shared AI-credit wallets, org-billed usage, Pro seat subscriptions, and seat assignments work.
Organizations, Billing Groups, and Pro Seats
Where you see this in the app
Organization controls live at Settings -> Organizations.
Use this page when a team, client account, lab, publisher, or company should share billing infrastructure without turning the organization into the owner of every account asset.
The page covers:
- organization creation,
- organization members and roles,
- email invitations and invitation tokens,
- organization AI-credit wallets and top-ups,
- org-billed usage and wallet activity,
- organization Pro seat subscription capacity,
- local Pro seat assignments.
What an organization is
An organization is a billing group and roster, not a replacement account.
That means organization membership can help a team pay for AI usage or assign Pro seats, but it does not move personal identity, content ownership, followers, custom domains, API tokens, webhooks, or Stripe Connect payout identity away from the user accounts that own them.
This boundary is important:
| Area | Owner |
|---|---|
| Public profile and followers | User account |
| Posts and profile workspace authorship | User account |
| Stripe Connect payout identity | User account |
| Custom domains | User account |
| PATs and webhooks | User account |
| Shared AI-credit wallet | Organization billing account |
| Org Pro seat capacity | Organization billing subscription |
Peer-review access is also separate. A conference or workspace may use an organization as a sponsor billing source, but reviewers, chairs, authors, and program committee users still need the relevant peer-review role or assignment.
Roles, members, and invites
The organization page shows every organization you belong to, your role, and the member count.
Typical roles are:
| Role | Plain-English meaning |
|---|---|
Owner | Full organization control, including settings and archive |
Admin | Manage the organization and members |
Billing admin | Manage billing-oriented actions such as wallet top-ups, usage review, and seats |
Member | Belongs to the organization but has limited management authority |
Managers can invite users by email and choose the invitee role. If email delivery is configured, GetPaidX sends the invitation. The page can also show a token or accept URL so the invite can be shared manually.
Accepted members appear in the members list. Owners or admins can update roles or remove members when their access should change.
Organization wallets and usage
Organizations can have their own AI-credit wallet.
Use the organization wallet when workspace or model usage should be paid by the team instead of by one person's personal wallet.
The page shows:
| UI area | What it means |
|---|---|
| Wallet summary | Available organization credit balance |
| Top-up packages | Stripe Checkout options that add credits to the organization wallet |
| Usage events | Recent org-billed workspace/model activity |
| Wallet transactions | Credit purchases, debits, and balance changes |
Post workspace launches normally start with personal/default billing. When you are eligible to spend organization credits, the post workspace config can show a Bill workspace to selector. Choosing an organization asks GetPaidX to charge accepted workspace usage to that organization's wallet.
If org-billed usage does not work, check your role, the organization's spend policy, wallet balance, and whether you are allowed to start that workspace in the first place.
Pro seat subscriptions
Organization Pro seats are subscription-backed capacity.
The page can show:
| Label | What it means |
|---|---|
Paid seats | How many organization Pro seats the subscription currently provides |
Assigned | How many active members currently have a Pro seat |
Available | Paid seats not yet assigned |
Suspended | Assignments that are not currently active |
Subscription | Current subscription status and renewal timing when available |
Billing managers can start seat checkout with a chosen quantity. If a subscription already exists, they can open the billing portal to manage the subscription.
Stripe-hosted checkout and portal pages handle the payment/subscription side. GetPaidX then reflects the reconciled seat capacity back in the organization page.
Seat assignments and suspension
Seat assignment is local to the organization roster.
After the organization has active seat capacity, a billing manager can assign a Pro seat to an active member. The member then receives Pro through that organization seat while the assignment is active.
A member row can show:
| Status | Meaning |
|---|---|
Active Pro seat | The member currently receives Pro via this organization |
No Pro seat | The member belongs to the organization but does not have an assigned Pro seat |
Suspended seat | A previous assignment is inactive because subscription capacity/status no longer supports it |
Revoked seat | A manager manually removed the assignment |
Suspension can happen when the organization subscription is no longer active or when seat quantity is reduced below the number of active assignments. Revoking a seat removes the member's organization-provided Pro entitlement but does not remove the member from the organization.
Related docs
Previous
Programmatic API Catalog and Token Scopes
How to use personal access tokens, scope groups, and the live API catalog when automating GetPaidX from scripts or workspace agents.
Next
Account Delegation and Acting on Behalf
How trusted delegates accept invitations, start and stop acting sessions, use baseline and payout scopes, and understand direct-session-only boundaries.