Skip to main content

Admin Console

The control centre for your workspace: robots, published flows, schedules and triggers, users and permissions, queues, vaults, monitoring, licensing and API tokens.

The Admin Console dashboard

Where things are

Running work

PageFor
DashboardWorkspace at a glance
RobotsCreate robots, generate tokens, see what is connected
Published FlowsFlows available to robots, and their versions
JobsEvery run, with status, duration and logs
SchedulesCron-based unattended runs
TriggersEvent-driven runs — HTTP, mail, file system, queue
QueuesWork items flows consume and produce
MonitoringAlerts for robots that go quiet

People and access

PageFor
UsersInvitations and workspace roles
CollaboratorsPer-flow access — Owner, Writer, Reader
VaultsCredential vaults, ownership and orphans

AI

PageFor
AgentsAI agents, their runs and review

Workspace

PageFor
APIGenerate and revoke API tokens
AuditWho did what, when
RepositoriesYour own package and application repositories
LicensesOn-Prem and Private Cloud licensing
SubscriptionsPlan, usage and invoices

Two things to do on day one

Both are cheap now and expensive to retrofit.

  1. Share every vault with a second personVaults. A forgotten password makes that user's credentials permanently unrecoverable, and nobody at Robomotion can help. Sharing is the only protection, and it has to happen while someone can still open the vault.
  2. Add a downtime alertMonitoring. A robot that never picks up its schedule produces no job at all, so nothing appears in Jobs. Silence is the failure mode that goes unnoticed longest.