admin panel
The Admin Panel is where site admins manage members, agent tokens, schedule presets, alert rules, and webhooks for the sites they belong to. Installer management, the template library, user accounts, and email configuration are internal owlette pages and are not shown to customer accounts.
two levels of access
The Admin Panel holds two kinds of page.
Site-scoped pages are open to site admins — accounts with the global admin role — and always act on the sites that account belongs to:
| page | url | what it does |
|---|---|---|
| members | /admin/members | add and remove the people who can reach one site |
| agent tokens | /admin/tokens | list and revoke agent refresh tokens for a site |
| schedules | /admin/schedules | manage schedule presets |
| alerts | /admin/alerts | manage threshold alert rules for a site |
| webhooks | /admin/webhooks | manage a site's outbound webhook subscriptions |
Internal pages — installers (/admin/installers), template library (/admin/presets), users (/admin/users), and email (/admin/email) — cover platform-wide operations run by owlette. They are hidden from the sidebar for customer accounts, and their routes bounce anyone else back to the dashboard.
roles at a glance
| role | site access | admin panel |
|---|---|---|
| member | read-only on the sites they belong to | none |
| admin (site admin) | write access on the sites they belong to — machine commands and configuration, deployments, roosts, talons, webhooks, logs, and site members | the five site-scoped pages above, always limited to those sites |
Site data never widens with the panel: a site admin who belongs to two sites sees exactly those two in every site selector.
getting site admin access
admin is an account-level role, not a per-site setting, so it is granted once and applies to every site that account belongs to. It is set by owlette from the internal user-management page — email support@tridant.io to have an account upgraded.
Because the role is account-level, adding someone to a site with the admin role does not by itself grant admin rights: an account that is still a member joins as a member. See member management.
access
- Profile menu → "admin panel" (visible to site admins; members do not see the entry). For a site admin it opens on members.
- Direct URLs:
/admin/members,/admin/tokens,/admin/schedules,/admin/alerts,/admin/webhooks
Members are redirected to the dashboard with an error message, as is a site admin who opens an internal page directly.
capability matrix
Read access to the sites an account belongs to is baseline role behavior, not a Capability enum value. The capability rows below mirror RoleCapabilityMatrix in web/lib/capabilities.ts; site-scoped grants apply only to the sites that account belongs to.
| capability | member | site admin | scope |
|---|---|---|---|
| Read access to sites you belong to | yes | yes | site membership |
USER_SELF_PREFS | yes | yes | self |
USER_SELF_DELETE | yes | yes | self |
MACHINE_VIEW | yes | yes | sites you belong to |
MACHINE_EXEC_COMMAND | no | yes | sites you belong to |
MACHINE_CONFIG_WRITE | no | yes | sites you belong to |
MACHINE_REMOVE | no | yes | sites you belong to |
DEPLOYMENT_MANAGE | no | yes | sites you belong to |
DISTRIBUTION_MANAGE (roost) | no | yes | sites you belong to |
UNINSTALL_TRIGGER | no | yes | sites you belong to |
PRESET_MANAGE (site presets) | no | yes | sites you belong to |
SITE_MEMBER_MANAGE | no | yes | sites you belong to |
WEBHOOK_MANAGE | no | yes | sites you belong to |
SITE_LOGS_MANAGE | no | yes | sites you belong to |
TALON_MANAGE | no | yes | sites you belong to |
AGENT_TOKEN_REVOKE | no | yes | sites you belong to |
ALERT_RULES_MANAGE | no | yes | sites you belong to |
USER_ROLE_MANAGE | no | no | internal |
USER_DELETE | no | no | internal |
SYSTEM_PRESET_MANAGE (deployment template presets) | no | no | internal |
INSTALLER_MANAGE | no | no | internal |
GLOBAL_SETTINGS_WRITE | no | no | internal |
The last five capabilities back the internal pages; no customer role holds them.
hoot chat access follows site read access. hoot actions that execute commands or write machine configuration require MACHINE_EXEC_COMMAND or MACHINE_CONFIG_WRITE. LLM keys are per-user and are managed by each person in their own account settings — there is no admin-managed shared key.
account settings
Your own preferences, not the site's: how timestamps render, which alert emails you get, which machines you have muted, your hoot key, password and second factors, and your API keys.
member management
Add and remove the people who can reach one site, and see who owns it. Site admins manage membership for the sites they belong to from Admin Panel -> members.