Recently I learned about a superadmin role which caused some confusion. In the most recent DLeap versions, users in this role may see extra actionbuttons regardless of workflow permission settings in applications.
Hence I would like to clarify all DLeap admin roles as they are documented not enough.
- There should be Volt App Users group with Editor access and Delete documents permission configured on VoltBuilder.nsf ACL which grants access to the Manage page to developers. Only people in this group can create their own apps. Other users can only access running applications once they learn the appllcation URI.
- There is [VoltAppManager] role which is a superadmin role that allows administrator to access the Manage page and see all apps regardless of their access permissions. The workflow permissions still apply but [VoltAppsManager] can modify stage permissions as they wish and thus reconfigure the application security. The business case for this is to take ownership of apps created by users who are no longer available.
- There is [LeapAdmin] role which grants access to Admin dashboard and nothing else. In other words, [LeapAdmin] role does not grant superadmin permissions to manage apps.
@Christopher Dawes can you confirm that the above is correct, please?
Reference:
- [VoltAppsManager] and [LeapAdmin] are mentioned on page post-installation tasks
- Admin and SuperAdmin groups are mentioned in relation to admin application dashboard only
- "Volt app authors" group is documented on page controlling who creates applications