Access Management Studio

Standard access rights are spread over groups, record rules and views, which is hard to maintain. This module adds an Access Studio menu where an administrator defines one access rule with its users and everything to restrict. Restrictions cover menus, fields, actions, buttons and tabs, filters and group-by options, the chatter and developer mode, plus record domains. It works across all installed apps and supports multiple companies. Read-only users are blocked from writing data, and the administrator can never be made read-only. The benefit is showing each user only what is needed from one screen.

1. 1

   Create an access rule

   In the Access Studio menu the administrator creates an access record with a Name, the Users it applies to and the Companies. A smart counter shows the number of rules and an Update action refreshes them. Rules can be archived without deletion.

   • Fields: Name, Users, Companies
   • Button: Rules counter and Update
   • Archive instead of delete
2. 2

   Hide menus

   The Hide Menu tab lets the administrator choose menus that will be removed for the users of the rule. The menus disappear from the navigation for them. Unrelated users are not affected.

   • Tab: Hide Menu
   • Multi-select of menus
3. 3

   Control fields

   The Hide Field lines pick a model and its fields and set them Invisible, Read-Only or Required, with an option to remove the external link on relational fields. This tailors forms per user group. The rule applies to every view showing the field.

   • Options: Invisible, Read-Only, Required
   • Option: Remove External Link
4. 4

   Restrict actions on a model

   The Remove Action lines select a model and hide Export, Create, Edit, Delete, Archive/Unarchive, Duplicate or Chatter, or make it read-only. Specific views, server actions and report actions can also be hidden. The Action menu of lists and forms respects these choices.

   • Options: Hide Export, Create, Edit, Delete, Archive, Duplicate
   • Hide views, server actions and reports
5. 5

   Hide buttons, tabs and filters

   The Button/Tab Access lines choose buttons, pages or links (including smart buttons) of a model to hide, and Hide Filters/Group By lines hide search filters and group-by options. The available nodes are read from the model views. This removes clutter and risky actions.

   • Node types: Button, Page, Link
   • Node types: Filter, Group By
   • Smart buttons supported
6. 6

   Apply record domains and CRUD limits

   Access Domain lines apply a domain filter to a model and allow or deny Read, Create, Write and Delete. The domain is validated when saved. This works like record rules but is managed from the same rule.

   • Domain filter per model
   • Rights: Read, Create, Write, Delete
7. 7

   Read-only users and developer mode

   Ticking Read-Only makes all users of the rule unable to change data, and a rule raises a message saying the user is read-only. Hide Chatter and Disable Developer Mode can be set for the same users. Setting the admin user as read-only is refused.

   • Options: Read-Only, Hide Chatter, Disable Developer Mode
   • Admin cannot be read-only

Back to version applications