This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Creating a Subadministrator security role

Administrators, members of the Administrators group, can use Developer Studio  to view every AR System server  object and can modify any object that is not reserved by another user. You can use Subadministrator Permissions to grant administrator access to a subset of existing forms, local applications, and workflow to subadministrators, members of the Sub Administrator group. A subadministrator with administrator access to a server object can use BMC Remedy Developer Studio to view and modify it the same as an administrator. A subadministrator can also create objects.

Subadministrators can perform the following functions:

  • Log on to  Developer Studio
    When you log on as a Subadministrator, the server icon in Encryption Security Navigator has a yellow badge with a letter S instead of a green badge with a letter A.
  • Create local applications, forms, and packing lists.
    When you create an object as a subadministrator, set the Subadministrator Permissions so that you can access the object.
  • Modify local applications, forms, and packing lists to which they have administrator access.
  • Create and modify filters, active links, and escalations associated with forms to which they have administrator access.
  • Create and modify active link guides, filter guides, images, and menus.

Subadministrators cannot perform the following functions:

  • Modify local applications, forms, and packing lists to which they have no administrator access.
  • View or modify forms to which they do not have subadministrator access in local application or packing lists to which they do have administrator access.
    If a user has subadministrator access to a local application or a packing list, but not to a form in the local application or packing list, the form is not listed in the object list or editor.
  • Create or access deployable applications.
  • View or modify roles, distributed mappings, or distributed pools.
  • Change server information settings.
  • Release licenses of users currently accessing BMC Remedy Encryption Security.

After you have granted a group subadministrator permissions for an application, the members of that group can modify the application's appearance, group permissions, help text, and change history. Subadministrators can also change which forms are included in an application object, although they cannot alter the forms themselves unless they have administrator access to them. 

The following figure is an example of using Subadministrator Permission to enable users to maintain some objects on an AR System server.

Users administering forms

To make a user a subadministrator

  1. Include the Sub Administrator group in the Group list in the User form entry for every user who is to be a subadministrator.
    A member of the Sub Administrator group must have a fixed license.
  2. Give a group, of which the user is a member, administrative access to the appropriate local applications, forms, and guides.
    To give all members of the Subadministrator group administrator access to an object, give the Public group Subadministrator permission. To divide administrator access between groups, create a group for each collection of objects, for example, Engineering Subadministrators and Sales Subadministrators.

    To give subadministrators access to an AR System server that has object reservation enforced, you must grant them access to a form. See Version control in AR System.

To grant subadministrator capabilities to a user

  1. In the Mid Tier , open the User form of the appropriate server in Search mode.
  2. Perform a search to find the user you want to give administrator access to.
  3. Make the following changes:
    • From the Group list menu, select Sub Administrator.
      The list must include the Sub Administrator group to give the user the potential to be a subadministrator.
    • From the License Type option list, select Fixed.
      You must assign subadministrators a Fixed Write license.
  4. Save your changes.
  5. Give subadministrator permission for the form to a group or role to which the subadministrator belongs, as described in the following procedure.

To assign subadministrator permissions to forms, local applications, and packing lists

  1. In Developer Studio , open the appropriate form, local application, or packing list for modification.
  2. Access the Subadministrator Permissions:
    • For a form, select the Definitions tab. In the Permissions panel, expand the Subadministrator Permissions sub-panel.
    • For a local application or a packing list, in the Properties tab, click the Permissions > Subadministrator Permissions property and then the ellipses button.
  3. In the Subadministrator Permissions page or dialog box, use the arrow buttons to move the appropriate groups into the Permissions list. 
    When assigning permissions for an application, you must assign the same permissions as are assigned for the individual forms in the application.

The members of the group or role have the same privileges and permissions that an administrator has for that object.

Was this page helpful? Yes No Submitting... Thank you