Show Contents / Index / Search

Restricting User Access to Application Features

By removing access to select Reflection application features, you can disable the functionality of features you do not want to support.

There are three ways to remove application features:

  • Group Policy
    Use Microsoft Group Policy Object editor, along with the .ADM and .ADMX files installed with Reflection to create a policy, and then deploy the policy.


  • Permissions Manager
    Open Permissions Manager from a workstation installation directory, remove access to the features, and then save the results as an .access file. Then, you can deploy the .access file by adding it to a companion install package, and deploying the companion install package.


  • The Attachmate Customization Tool
    Create a companion database and open Permissions Manager from the Attachmate Customization Tool interface. Remove access to the features, save the companion install package, and then deploy the companion install package.

Note: While you will most likely choose to restrict settings and actions via either Group Policy or by deploying Reflection .access permission files – you can use both. Individual permissions are merged with the following precedence (highest to lowest):

  • Group Policy – user
  • Group Policy – machine
  • Local permissions file (.access)

In this Section

Restrict Access with Group Policy

Restrict Access with Permissions Manager

Restrict Access to Reflection 2011 features with ACT

Permissions Manager

Permissions Manager Reference Guide