Users / Roles – Permissions Overview
This article provides an overview of all permissions by role.
In aleno, different roles can be assigned – from Account Owner to Viewer. Each role has specific rights and permissions that define access to features and settings.
This overview compares all user roles: which actions are allowed, where restrictions apply, and what can be configured individually per user.
👤 Administration
Function | Account Owner | Admin | Service | Viewer |
---|---|---|---|---|
Create other user profiles (Admin, Service, Viewer) | ✅ | ❌ | ❌ | ❌ |
Create other user profiles (Service, Viewer) | ✅ | ✅ | ❌ | ❌ |
Edit/delete profiles (lower levels only) | ✅ | ✅ | ❌ | ❌ |
Transfer Account Owner / manage restaurant ownership | ✅ | ❌ | ❌ | ❌ |
Manage multiple restaurant accounts (e.g. create restaurant groups, merge guest databases) | ✅ | ❌ | ❌ | ❌ |
⚙️ Settings & System
Function | Account Owner | Admin | Service | Viewer |
---|---|---|---|---|
Change system settings (widget design, shift settings, capacities, times, emails) | ✅ | ✅ | ❌ | ❌ |
Access to different system areas (Calendar, booqIn, seatIn, relatIn, sellIn, reporting, msgIn) | ⚙️ configurable per user | ⚙️ configurable per user | ⚙️ configurable per user | ⚙️ configurable per user |
📅 Reservations
Function | Account Owner | Admin | Service | Viewer |
---|---|---|---|---|
Create/edit reservations (booqIn/seatIn) | ✅ | ✅ | ✅ | ❌ |
Move reservations | ✅ | ✅ | ✅ | ❌ |
Block shifts and time slots online (lock symbol) | ✅ | ✅ | ⚙️ configurable per user | ❌ |
View reservations (read-only) | ✅ | ✅ | ✅ | ✅ |
Add Ad-Hoc users when creating/editing (booqIn/relatIn) | ✅ | ✅ | ✅ | ❌ |