Making administrator functionality available to other users
Contents
Certain functionality is normally only available to user with the $ADMIN role. To allow other (non-administrator) users to get access to some of these specific functions too, Axiell Designer 7.13 and up allow you to add these functions as so-called application features to a .pbk and specify access rights for roles like you would for methods for example.
| 1. | Simply right-click your application structure file (.pbk) in the Application browser and select New > Add application feature in the pop-up menu. |
| 2. | A new Application features list header and underneath it a new application feature node will be added underneath the Users node in the .pbk. You can add multiple of these nodes, also by right-clicking the Application features list header and selecting New > Add application feature in the pop-up menu |
| 3. | Select the desired application feature node and edit it in the properties tab in the right window pane. Select one of the four currently available application features which you'd like to make available to certain non-admin roles too. Create a new application feature node for each feature type you'd like to do this for.  |
| 4. | Then list one or more roles in the Access rights list and assign the desired access rights. (Do not include $ADMIN.) When accessible (only roles with Full access and $ADMIN users), Record history reporting and View/recover deleted records (aka Journal maintenance) are available through the Maintenance menu in the main vertical menu on the left of the screen, while View active sessions is available under the Account menu in the same toolbar. For the Axiell Move option to become available (roles need Read access at the least) in the main menu, this functionality also must have been set up for the application. |
Note that users with sufficient access rights to an application feature can still be prevented access to that feature if their roles have not been assigned explicit access rights to a possible other application object related to the feature. This currently only applies to the Move functionality: if the Missions and Mission items data sources have (only) been assigned None access rights for $REST, for example, then users with any other role with sufficient access rights (Read in this case) to the Move application feauture still won't see the Move option in the main menu.