Admin Panel & Roles | Alephant Documentation

AIvis separates deployment-wide administration from scoped resource curation so that people receive the access they need without expanding sensitive configuration access unnecessarily.

Page purpose

Define roles before opening models, knowledge, and Agents to more users. Otherwise, later connectors, Actions, or Agents may not have a clear owner, and audits become harder because it is unclear who should be allowed to modify configuration.

Confirm first	Why it matters
Who is the first Admin	The first Admin establishes deployment-level configuration, invites other administrators, and owns the initial security boundary.
Who needs Curator access	Curators should serve a defined group or business scope, not replace Admins.
Which resources can be shared	Agent, document set, and Action sharing determines what end users can actually use.
Which settings must stay Admin-only	Models, indexing, security, and organization settings should not be changed by operational roles.

Access the Admin Panel

After signing in with the appropriate role, Admins begin from Admin and can open model configuration at /admin/configuration/language-models. Curators begin from Curator at /admin/agents; their menu also provides MCP Actions, OpenAPI Actions, connectors, and document sets. Menu visibility does not remove the ownership and group boundaries described below.

Admin and Curator

Role	Primary entry	Primary responsibility
Admin	Admin → `/admin/configuration/language-models`	Configure deployment-wide settings and manage all Agents, Actions, connectors, document sets, and attachments
Curator	Curator → `/admin/agents`	Manage Agents, connectors, and document sets for groups for which they are a curator; create and maintain only their own MCP and OpenAPI Actions
Global Curator	Curator → `/admin/agents`	Manage Agents, connectors, and document sets for groups of which they are a member; create and maintain only their own Actions

First administrator

Before configuring the deployment, the person responsible for its initial setup should confirm administrator access. That administrator should then establish the intended roles and access boundaries before delegating configuration or curation work.

Responsibility boundaries

Assign the smallest role that supports a person’s task. A role name does not guarantee every menu is visible: deployment mode, server configuration, and administrator settings can still limit available controls.

Admins own deployment-wide settings and can manage all resources. Curators manage Agents, connectors, and document sets for groups for which they are a curator; Global Curators manage those group-scoped resources for groups of which they are members. Both Curator roles can create MCP and OpenAPI Actions, but can modify, delete, or maintain protected credentials only for Actions they created. Global Curator status does not expand Action ownership.

A Curator can attach a currently available Action to any Agent they can edit. Neither Curator role can change deployment-level models, Index Settings, organization-wide integrations or security, Usage, or other organization settings.

Next steps

Confirm the deployment mode, configure deployment-level settings as an Admin, and give Curators only the group scope needed for their Agents, connectors, and document sets. Curator-created Actions remain owner-scoped.