The console
What owners and admins of an organisation see in the console – security, members, workspaces, usage, agents, the operator's access and the protocol –, how to sign in there and what of it is itself in the protocol.
The console is a place of its own on the web, separate from the app: there you see what happens in your organisation and who did what. It is for owners and admins of an organisation with its own space. Members, clients and a client's organisation do not open it.
Sign in to the console#
- Open console.arvemo.ai. The app's sign-in does not count here – the console has its own.
- Enter your address and choose Send code.
- Enter the six-digit code from the mail and choose Sign in. A code works once and for ten minutes.
The page answers the same for every address – it does not reveal who may use the console. A session ends after 12 hours or after 30 minutes without a click. Sign out ends all your console sessions.
What you see there#
Under your organisation's name:
- Security: signs of a problem, ordered by severity, with the reason and what to do.
- Members, Workspaces, Usage and Agents: who is in, which workspaces exist, what the AI cost and what the agents did.
- Operator access: every time the platform's operator looked at your organisation or changed something about it.
- Protocol: who did what, see below.
Read the protocol#
The protocol records who did what in your organisation – people, agents, the system and the operator. Each row carries the checksum of the one before, so a row changed, missing or put in would show. The Protocol page shows:
- whether your chain holds, how many rows are still waiting for their seal and when it was last recomputed in full;
- what happened in the chosen period (1, 7 or 30 days), per day and counted by action and by who acted (people, agents, system, operator) – without names.
The console does not show the single rows yet – who read, changed or exported what. They open once sign-in has a second factor.
Who sees that I was in the console?#
Every look in the console, every refused sign-in and every export is itself a row of the protocol. When the platform's operator looks at your organisation, that is in your protocol and under Operator access. The operator does not see the content of your workspaces in the console.