Workspace admin

Run AI agents across your enterprise

People and roles, budgets with a forecast, app policy and sign-in, in one place for the whole company.

Book a call
FIG 4.0

What admins control

FIG 4.1

Four clear roles

Owner, admin, billing admin and member, each explained in plain words.

FIG 4.2

Budgets with a forecast

Spend against the budget, and when you’ll reach it.

FIG 4.3

Sign-in your way

SSO, directory sync and two-step sign-in, tested before they’re required.

1.0People and roles

Everyone, and what
they can do

Invite in bulk, pick a role, and see each person’s spend against their budget.

Roles in plain words

Each role says what it can and can’t do, right where you pick it.

One person’s page

Role, limits and spend in one place, with any request for more.

Bulk invites

Paste a list; each address is checked as you type.

Suspend or remove

Suspend keeps history. Remove asks who takes their agents.

Transfer ownership

Confirmed by typing their email; they have 7 days to accept.

Agents stay private

Admins see names and cost, never chats or files.

2.0Budgets and usage

Know the bill
before it comes

Spend by person, agent, model or day, with a forecast against the budget and alerts at 50, 80 and 100 percent.

  • Forecast with a range

    Dashed and banded, so it never looks like actual spend.

  • Group it your way

    By person, agent, model, kind of work or day.

  • CSV export

    The chart and the table add up to the same total.

  • Cloud costs apart

    What your own cloud bills is shown, and kept out of Miles spend.

Who’s blocked, and why

It says whose budget stopped them and what they asked for.

Stop, or just alert

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

Decide which apps
agents can use

Allow every app, only approved ones, or all but a block list. Set the most an agent can do in each.

Requests with reasons

People ask for an app and say why. The most-asked come first.

Every connection

Who connected what, and when it was last used. Tokens are never shown.

Tool limits per app

People can turn tools off, never on beyond your limit.

Risky tools marked

Writes and deletes are flagged, and can always ask.

Expired sign-ins

Shown by person, so the right one signs in again.

Revoke one, or all

End one account’s access or disconnect an app everywhere.

4.0SSO and SCIM

Sign-in, the way
IT wants it

Connect Okta or any SAML provider, test it, then require it. Directory sync adds and suspends people for you.

  • Two-step sign-in

    Require it with a grace period, and see who isn’t set up.

  • Session policy

    Sign out after inactivity, cap session length, or sign out everyone.

  • Hand setup to IT

    A setup link that works for 30 days and opens nothing else.

  • Certificate alerts

    Your IT contact hears 30, 7 and 1 day before it expires.

Directory sync

Status, counts and the attribute map. A conflict names the matching field and both records.

Verified domains

A TXT record, with steps for your DNS provider.

More of Miles

Open this week

30 minutes • With the team

One place to run it. For everyone.

Bring a real task. We’ll show an agent doing it on its own computer, in your apps, and asking before it acts.

Live demoYour use caseSecurity questions