Organizations
An organization is the top-level container for a team’s wylon usage. It owns billing and members. Every user belongs to at least one organization; most teams only need one.
Hierarchy
Resources are managed under your organization.
Organization # billing, members
├─ API keys # auth tokens
└─ Batch jobs # batch jobs and input/output files- Organization — the billing and membership boundary. One plan, one payment method, one invoice.
- Resources — API keys and batch jobs belong to the organization.
Members & roles
Invite teammates by email. Each member has an organization-wide role.
| Role | Can |
|---|---|
| Admin | Everything: manage members, billing and payment methods, create and use API keys, call inference, plus transfer the admin role and delete the organization. |
| Member | Create and use API keys, call inference, and view their own usage. |
group
Invitations are sent via email and expire after 7 days. Invitees must sign in with the exact
email address you entered — OAuth accounts (Google, GitHub) must have that address verified.
Leaving or deleting
A member can leave an organization from their personal settings. An admin cannot leave unless at least one other admin remains, or after transferring the admin role to another member. Deleting an organization is a two-step confirmation and immediately disables all keys and cancels in-flight batch jobs — back up important data first.
