Skip to main content

Administration — overview

The administration console lives at /app and is where you govern your organization in Imaginne: users and roles, profiles, skill groups, the skill catalog, policies, credentials (BYOK and env-secrets), templates, integrations, and the audit log.

Who gets in and where they land​

Console access is exclusively via browser-based login — the same identity that applies across every surface. There's no local password creation and no API key creation: you log in, the browser authenticates, and the session is bound to your organization.

Where you land right after login depends on your role:

RoleDestinationWhat they administer
Organization administrator (org_admin)/orgEverything: users, profiles, groups, skills, policies, BYOK, env-secrets, templates, integrations, audit.
Skill administrator (skill_admin)/skill-adminOnly the skills in the groups under their responsibility (My Groups).
User (member)/chatAdministers nothing; goes straight to the chat.
An org_admin also needs a profile to use the chat

Administering the organization and using the agent are separate things. An administrator with no profile assigned opens the chat with no skills at all. Assign a profile to yourself if you want to use the chat surfaces. See the "no profile" notice further down.

Side navigation​

The console sidebar groups the administration areas. Each item leads to its page:

ItemRouteWhat it's for
Dashboard/orgOverview with counters and recent activity.
Users/org/usersUser list, creation, and role management.
Profiles/org/profilesLink skills to users.
Skill groups/org/skill-groupsOrganize skills and delegate administration.
Skills/org/skillsThe organization's skill catalog.
Governance/org/governancePolicy editor and simulator.
BYOK/org/byokThe organization's own model keys.
Env-secrets/org/env-secretsSecrets injected into skills.
Templates/org/templatesThe organization's DOCX/PPTX templates.
Integrations/org/integrationsConnections to Slack, Google, Atlassian.
Audit/org/auditLog of administrative actions.
The routes are internal to the console

The table above shows the actual paths inside /app for orientation. The documentation always links to the explanatory pages for each area (for example, Users & roles).

The Dashboard​

The home page (/org) gives you a quick read on the state of the organization. It brings together:

  • Counter cards — Users, Profiles, Skill groups, and Skills. Each card shows the current total and leads to the corresponding listing.
  • Recent activity — the latest administrative events (user creation, skill publication, profile change, etc.), a sample of the audit log.
  • "No profile" notice — when you, the administrator, have no profile assigned, the Dashboard displays a notice explaining that the chat will open empty until you assign yourself a profile.
With no profile, the chat opens empty

The set of skills that appears in your session is the union of the skills from the profiles assigned to you. With no profile — administrators included — no skill enters the conversation. That's the reason for the notice on the Dashboard.

What the console does not have​

To set the right expectations, it's worth being clear about what falls outside the scope of this console:

  • There's no usage or billing screen. The visibility an organization administrator has into activity is limited to the Dashboard cards and the audit log. Detailed consumption metrics and billing are not exposed here.
  • There's no API key creation. Access is browser-login only. Creating a user does not generate a password or a key — the user receives an email to set their own password. See Users & roles.
  • There's no infrastructure configuration. Servers, deployment, and networking are the platform's responsibility, not this console's.

Where to start​

If the organization is new, a common path is: create users → create skill groups → publish/import skills → create profiles linking skills to users → tune the policy and, where relevant, configure BYOK and env-secrets.

Console areas​