User permissions rethought: granular access instead of rigid roles
With the new permissions update, we are moving access control in Memida to a central permission system. Instead of unlocking functions only through broad roles such as admin, user, or viewer, permissions can now be assigned much more precisely per user and per function.
Fig. 1: User permissions overview
(1) The assigned permission group remains visible directly below the user’s name in the user profile. (2) If you click Permissions in your user profile, you can see your personal permissions in detail.
What's new?
With this update, permissions are separated much more granularly across many areas of the application. This includes users, inspection equipment, cost centers, inspection reports, inspection instructions, labels, master data, data export, API, and webhooks.
The main improvements are:
- individual permissions directly per user
- clear separation between view, edit, and special actions
- separate access control for API, webhooks, and data exports
- stricter checks for navigation, page access, and actions
Manage permissions directly on the user
Groups still exist, but they now mainly serve as a default starting point. Permissions can then be adjusted specifically per user. This makes it much easier to distribute tasks without handing out unnecessarily broad administrative access.
This is especially helpful when users need to take over administrative tasks without requiring full access to all settings.
Less visible, better protected
The new permission system affects more than just buttons. Menus, pages, search results, widgets, and action menus now align more closely with the permissions a user actually has. At the same time, package and subscription limits are still respected, so unavailable features are excluded automatically.
This makes the interface clearer and access control more consistent.
You can find more information about the affected areas in our handbook and API documentation.