dashboard-web is the shared customer dashboard for OpenLeash.
Teams use it to onboard, connect identity, manage users, configure policy, set BYOK evaluation keys, issue deployment tokens, review risky actions, and understand what agents are doing across their environment.
- Organization setup and sign-in
- Identity provider configuration
- Users, roles, and deployment coverage
- Policies and approval flows
- Plugin requirements, defaults, employee installation freedom, configuration locks, and organization/per-agent profiles
- Agents, MCP servers, skills, and external-agent visibility
- Audit trails for risky, approved, denied, and held actions
- Provider/BYOK evaluation settings
npm install
OPENLEASH_API_URL=http://localhost:9319 npm run dev:dashboard-webOpen:
http://localhost:9300
Recommended full-mode runner:
python3 run.pyChoose Private Cloud or OpenLeash Cloud.
| Environment | How |
|---|---|
| 🏢 Private Cloud | Runs directly for one customer tenant. |
| ☁️ OpenLeash Cloud | Composed by cloud-dashboard-web. |
| 🧪 Local dev | Talks to dashboard-api on localhost:9319. |
The dashboard renders backend-owned plugin manifests and settings schemas. Admins can independently choose whether a plugin is mandatory, enabled by default, installable by employees, and configurable by employees. Organization settings and profiles can target all agents, an agent kind, or an exact enrolled runtime. Employees see clear required, blocked, unlocked, and locked states; a mandatory plugin may still be customizable when the admin allows it.
Operational, dense, calm. This is a working security console, not a marketing page.
Prefer readable tables, timelines, obvious states, crisp empty states, and controls that feel safe to use repeatedly.