The Team Plan: One Workspace for Your Organization

The Team plan turns Radient into a workspace for your organization. Invite your team, give each person a role, and share agents and teams privately inside the organization, all under one monthly subscription.

#What the plan includes

• A shared workspace. Every member signs in with their own Radient account and works in the same organization.
• Private sharing. Agents and teams published to your organization are visible to its members only.
• Pooled credits. Add credits once and the whole team draws on the team's balance — including covering a member whose own balance runs out. See Pooled credits.
• Team Bridge and Vault team vaults. Members' agents can exchange notes, questions and requests through Team Bridge (Agent messages in Local Operator), and Vault team vaults (beta; request access through the contact form) let members share a credential by reference instead of pasting it.
• One subscription, one seat per active member, billed monthly. The amount is shown at checkout. Pending invitations are free until they are accepted, and the seat count updates automatically as members join or leave.

#Free trial

Organizations that haven't had the Team plan before can try it free for 30 days. The organization's owner starts the trial, and needs a verified email address to do so. No credit card is required, and nothing is charged automatically, during the trial or after it ends.

Start your free 30-day Team trial

• What's included. Everything in What the plan includes: members and roles, private sharing, pooled credits and member spending, Team Bridge and Vault team vaults. The trial adds no free credits; usage is paid from a balance as usual.
• When it ends. Team features pause until you subscribe. Nothing is charged automatically and your data is kept: your members, roles and shared agents are kept, Team Bridge history stays readable (read-only), and Vault team vaults are locked, not deleted, and restored when you subscribe. Invitations still pending when the trial ends are withdrawn and are not restored; re-send them after you subscribe.
• Credits you buy. Credits added to the organization's balance during the trial stay there and are never lost. When the trial ends they follow the same rules as a lapsed plan: not spent, refunded, expired or moved, and pooled spending stops by default.
• Subscribe at any time. Choose Subscribe to Team on the Team page during the trial or after it. The paid plan takes over straight away, with no gap in access; after the trial has ended, subscribing restores your members.
• One trial. There is one free trial per organization and account; a trial cannot be started again.

#Free trial questions

Do I need a credit card to start the trial?

No card needed. The trial asks for no payment details.

Will I be charged when the trial ends?

No. Nothing is charged automatically and nothing converts to a paid plan on its own. Team features pause until you choose to subscribe.

What happens to my team's data when the trial ends?

It is kept. Members, roles and shared agents stay in place, Team Bridge history stays readable (read-only), and Vault team vaults are locked and restored when you subscribe. Invitations still pending at the end are withdrawn and are not restored; re-send them after you subscribe.

Can I subscribe before the trial ends?

Yes, at any time, with no gap in access.

Can I start the trial again?

No. There is one trial per organization and account.

#Pooled credits

Adding credits to the organization's balance once lets the whole team use them. A few behaviours are worth knowing exactly:

• A call is paid by exactly one balance — the first balance in your payer order that can cover it. Calls are never split across balances, and a refused call (insufficient credit) is not charged to anything.
• Payer order. Sign-in tokens created through the OAuth flow pool the team's balance first, then your own. API keys and other tokens charge your own balance first, then the team's. You can pin a preferred balance in the console; a pinned balance that cannot currently pay is skipped.
• Member spend. An owner or admin decides whether members may draw on the organization's balance. Left unset, it follows the plan: while the plan is active (or in its past-due grace), members may draw on the pool; when the plan lapses, pooled spending turns off. An explicit setting is remembered across cancellation and restart.
• Attribution. Every usage record notes which balance paid (own or team), so shared spend is visible per member in the usage view.

#If the plan is cancelled or lapses

Cancelling schedules the plan to end at the close of the current period — everything keeps working until then, and Resume undoes it.

When the subscription actually ends:

• Members lose access, not their membership. Every member except the owner loses access to the organization's shared features. Their membership rows are kept, not deleted, which is what makes a restart restore them; the owner keeps the Team page and billing controls throughout.
• Pooled spending stops by default. With the default settings, the team's balance stops being a payer for everyone — including the owner — as soon as the plan lapses. If an owner explicitly enabled member spend, that setting survives and the owner can keep spending the organization's balance.
• The balance is not touched. Cancellation changes no money: the organization's balance, ledger and any held credits are left exactly as they are. Credits are not spent, refunded, expired or moved, and the owner retains access to the organization's billing account.
• Starting the plan again restores everyone. Members who lost access become active again in one step, and anything that was held while the plan was lapsed — an invitation accepted in that window is held rather than usable — becomes usable with the rest.
• A failed payment is not a cancellation. While a subscription payment is past due, the plan keeps full access and the billing contacts receive notices; access is only affected when the subscription actually ends.

#Start and manage the plan

Open the Team page in the Radient console. The owner manages the plan from the plan card:

• Upgrade: the upgrade dialog shows the seats, the per-seat amount, and the total before you continue to the payment page. The plan activates as soon as the payment is confirmed.
• Manage billing: open the billing portal to manage your subscription's billing details.
• Cancel: schedule a cancellation for the end of the current period. The team keeps access until then, and you can start the plan again later.
• Resume: undo a scheduled cancellation so the plan renews at the end of the period.

The same page keeps the paperwork together: billing contacts (the people who receive billing notices) and invoices, which appear after the first plan payment.

If the plan lapses, the organization's shared features become unavailable while the team itself (its members, their roles, and its shared content) stays in place, and starting the plan again restores access. The owner keeps the Team page's management controls throughout, so the plan can always be restarted or closed.

#Members and roles

Invite people from the Team page: choose Invite member, enter their email address, and pick a role. If the address already has a Radient account, the person is added to the team directly; otherwise they receive an email with an invitation link that works once and expires after seven days, and they accept it on the console after signing in.

* An owner can remove anyone; an admin can remove members.

• Owner: manages the plan and the team, and is the only role that can change roles or billing.
• Admin: invites people and removes members.
• Member: uses the organization's shared features.

Transfer ownership with Make owner (you become an admin): the new owner takes the owner role and you become an admin. A team always keeps at least one owner. Use Leave team to leave the team: you lose access immediately, so if you are its only owner, make someone else an owner first.

#Private agents and team hubs

Your organization is a private namespace for sharing. These commands act as the signed-in person, so sign in first and pass the organization's tenant_id: run lop teams push <team> without --org and it lists your organizations with their tenant IDs.

lop login radient
lop agents push --name "My Agent" --org <tenant_id>
lop agents pull --id "<agent_id>" --org <tenant_id>
lop teams push --org <tenant_id> <team>
lop teams pull --org <tenant_id> <team_id>

• Publishing to the organization requires an admin role. Admins need the Team plan active; the owner can publish in every plan state. Anything published stays readable to the organization's members only.
• In the Local Operator desktop app, the Agent hub lets you publish an agent with your organization as the target, and an organization's agents and published teams appear in its own view, including a Pull action to install a team on the current computer.

#Teams and volume

See Radient pricing for the current offerings. For teams and volume (volume terms, invoicing, or anything Radient Pass does not cover), email contact@radienthq.com and tell us what you need; we answer within two business days.

#See also

• Agent Hub: the public hub of shareable agents.
• Personal Tunnels: reach your computer's tools from anywhere.
• Radient Pass: the pay-as-you-go balance behind everything.