Every team workspace has an admin console. A managed organization also finds groups, roles, rules, models, resources and sign-in settings there. A personal workspace has no admin console.
Open the admin consoleLink to the Open the admin console section
- From the workspace menu at the top of the sidebar › “Administer” followed by the workspace name.
- From your account menu at the bottom of the sidebar › the same entry.
- “Settings” › “Your workspace” › “Open admin console”.
The admin console opens for anyone who has at least one permission over the whole organization: the owner, the admins, and any custom role that grants one. A group manager, whose permissions are limited to their own groups, gets “My groups” instead: see Groups, roles and labels.
The first time you open it, Moon AI offers “Welcome to the administration of … A 30-second tour?”. “Take the tour” walks you through the navigation, the setup steps and the “To do” list; “Later” closes the offer.
NavigationLink to the Navigation section
Pages are sorted into five groups. The search field at the top of the navigation finds a page from a single word, such as SSO or licenses.
| Group | Pages | Opens with |
|---|---|---|
| “Organization” | “Overview” | Any access to the admin console |
| “General” | “Change organization settings”, “Set organization rules”, or the owner’s rights | |
| “People” | “Members” | “View members” |
| “Invitations” | “Invite members” or “Import members” | |
| “Groups” | A permission on groups, or “View members” | |
| “Roles” | “Create and edit roles”, “Assign roles to members” or “Set organization rules” | |
| “Organization labels” | “Create and edit labels” or “Apply labels to members” | |
| “Licenses and usage” | “Plan and licenses” | “View member licenses”, “Manage member licenses” or “View contract and invoices” |
| “Usage” | “View usage” or “Export usage” | |
| “What members use” | “Rules” | “Set organization rules” |
| “Models” | “Set organization rules” or “Choose models” | |
| “Resources” | “Manage connectors”, “Manage storage”, “Manage shared library” or “Publish to the catalog” | |
| “Security” | “Sign-in” | “Manage security” |
| “API and keys” | “Manage admin API keys” or “Change organization settings” | |
| “Activity log” | “View audit log” or “Export audit log” |
A team workspace without organization features has a reduced console: “Overview”, “General”, “Members”, “Invitations”, “Plan and licenses”, “Usage”, “API and keys” and “Activity log”. The other pages appear once the organization functions are turned on. Permissions are described in Roles.
Save your changesLink to the Save your changes section
On settings pages, a bar appears at the bottom as soon as a field changes: “Unsaved changes”, with “Discard” and “Save changes”. Leaving the page before saving opens “Leave without saving?”, with “Stay” or “Leave without saving”. Every saved change is recorded in the audit log.
OverviewLink to the Overview section
The first page of the admin console sums up the state of the workspace.
- At the top, in a managed organization, the “Setting up” card ticks off the steps already done: see Setting up. “Hide” removes it.
- The “To do” list shows what needs your attention, with a link to the relevant page. When it is empty, it reads “Nothing to do. Everything is set up.”.
- The key figures come next: active and suspended members, taken and free seats, pending invitations, groups, usage over 30 days, contract and invoices.
- The page ends with the members closest to their monthly limit, and “View all usage”.
| “To do” alert | Suggested action |
|---|---|
| Invitations are waiting for an answer | “View invitations” |
| Domains are still to be verified | “Verify the domain” |
| “Single sign-on (SSO) is not set up” | “Set up single sign-on” |
| “The contract ends on” followed by the date, with no renewal planned | “View contract” |
| Invoices are overdue | “View invoices” |
| A license pool is full, or members have no license | “View licenses” or “View members” |
A team workspace with no subscription shows “This workspace has no subscription. Each member uses their own free limit.”.
General pageLink to the General page section
| Section | Contents | Details |
|---|---|---|
| “Identity” | “Name”, “Identifier”, “Description”, “Logo” and the creation date | Rename a workspace |
| “Type and features” | “Organization type”, “Organization features” | Turn on the features |
| “Access and retention” | “Access outside the organization”, “Conversations kept for” | Access and retention |
| “Organization instructions” | The text Moon AI reads in every conversation of the members | Instructions |
| “Memory” | “Allow memory in this workspace” | Memory |
| “Ownership and deletion” | “Owner” › “Transfer”, “Delete organization” | Transfer, Delete |
Saving a change to the organization features or to access outside the organization first opens a confirmation that describes its effect.
API and keys pageLink to the API and keys page section
The “API and keys” page connects the organization to your programs. The owner, the admins and the roles that manage the API can see it.
| Section | Contents |
|---|---|
| “Getting started” | A “First call” example with the organization identifier, “Read the documentation” and the “OpenAPI file” |
| “Admin keys” | The keys a program uses to manage the organization |
| “Webhooks” | The addresses of your servers that are notified of the organization’s events |
| “Moon CLI” | The “Moon Blur required in Moon CLI” switch |
Create an admin keyLink to the Create an admin key section
- “Admin keys” › “New key”.
- Enter a “Name” that says who uses it, such as your HR software.
- Under “Permissions”, choose “No access”, “Read access” or “Read and write” for each area.
- Choose the “Expiration” (“Never” or a number of days) and, if you want, the “Allowed addresses”: one address or range per line.
- Click “Create key”, copy it, then click “I copied it”. It will not be shown again.
A key never has more rights than the person who creates it. It never deletes the organization, never changes its owner, never pays and never manages other keys. It stops working when its creator leaves the organization. A key’s rights cannot be edited: to get different rights, create a new key. “Revoke” stops it at once. Using keys from a program is described in Admin API.
Add a webhookLink to the Add a webhook section
- “Webhooks” › “New webhook”.
- Enter the “Address”, a public HTTPS address of your server, and a “Description”.
- Tick the “Events”: a member joins, leaves or is suspended, a license pool is full, the rules change, the contract renewal is coming up.
- Click “Create webhook”, then copy the “Signing secret”. It will not be shown again.
“Send a test” checks that your server answers. “View deliveries” lists the latest deliveries. “Create new secret” replaces the current secret, which stops working at once. Checking the signature is described in Organization webhooks.
Moon Blur in Moon CLILink to the Moon Blur in Moon CLI section
The “Moon Blur required in Moon CLI” switch is described in Organization rules.