Four clear roles
Owner, admin, billing admin and member, each explained in plain words.
Workspace admin
People and roles, budgets with a forecast, app policy and sign-in, in one place for the whole company.
Book a callOwner, admin, billing admin and member, each explained in plain words.
Spend against the budget, and when you’ll reach it.
SSO, directory sync and two-step sign-in, tested before they’re required.
1.0People and roles
Invite in bulk, pick a role, and see each person’s spend against their budget.
Each role says what it can and can’t do, right where you pick it.
Role, limits and spend in one place, with any request for more.
Paste a list; each address is checked as you type.
Suspend keeps history. Remove asks who takes their agents.
Confirmed by typing their email; they have 7 days to accept.
Admins see names and cost, never chats or files.
2.0Budgets and usage
Spend by person, agent, model or day, with a forecast against the budget and alerts at 50, 80 and 100 percent.
Dashed and banded, so it never looks like actual spend.
By person, agent, model, kind of work or day.
The chart and the table add up to the same total.
What your own cloud bills is shown, and kept out of Miles spend.
It says whose budget stopped them and what they asked for.
Stopping new tasks at the budget is its own switch. Running tasks always finish.
Know who spent what before the bill comes. Spend by person, agent and day, with an alert before anyone reaches a limit.
3.0Apps policy
Allow every app, only approved ones, or all but a block list. Set the most an agent can do in each.
People ask for an app and say why. The most-asked come first.
Who connected what, and when it was last used. Tokens are never shown.
People can turn tools off, never on beyond your limit.
Writes and deletes are flagged, and can always ask.
Shown by person, so the right one signs in again.
End one account’s access or disconnect an app everywhere.
4.0SSO and SCIM
Connect Okta or any SAML provider, test it, then require it. Directory sync adds and suspends people for you.
Require it with a grace period, and see who isn’t set up.
Sign out after inactivity, cap session length, or sign out everyone.
A setup link that works for 30 days and opens nothing else.
Your IT contact hears 30, 7 and 1 day before it expires.
Status, counts and the attribute map. A conflict names the matching field and both records.
A TXT record, with steps for your DNS provider.
Bring a real task. We’ll show an agent doing it on its own computer, in your apps, and asking before it acts.