Manage
The Administrator surface - users, roles, organization settings, API keys, webhooks, data operations, and the trust story.
Everything in this section lives under Settings, and all of it requires the Administrator role. It's the smallest surface in AssetLab and the one with the longest consequences - decisions here shape what everyone else sees.
What lives here
| Page | What it covers |
|---|---|
| Users & invitations | Getting people in, roles, removal |
| Roles & user groups | Scoping teams by site, system class, and work category |
| Organization settings | Identity, currency, notifications, workflow options |
| API keys | Scoped, tenant-bound keys for the API and MCP |
| Webhooks | Pushing events to your other systems |
| Import & export | Data in, data out, in bulk |
| Security & data residency | Where data lives and how it's protected |
| Language & localization | English and French |
The Administrator's first hour
For a new organization, work through Settings in this order:
- General settings - currency first (it lives on the General tab, and money formatting flows everywhere).
- Users - invite the core team with conservative roles.
- User groups - once dispatch by district or trade matters; small teams can skip them (ungrouped users are unrestricted).
- Work order / requester portal settings - categories and routing to match your operation.
- API keys - when you're ready for AI or integrations, not before.
A standing habit
Settings changes are organization-wide and immediate. Two safeguards worth adopting:
- Announce changes that alter what people see (categories, portal fields, group scopes) - a silent change reads as a bug to the field.
- Review users and API keys on a calendar - quarterly is plenty, forgetting entirely is the failure mode.