Admin Guide
The console, section by section, for whoever runs Asteria Cloud for an organisation.
The console lives at console.asteria-labs.com, and it is where you decide what everyone else can do. Only administrators can open it.
There is no link to it from the chat screen. From inside the app the route is Platform in the sidebar, then Organization settings at the bottom of the panel that opens. Going straight to the address is quicker, and worth bookmarking.
This guide follows the console's own sections, in the same order, so a page here matches what is in front of you.
What you own
Four things, roughly in the order they will matter.
Who is in. Invitations, roles, deactivation, and the seat count you are paying for. See Users.
What the assistant can reach. Which models exist, which providers are connected, which tools your organisation allows. See Models, MCP servers and Connectors.
What it costs. Usage by project and by person, storage, and credits if you are on them. See Usage.
How it behaves by default. Organisation-wide instructions, your brand palette, your presentation template, and which features members may use at all. See Organization.
The four settings worth doing on day one
Before anything else:
- At least one chat model, and a default. A flash or lite tier is the right pick: capable enough for the large majority of work, and used almost everywhere. Nothing works without it, and an omitted
modelon the API depends on it. Models. - An embedding model, 1024 dimensions. Without one, collections cannot be indexed and users get an error they cannot act on. Models.
- Your organisation's name and context. Two boxes that improve every answer everyone gets. Organization.
- Invite one colleague and watch them arrive. It is the cheapest way to find out your email is not being delivered. Users.
The sections
Dashboard
Requests, cost, active users, model health.
Users
Invitations, roles, seats, deactivating and deleting.
Organization
Instructions, context, palette, deck template, and the feature switches.
Moderation
Reports your members file about published agents and skills.
Models
Providers, credentials, defaults, task models and fallbacks.
MCP servers
External tool providers, offered once and granted per user.
Connectors
Google and Microsoft, and when you need your own application.
Usage
What was spent, by whom, on what.
Storage
Per-user usage, caps, and the nightly reconciler.
Credits
Balance, runway, limits and grants.
Projects also live under Platform, and are documented in Platform & API because they are the seam between administration and building on the API.
A note on what you cannot see
You administer the organisation. You do not read your members' conversations from this console: there is no screen that shows you what somebody asked yesterday.
Worth knowing precisely, because people ask. You can see that usage happened, by whom, at what cost, and you can see what members chose to publish or share. The content of a private conversation is not an administrative surface.