This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Permissions and structures

Permission for an BMC Remedy AR System object is generally defined by specifying the list of groups that can access it (use the ARInternalIdList structure). The groupList parameter for the active link functions is of this type.

For schemas, fields, and containers, however, you can assign different levels of access to different groups. Permission for these objects is defined by the groupList (schemas and containers) and permissions (fields) parameters, both of which are pointers to structures of type ARPermissionList (see the following figure).

Structures used to define field and schema permissions 

 

Each ARPermission in the list represents a particular access control group and has the following elements:

Group ID

Internal ID of the group.

Permission Level

Integer that specifies the access privileges for the group. The following tables list the valid integers for schemas, containers, and fields.



Schema/Container permission values for ARPermissionStruct

0

AR_PERMISSIONS_NONE

Group has no access to the schema or container.

1

AR_PERMISSIONS_VISIBLE

Group can see the schema or container.

2

AR_PERMISSIONS_HIDDEN

Group cannot see the schema or container.



Field permission values for ARPermissionStruct

0

AR_PERMISSIONS_NONE

Group has no access to the field.

1

AR_PERMISSIONS_VIEW

Group has read-only access to the field.

2

AR_PERMISSIONS_CHANGE

Group has read-write access to the field.

Depending on whether you are assigning permission to a schema or a field, different privileges are associated with the possible values.

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

Comments