To Add Access Rights to a Project

When you create or change the access rights by screen, role, or user in an instance of MYOB Acumatica, these changes are saved in the database for the current tenant.

Addition of Access Rights to the Customization Project

You can add to a customization project the access rights of roles by screen that are saved in the database for the current tenant. To do this, perform the following general actions:

  1. You open the customization project in the Customization Project Editor. (See To Open a Project for details.)
  2. In the navigation pane, you click Access Rights.

    The Access Rights page opens.

  3. On the page toolbar, you click Add New Record.
  4. In the Add Access Rights for Screen dialog box, which opens, you select the forms (screens) for which the access rights should be configured. You can add all forms by selecting the Included check box (see the following screenshot).
    Figure 1. Adding the access rights to the customization project


  5. You click Add to add the selected access rights of roles to the table on the page and close the dialog box.

The system adds to the customization project the data from the database for the selected access rights of roles. You can view the HTML source code of each project item on the Edit Project Items page (see the following screenshot).

Figure 2. Viewing the HTML code of the ScreenWithRights item included in the project


You can change the merge rule for any added screen by selecting the needed option in the Merge Rule column on the Access Rights page. A merge rule determines the way the system applies the access rights from the customization project during its publication. The following options are available:

  • Grant All: To set the access rights to Granted for all user roles in the system.
  • Revoke All: To set the access rights to Revoked for all user roles in the system.
  • Copy from Current Tenant (default): To copy the access rights from the current tenant. For roles that are not included in the customization project, the system handles access rights based on the availability of the form in the target tenant as follows:
    • The form exists in the target tenant: Access rights remain unchanged.
    • The form does not exist in the target tenant (that is, it's a new form with no access rights specified for it in this tenant): The system sets the access rights to Revoked.

A customization project may not include explicitly specified access rights on the Access Rights page. In this case, when the customization project is being published, the following rules are applied to each site map node:

  • If the site map node does not exist in the target instance, the site map node will not be available for any roles; the access rights will be set to Revoked. That is, after the customization project has been published, you need to grant the access rights explicitly.
  • If the site map node already exists in the target instance, the existing access rights remain unchanged.
Tip: The site map node corresponds to the screen selected in the Screen Name box of the Add Access Rights for Screen dialog box. The site map node is considered existing in the target instance if the form (screen) is listed on the Site Map (SM200520) form.

Publication of Multiple Projects with the Same ScreenWithRights Items

If you publish multiple customization projects that contain the same ScreenWithRights items, the system performs the following actions:

  • If a level is specified for each of the projects, merges the projects, adds to the merged project the ScreenWithRights items from the project with the highest level, and displays a warning that the ScreenWithRights items from other projects will be ignored
  • If the projects have the same level or no level is specified for at least one of the projects, does not publish the projects and displays an error