AudienceView Connect
AudienceView Documentation

AudienceView Applications

AudienceView contains the following applications:

Module Description
AudienceView Desktop Used to configure AudienceView applications and for ticket box office sales.
For more information, refer to AudienceView Desktop.
AudienceView Online Used for online ticket sales.
For more information, refer to AudienceView Online Configuration Guide.
AudienceView Kiosk Used for kiosk ticketing sales.
For more information, refer to AudienceView Kiosk Configuration Guide.
AudienceView Access Control Used for scanning tickets and marking tickets.
For more information, refer to Configuring Access Control.
AudienceView POS (point of sale) Used to sell concessions and merchandise quickly and easily though a touchscreen-friendly interface.

Your system administrator can control your access to AudienceView using:

  • Users
  • Roles
  • Groups


A user identifies someone who can access AudienceView. Users have user names and passwords that they can use to logon to AudienceView. A user can be anyone from an administrator or box office ticket seller to an anonymous customer accessing online sales. Users can be assigned one or more groups and/or roles that determine how they can interact with AudienceView. 


Roles restrict a user's access within AudienceView and are most often used to reflect an organization’s sales channels. Access to the following items can be restricted by role:

  • Venues
  • Series, Performances and Bundles
  • Service Charges and Miscellaneous Items
  • Payment and Delivery Methods
  • Hold Types
  • Producers
  • Fundraising Programs

When such an item is created, roles are granted access. When users log on to AudienceView with an allowed role, they can access the item. A user's group determines what the user can do with the item. A user may have multiple roles associated to them, but when logging in, they must choose a single role to use. This role can be changed at anytime using the Options menu.


A group defines the functionality a user has permission to view and perform. For example, a group specifies whether users can create, modify and/or delete an item in the application, what pages they can view, and so on. Groups and roles work together to define a user’s experience with the application. For example, for users to sell tickets, they must be given access to the performance (by means of their role) and access to selling functionality (by means of their group).