Open topic with navigation

Defining User Permissions

After you enable security in BarTender, you can specify permissions for the Windows users and groups that are defined locally or on the Windows domain. To do this, use the User Permissions page, which is located in the Security node of Administration Console. (For information about how to enable security, refer to Enabling Security.)

By specifying user permissions, you can define what actions a user can perform based on the identity of the person who is logged in to a computer. For example, you might want an employee in a "Print Operators" group to be able to view and print BarTender documents but not to change the template design in any way.

After you configure the BarTender security settings, any Windows user or group that is not listed in the Users and Groups pane is automatically denied access to all actions within the BarTender Suite.

When you specify the permissions for users and groups, you need to understand how permissions are managed within the BarTender Suite.

ClosedPermission Status

Use the User Permissions page to allow or deny permissions for specific actions for the different applications in the BarTender Suite, as follows:

If you do not specify either Allow or Deny, permissions are inherited from the user's group membership. If a user is not a member of a group, then the absence of a specification is equivalent to specifying the Deny option.

ClosedInherited Permissions

Inherited permissions are permissions that are passed down from a group to all individual users in that group. By using groups, you can define the settings for many people at one time.

When you define an individual user's permissions, you must take into account the permissions of every group that the user is a member of. BarTender uses the following rules to determine a user's permission to perform an action:

ClosedLinked Actions

Some actions are linked to other actions, so that when you grant permission to perform one action, permission is automatically granted to perform another. Similarly, if you deny a user permission to perform an action, the status of another action may automatically change.

Consider the following example: If you deny someone the Run permission for BarTender, you also prevent him or her from modifying templates, printing documents, or saving documents, because a user has to open and run BarTender to perform any of those actions. Therefore, if you select Deny for the Run permission, all other actions within BarTender automatically switch to a Deny status.

In This Section