An organization groups teams. Each team has its own wallet, projects, agents and members, so several Wiro accounts can share credit and API keys. Every account keeps its Personal workspace. Prefer separate wallets? Separate accounts each have their own wallet and concurrency limit, and the same card works on each. Docs: Organizations & Teams, Managing Teams and Team Billing & Spending.
Set up a team
Open Organizations in the sidebar, then Create Organization. You become admin of its "Default Team". For more teams, such as one per project, click Create Team.
Click Switch next to the team.
Add credit: Credit Balance, then Add to Credit Balance, or use Transfer Credit.
Open Projects, then New Project. Its API key charges the team wallet.
Click Manage, then Invite Member, and choose Member or Admin.
Invitees click Accept Invite in the email, then sign in or Create Account with the invited address. Invites expire after 72 hours; resend if needed.
Roles
Owner (created the organization): admin of each team they create, and alone can create or remove teams and edit, remove or restore the organization.
Admin: edits Team Settings, manages members, roles and per-member spend limits, and can transfer credit and redeem coupons for the team.
Member: runs models, creates projects and chats with team agents. Everyone in the team sees all members and their spending.
Who pays
Team workspace runs charge the team wallet, never a member's personal wallet.
Transfer Credit (under Credit Balance; owners and team admins) moves balance between your Personal Wallet and teams you administer, or between two such teams, keeping expiry dates.
The concurrency limit uses the team wallet's balance and counts all members' team tasks together.
Team projects and API keys
A team project's API key charges the team wallet, with no extra header; personal keys charge your personal wallet. To move a personal project into a team you administer, choose Transfer in its menu on Projects. The key stays the same. See How do I get an API key? and Team API Access.
Limit models and spending
Model Access (in Team Settings): All Models, an Allowlist or a Blocklist. Blocked models fail in the team workspace (dashboard or team project key) with "This model is not available for your team" (see Why do I get "tool-not-accessible"?). Personal workspaces aren't affected.
Spend Limit per team (with an admin email alert) and per member on the Members page. Both count all-time spending, not monthly.
Switching workspaces
Credit Balance, Transactions, Coupons, Projects, Project Usage and Task History show your workspace in a banner with Switch Workspace and list only its data, with no combined total (see How do I see how much I've spent?). The Organizations page also has Switch per team and Switch to Personal. The choice is remembered per browser.
Coupons
In a team workspace only admins and the owner can redeem coupons, crediting the team wallet. Each person can redeem a code once, personally or for a team, and each team once. A code issued only to your account works only in Personal; in a team it returns "Coupon not exists". See How do I use a coupon code?
Removing members or a team
Admins remove people from the … (Actions) menu on the Members page; the person is emailed. Members can't leave on their own; admins can remove themselves. The last admin can't be removed or demoted.
A removed member's projects stay in the team and keep charging its wallet. An admin can delete them.
Only the owner can remove a team (Team Settings, then Remove Team). Its projects return to their creators, and their keys then charge the creators' own wallets. The balance isn't moved and the team leaves Transfer Credit, so transfer it out first or contact support.