Defining User Permissions

Once you have enabled BarTender's integrated security system, you can specify permissions for Windows users and groups (defined locally or on the Windows domain) using the User Permissions page, located within the Security node of the Administration Console. By specifying user permissions, you can define what actions a user can perform based on the identity of the person logged into a computer. For example, you may want an employee in a "Print Operators" group to be able to view and print BarTender documents, but to be unable to change the template design in any way.

Once you have enabled BarTender's security settings, any Windows user or group not listed in the Users and Groups pane will automatically be denied access to all actions within the BarTender Suite.

When specifying the permissions for users and groups you will need to understand how permissions are managed within the BarTender suite.

ClosedPermission Status

The User Permissions page allows you allow or deny permissions for specific actions for the different applications in the BarTender Suite.

If neither Allow or Deny are enabled, permissions are inherited from a user's group membership. If a user is not a member of a group, then the absence of a selected check box is equivalent to the Deny option being enabled.

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 settings for a number of people, instead of repeatedly configuring settings for one individual user after another.

When defining an individual user's permissions, you will need to take into account the permissions of every group the user is a member of. BarTender determines a user's ability to perform an action based on the following rules:

ClosedLinked Actions

Some actions are linked to other actions, so that granting access to perform one action automatically grants access to perform another. Similarly, if you deny the ability of a user to perform an action, it may automatically change the status of another action. Consider the following example: If you deny someone the ability to 'Run' BarTender, you also prevent them from modifying templates, printing documents, or saving documents (since you have to open BarTender to perform any of those actions). Therefore, if you select Deny for 'Run', all other actions within BarTender will automatically switch to a Deny status.

In This Section