Administrator & Moderator
Administrator Role
The Administrator role grants unrestricted access to all data and features in Primentra. This is a server-level privilege set directly on a user account — it is not a role permission.
What administrators can do:
- Access all models and entities regardless of role permissions
- Manage Users (create, edit, delete, lock/unlock accounts)
- Manage Roles and assign permissions
- Access General Settings, including database connection and email configuration
- Access all other admin pages: Models, Integration Views, Logs (Audit Log, System Log, Database Log)
- View and modify data in any entity
Regular users without the administrator flag:
Regular users can still access other admin pages — General Settings, Models, Integration Views — based on their role permissions. The administrator flag specifically controls access to the Users and Roles pages, and overrides all entity-level permission restrictions.
Crown icon:
Administrators are identified by a crown icon that appears next to their name in the Settings menu and in the Users list. This makes it easy to identify which accounts have elevated privileges at a glance.
How administrator access works:
Administrator access is granted through role membership. Any role with the IsAdmin flag enabled grants full administrator privileges to all its members. Assign a user to an admin role in Settings → Access Management → Roles.
Moderator Permission Level
The Moderator flag is a role-based permission that grants full CRUD access (Create, Read, Update, Delete) plus the ability to manage entity and model configuration within the assigned scope.
What Moderator grants:
- Full CRUD access to data rows (all four operations automatically enabled)
- Access to entity configuration (editing entity settings, attribute definitions)
- Access to model configuration within the assigned scope
How Moderator differs from granular CRUD:
- CRUD only — Users can perform the specific operations you enable (e.g., Create + Read but not Delete)
- Moderator — Automatically enables all four CRUD operations plus configuration access. Use for team leads and data stewards.
How Moderator differs from Administrator:
- Moderator is a role-based permission — it applies only to the models and entities assigned to the role
- Administrator is a user-level flag — it bypasses all permission checks across the entire application
Setting Moderator access:
- Go to Settings → Access Management → Roles tab
- Open the role and click Edit permissions
- For the desired model or entity, click the Mod toggle button
- All CRUD buttons will automatically activate when Moderator is enabled
- Click Save permissions to apply changes