System configuration overview and access
System configuration is the administration area of MobilityManager where you tailor how the platform behaves for your tenant: notification emails, where documents are stored, how workflow labels read, expense (Belege) rules, vehicle reference data, and regional settings. This article explains what the area covers and who is allowed to open each part of it.
What system configuration includes
- Email templates — the subject and HTML body of notification emails, with reusable placeholders.
- Document storage — the global provider (Local, Azure Blob, or S3) that holds uploaded documents.
- Localization — translated labels for Beleg workflow states and Beleg types.
- Belege configuration — expense validation rules and thresholds, published as versioned configurations.
- Reference data — fuel types and motor types used across vehicles.
- Tenant settings — default language and the regulatory framework (HU, §57a, MFK).
Who can access each area
Access is governed by the role-based permission system. Every endpoint is protected with a [RequirePermission] check, so a user sees an area only when their role (or a custom role) grants the matching permission. The built-in roles are SystemAdmin, FleetManager, and Driver.
| Area | Permission to view | Permission to change |
|---|---|---|
| Email templates | email-templates:view | email-templates:manage |
| Document storage | settings:manage | settings:manage |
| Localization | settings:manage | settings:manage + SystemAdmin role |
| Belege configuration | settings:manage | settings:manage + SystemAdmin role |
| Reference data (fuel/motor types) | vehicles:view | vehicles:manage |
| Regulatory framework & language | settings:manage | settings:manage |
Note: A few sensitive operations require more than a permission. Publishing or rolling back a Belege configuration version, and saving localization labels, additionally require the caller to hold the SystemAdmin role. Even a custom role with settings:manage receives a 403 (UNAUTHORIZED) response for those specific actions.
Where to find it
Most configuration pages live under the admin area of the UI, for example /admin/tenant-settings, /admin/email-templates, /admin/reference-data, /admin/document-management, and /admin/belege-configuration. Menu items appear only when your role grants the required permission and, for module-specific pages, when your license enables that module.
Good practices before you change anything
- Confirm you are editing the correct tenant — settings are tenant-scoped.
- For expense rules, review the active Belege configuration version before publishing a new one.
- Treat storage-provider changes carefully; they affect where every new document is written.
- Validate values before saving so a typo cannot be persisted (see the validation article).
Tip: Grantsettings:manageandemail-templates:manageonly to the small group of administrators who own configuration. FleetManagers typically need read access and reference-data management, while Drivers need none of these permissions.
Related
- Managing email templates
- Belege configuration overview and publishing a version
- Managing reference data: fuel types and motor types
- Validating configuration before publishing
