Overview
The Admin Console is the control hub for your Leena AI deployment. It is where administrators configure how the platform behaves across every product area — who can access the dashboard, which channels employees reach the assistant on, how the assistant authenticates users, what templates and guardrails apply, and what activity gets logged for audit.
Settings made here are platform-wide. They apply across AI Colleagues Studio, Workflows Studio, Knowledge Management, Helpdesk, and the Virtual Assistant, rather than to a single workflow or AI Colleague.
Who this is for
The Admin Console is intended for the department specific (IT, HR, Finance, and Procurement) or system administrators responsible for governing how Leena AI runs in your organization — typically the platform owner or Center of Excellence team, working alongside whoever owns identity and compliance.
Day-to-day builders (workflow designers, knowledge authors, helpdesk agents) generally don't need the Admin Console. Their configuration lives inside their own product areas.
What's inside
The Admin Console groups its pages into the following sections. What you actually see is filtered by your role — see Visibility and access below.
Dashboard settings
Controls for the Leena AI dashboard itself — the administrative interface your team logs in to.
| Page | What it covers |
|---|---|
| Dashboard users | Create, edit, and deactivate dashboard users; assign roles; bulk upload users; manage user groups |
| Setup | Organization-level details such as company name, logo, and session token expiry |
| Authentication | How dashboard users sign in, including SSO configuration |
| Inactive user report | Audits terminated or dormant employees who still hold active dashboard access |
Bot Users
Controls for the employees who use the assistant, as opposed to the admins who configure it.
| Page | What it covers |
|---|---|
| User Table | The employee records the assistant recognizes, with their attributes |
| User Sync | How employee data is imported and kept current from your HRIS or directory |
| Audience | Named employee segments used to target workflows, notifications, and knowledge visibility |
Templates
A shared library of reusable message and document templates, organized by type — email, bot, letter, and WhatsApp. Templates created here are available to Workflows, Notifications, and Onboarding.
Orchestrator
Settings that shape how the AI Colleague reasons and responds.
| Page | What it covers |
|---|---|
| Settings | Core assistant behavior, including live chat handoff |
| Voice | Enables voice interactions and configures the voice agent |
| MCP server & A2A | Exposes Leena's capabilities to external agent platforms over MCP and A2A |
| Capability discovery | Controls how the assistant surfaces what it can do to employees |
| Guardrails | PII detection, content moderation, and jailbreak protection |
API credentials
Issue and revoke credentials for programmatic access to Leena AI. Client secrets are shown once at creation time and cannot be retrieved afterwards, so store them securely when they are displayed.
Leena Native Channels
Configuration for Leena's own assistant surfaces and how employees authenticate into them.
| Page | What it covers |
|---|---|
| Settings | Web app configuration for the Virtual Assistant |
| Widget config | The embeddable assistant widget |
| Language | Languages the assistant supports and how it selects between them |
| Apps authentication | Sign-in for the mobile and desktop apps, including OTP |
| Web authentication | Sign-in for the web assistant |
| Other auth settings | Additional authentication rules applied across surfaces |
| SAML apps | SAML applications used for identity federation |
External channels
Where employees reach the assistant outside Leena's own apps: Google chat, Outlook, Teams, Telegram, Slack, Whatsapp, Voice & SMS, and Workvivo. Each channel has its own setup page covering credentials, app installation, and channel-specific behavior.
Email settings
Outbound email delivery configuration — Sendgrid setup, Mailgun setup, and Office 365 setup for your sending provider, plus a Blacklist for addresses that should never receive mail from the platform.
Logs
Operational and compliance history.
| Page | What it covers |
|---|---|
| Web login errors | Failed employee sign-in attempts, for diagnosing access issues |
| Email Logs | Delivery status for email sent by the platform |
| Whatsapp logs | Delivery status for WhatsApp messages |
| Audit Logs | A record of administrative actions taken across the platform |
| Data Subject Requests | GDPR and privacy requests for employee data access or deletion |
Visibility and access
The Admin Console shows you only the sections your role permits. This is not a display preference — the same permissions are enforced when a page is opened directly by URL, so a bookmarked link to a restricted page returns an access-denied message rather than the page.
Three things determine what appears:
- Your role. Each section and page is tied to a specific permission. A role granted only channel setup will see the channel sections and nothing else. Sections whose pages are all restricted are hidden entirely rather than shown empty.
- Your license. On a trial license, Authentication and Audit Logs are not available.
- What's enabled for your organization. Pages for capabilities your deployment hasn't activated may not appear, or may show an enablement prompt instead of configuration.
If you expect to see a section and don't, your role is the first thing to check. See Dashboard Users for what each role grants.
Integrations is a separate areaConnectors and integrations are no longer part of the Admin Console. They now live in their own top-level Integrations area, which also covers execution logs, alert rules, and credential expiry. Older links into the Admin Console integration pages redirect there automatically. See Integrations.
Updated 2 days ago
