• Application Security Group Pages
  • Application Security Group-Search Page
  • Application Security Group-Basic Page
  • Application Security Group-Labels Page
  • Application Security Group-Permissions Page
  • Application Security Group-Attributes Page
  • Application Security Group-Content Page
• Configuring Groups
  • Creating a Group
  • Configuring Group Permissions, Attributes and Content
    • Configuring Group Permissions
      • Assigning Subsystem Permissions to a Group
      • Applying a Group Filter to a Subsystem
      • Modifying a Group Permission
      • Deleting a Group Filter
    • Configuring Group Attributes
      • Assigning a Group Attribute
      • Modifying a Group Attribute
      • Deleting a Group Attribute
    • Configuring Group Content
      • Assigning Group Content Visibility
      • Modifying Group Content Visibility
  • Enabling User Groups to Refund Payments
  • Enabling Partial Offer Acceptance
  • Setting the Default Customer User Group
  • Modifying a Group
  • Copying a Group
  • Deleting a Group

You can control what a user can see and do within AudienceView by applying permissions, attributes and content at the user or group level.

• Permissions: Define what actions a user can perform within AudienceView. In addition, filters can be used to restrict which records a user can search for and open.
• Attributes: Control the fields that are displayed to the user. For example, expose or disable a field on a page, set default values, and so on.
• Content: Enables you to prevent users from viewing certain areas of the application. This is generally done to prevent users from viewing icons or tabs for areas of the application which they do not have permission to use.

Information Some permissions affect each other, so consider your users’ needs carefully. For example, to give a user permission to modify an existing bundle you must also give the user permission to search for existing bundles.

Permissions, attributes and content settings can be applied at the user or group level. If applied at both levels, users are given the combined settings. Therefore, what functions the user is allowed to perform and what parts of the application the user has access to are the sum of the user and group settings. The only exception is for permission filtering where if filters are applied at the user level and not at the group level, the user’s settings are always used. If a user belongs to multiple groups with different levels of permission, users are again given the combined permission.

Consider the following examples:

• Permissions: The user is enabled to create performances but the same permissions are not given to the group. When logged in, the user will be able to create performances.
• Permission Filtering: There is no filtering for the group, but you set filtering for the user. The filtering for the user is always used.
• Attributes: The group’s settings have a modified field label while the user’s settings have a default value for the field. The user would see the label from the group settings and the value from the user settings.
• Content: The user is enabled to access online sales but the group is not enabled for the same access. When logged in, the user will be able to access online sales.