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

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

Access to requests

Defining access to requests is important when you want to keep certain groups of users from knowing that certain requests exist. For example, if you use BMC Remedy AR System as the outsource help desk for several companies, you can assign access to requests so that only the company that submitted the request can see it.

You determine which groups or roles have access to a request through the Request ID field (field ID 1). If a group or role does not have access to that field, the group or role has no access to the request, even if it has access to other fields in that form.

You can grant access to members of explicit groups or roles. For example, you can give managers access to all requests. You can also grant access to members of implicit groups. For example, submitters can see their own requests but not those submitted by other users. For more information, see Controlling access by using implicit groups--Row-level security.

The following figure lists the questions that you can ask to determine the access that users have to requests in BMC Remedy AR System.

Accessing requests
(Click the image to expand it.)

For more information, see:

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

Comments