System configuration (super administrators)
The /system area is for tenant-wide configuration: integrations, AI, reference data, and monitoring. It is separate from /admin (firm operations such as users and offerings). Most fee earners never use /system.
Navigation labels and permissions come from the SBOS.AI web client sources: ALP/App/src/components/ui/layout/framework/navLinks.ts (allSystemLinks) and ALP/App/src/router/system.router.ts.
Who should use it
- IT or operations with
SystemIntegration.Edit,System.Admin, orBusinessEntity.Editas required per screen. - AI owners with
Agent.View(agents) andSystemIntegration.Edit(prompt library).
Modules (from system.router.ts + allSystemLinks)
| Area | Routes / screens | Typical permission |
|---|---|---|
| Tenant | Tenant settings | System.Admin |
| Integrations | System integrations, Syntaq app, MCP servers | SystemIntegration.Edit |
| Business entities | Business entities list | BusinessEntity.Edit |
| AI | Prompt library (/system/ai-prompts), AI agents, agent slots | SystemIntegration.Edit / Agent.View (see meta on each child) |
| Monitoring | Integration usage stats (SystemIntegration.View on usage child), time entry stats, audit logs | SystemIntegration.Edit on parent segments (see router) |
| Reference data | Law areas, capabilities, segments, offering categories, asset register types, … | Mostly .View or .Edit per entity (e.g. LawArea.View, Offering.Edit for offering categories) |
Audit logs
System → Audit logs uses SystemIntegration.Edit on the /system/audit-logs parent in system.router.ts. The separate Admin menu has other audit tooling depending on your tenant — do not assume paths are interchangeable.
Caution
Misconfiguration can interrupt email sync, billing, or login. Apply changes in a maintenance window with a rollback plan.
See also
- Administration overview
- System settings —
/adminconfiguration (different from/system) - Other admin screens