What is the "MAIN" Badge?
When browsing the permissions list for an application, you might see one permission marked with a blue MAIN badge next to its name.
- Definition: This represents the Entry Point for the application.
- Importance: If a user has "Edit" rights for specific features but lacks the MAIN permission, they effectively cannot use the tool.
- Tip: Always ensure the MAIN permission is included in your Profiles and Packages.
Why are the "Profiles" or "Assigned Users" tabs missing?
- Insufficient Rights: Your administrator account lacks the meta-permissions
define_profilesorassign_profiles. - Simple App Mode: If an application has only one permission, the Profiles tab is hidden automatically. Use Manual Grants or Packages instead.
Working with Large Lists (Sticky Search)
The interface includes a Sticky Search Bar when editing complex permissions (e.g., selecting structures). Use it to filter, then use Select All to bulk-select visible items only.
Permission Packages: status indicators in the user detail view
When you open a user's detail inside a Permission Package, each permission shows a status badge:
| Badge | Meaning |
|---|---|
| Active | Authorized through this Package. All good. |
| Manual (coincident) | Manually set to the same value — the package sync would have no effect. |
| Divergent | Authorized but with a different value or parameter than the Package defines. Use Sync to align. |
| Not granted | Permission was added to the Package after the last assignment. Use Sync on the permission row. |
| Disabled Manual | The permission was manually revoked after being assigned by the Package. |
| Disabled Assignment | The Package itself was unassigned from this user. |
| Profile: … | This permission is already provided by an active Permission Profile assigned to the user. |
| Auto (rule) | Provided by an automatic rule. The Package sync can still override it. |
| Founder | The user is the system Founder. All permissions are always active — no manual management needed. |
| Other Package | This permission is managed by a different Package. It cannot be modified here. |
A permission was granted but the user still can't access the application
- The user must log out and log back in to reload their session cache.
- Check that the MAIN permission is also granted (not just a sub-permission).
- If you used a Package, confirm the Package is still Active (not disabled).
I see "NON-DEFINED EXCEPTION" in a Package detail
This is a fallback label indicating a combination of permission state and source that the system has not classified. Please submit a support ticket including the Package ID and the permission name.
