• Application Security - Roles Pages
  • Application Security - Roles|Search Page
  • Application Security - Roles|Basic Page
  • Application Security - Roles|Labels Page
  • Application Security - Roles|Preferences Page
• Configuring Roles
  • Creating a Role
  • Suppressing Warning Messages
  • Setting Preferences for the Role
  • Setting the Default Customer User Role
  • Resetting Default Preferences for the Role
  • Modifying a Role
  • Deleting a Role
• Configuring AudienceView Online Roles
  • Forcing Email Addresses and Phone Numbers as Usernames

User Role Section

The following image illustrates the user role section of the Application Security application Roles|Basic page:

The user role section of the Application Security application Roles|Basic page contains the following properties:

Field	Description
Name	The user role name.
Description	The description of the user role.
Role Group	The group associated with the role.
Offer Time Out	The amount of time that the user role has to complete an order before an offer times out and the seats become available again. This is particularly important for AudienceView Online users. The defined 'Offer Timeout' values override each other in the following order: The Venue Configuration application Performance|Calendar page The Venue Configuration application Series|Calendar page The Application Security application Role|Basic page The Registry application Registry::EN::Session::Offer Timeout node Enter a relative date into the field or click or to select the relative date. For more information, refer to Using Relative Dates and Times.
Reservation Time Out	The predetermined length of time from the reservation creation date that offers will remain available for the role. Enter a relative date or date into the field or click or to select the date or relative date. For more information, refer to Using Relative Dates and Times and Using the Calendar to Select a Date. The time/date defined by the role will be overridden by any other 'Reservation Time Out' settings placed on a series, performance, miscellaneous item or gift.
Reservation Valid Until	The predetermined length of time from the performance start date that offers will remain valid until. Enter a relative date or date into the field or click or to select the date or relative date. For more information, refer to Using Relative Dates and Times and Using the Calendar to Select a Date. The time/date defined by the role will be overridden by any other 'Reservation Time Out' settings placed on a series, performance, miscellaneous item or gift.
Card Failure Limit	The predetermined number of times that a credit/debit card transaction can fail for the role.
Use Username as	Determines what, if anything, that users will be forced to use as their user names: E-mail: Forces the user to use email address associated with the account as the username. Home Phone: Forces the user to use home phone number associated with the account as the username. Mobile Phone: Forces the user to use mobile phone number associated with the account as the username. Work Phone: Forces the user to use work phone number associated with the account as the username.   Information Leaving this dropdown blank will allow users to define their own usernames. If you select one of the options above, the following .asp labels should be reconfigured: Username should be changed to the appropriate option on the login.asp and forgotpassword.asp pages. Email Address should be changed to Confirm Email Address on the forgotpassword.asp page.   Warning Do not change this setting if customer accounts already exist in your system. Changing the setting, for example, to force customers to use their 'Home Phone' numbers as their usernames will cause the 'Home Phone' field to become a mandatory field. If a customer account does not have a value stored in the 'Home Phone' field, the assumption that all of the data coming from database is valid is broken, and customers will not be able to access their accounts.
Best Available Max Seats per Row (AudienceView 6.8.10 HotFix 2)	Defines the maximum number of seats that will be allowed per row when using best available. For example, if this value is 5 and an Online user requests 24 seats, best available will return four rows of five seats and one row of four seats. If this field is empty best available returns all of the seats in single row. Desktop users can override this value using the Customer Services application Seats|Best Available page's 'Number of Rows' field.
Desktop Article	Defines the article that will be displayed on the AudienceView Desktop if a dashboard has not been selected. By default, the Default Dashboard Article is displayed if a dashboard has not been selected. Enter the article name or click to search for the article. For more information, refer to The Find Articles Dialog Box.
Default Price Type	The default price type that the role can sell (e.g. if Adult is selected then, by default, the Adult price type will automatically be selected for the user).
Default Dashboard	The default dashboard that will appear on the AudienceView Desktop. Once a dashboard report has been saved, it will appear in this dropdown. The 'Default Dashboard' can also be set using the Application Security application Users|Basic page or clicking on the loaded Dashboard ( indicates the default Dashboard). Changing the default on either of these pages will update the other. Both override the setting on this page.
Default Payment Method	The default payment method defines the types of payments that a particular role can except (e.g. if Cash is selected then, by default, the Cash payment method will automatically be selected for the user).
Default Delivery Method	The default delivery method defines the ways in which the role can deliver tickets to customers (e.g. if Window Sales is selected then, by default, the Window Sales delivery method will automatically be selected for the user).
Email From Address	The email address that any correspondence will be sent from for the role.
Email Template	The default Order Confirmation Email that will be sent by the role: Order Confirmation Email (text/avdocument): Creates a PDF version of the order confirmation. Order Confirmation Email (text/html): Creates an HTML version of the order confirmation. Order Confirmation Email (text/plain): Creates a plain text version of the order confirmation. The default Order Confirmation Email can also be set globally via the Registry. For more information, refer to Setting the Email Confirmation Template.
Default Cancel Tickets Template	The default Cancel Tickets Confirmation Email that will be sent by the role: Cancel Tickets Confirmation Email (text/html): Creates an HTML version of the cancellation email. Cancel Tickets Confirmation Email (text/plain): Creates a plain text version of the cancellation email. The default Order Confirmation Email can also be set globally via the Registry. For more information, refer to Setting the Cancel Tickets Confirmation Email Template.
Default Invoice Template	The default Invoice Email that will be sent by the role: Confirmation Email / Invoice (text/avdocument): Creates a PDF version of the invoice. Confirmation Email / Invoice (text/html): Creates an HTML version of the invoice. Confirmation Email / Invoice (text/plain): Creates a plain text version of the invoice. The default Order Confirmation Email can also be set globally via the Registry. For more information, refer to Setting the Email Invoice Template.
Default Ship To Template	The default Ship-To Confirmation email that will be sent by the role: Order Confirmation Email Ship To (text/html): Creates an HTML version of the ship-to order confirmation. Order Confirmation Email Ship To (text/plain): Creates a plain text version of the ship-to order confirmation. The default Ship-To Confirmation can also be set globally via the Registry. For more information, refer to Setting the Order Confirmation Ship To Template.
Available Invoice Templates	The Confirmation Email templates that are available to the role: Confirmation Email / Invoice (text/avdocument): Creates a PDF version of the invoice. Confirmation Email / Invoice (text/html): Creates an HTML version of the invoice. Confirmation Email / Invoice (text/plain): Creates a plain text version of the invoice. To make more than one Confirmation Email / Invoice template available to the role, hold CTRL or SHIFT while making your selections.
Options	The options that the role can: Allowed To Leave Single Seats: The role will be able to leave a single seat available within a row/section of sold seats. Display Per Ticket Charges on Seat Selection: The role will be presented with the per ticket charge values when selecting seats. Enable Add-On: The role will be presented with any add-on articles/items that have been associated with the selected items, and must be explicitly dismissed by the user. Add-on article/item links will still be available if this option is not selected, but the user must click on the available links to view the article/item. Enable Upsell: The role will be presented with any upsell articles/items that have been associated with the selected items, and must be explicitly dismissed by the user. Upsell article/item links will still be available if this option is not selected, but the user must click on the available links to view the article/item. Manage Over Caps: The role will be able to exceed limits while adding items to an order; however, the role will not be able to create orders exceeding the limits. As of AudienceView 6.8.11 HotFix 7, 6.8.13 HotFix 2 and 6.8.14, the items can be added to the shopping cart. The excess items then must be assigned to customers in the user's contacts list before the order can be completed.  No Access to Open Seats: The role will not be able to sell/purchase open seats, and will only be able to sell/purchase seats that are on hold. Send Customer Creation Email: The role will send an email to the address associated with an account when the account is created. To make more than one option, hold CTRL or SHIFT while making your selections.
Allowed Address States	The default address states that the role can accept and complete an order: Not Verified: The user has not attempted to verify the address against QAS (i.e. the user did not click on the Lookup Address button after entering the address). If this state is selected here, the user is allowed to save addresses that have not been checked by QAS. This state is selected by default. If a verified address is updated, the address state returns to Not Verified. Caution If Not Verified is selected, the other three options will not be applied. None of the addresses will be verified. Verified: The user attempted to verify the address against QAS, and the address was found to be valid. If this state is selected here, the user is allowed to save addresses that QAS deems to be valid. Not Applicable: The user attempted to verify the address against QAS, but it could not be verified (e.g. address is located in a country not covered by QAS). If this state is selected here, the user is allowed to save addresses that QAS cannot verify. Invalid: The user attempted to verify the address against QAS, but it was found to be invalid, and the user did not correct it. If this state is selected here, the user is allowed to save addresses that QAS deems to be invalid.

Assign Users Section

The following image illustrates the assign user section of the Application Security application Roles|Basic page:

The assign user section of the Roles|Basic page allows you to assign specific user's to the current role. To assign an available user to a role, select the users from the Available Users list and click '>>' to move them to the Assigned Users list. To remove a user from the Assigned Users list, select the user and click '<<'.

Information To select more than one user, hold CTRL or SHIFT while making your selections.

Restrict Venues Section

The following image illustrates the restrict venues section of the Application Security application Roles|Basic page:

This section contains the following properties:

Property	Description
Available Roles	User roles that have the ability to modify the venue and create/modify events taking place at the venue.
Restricted Roles	User roles that do not have the ability to modify the venue and create/modify events taking place at the venue. Admissions to venues can still be sold by the 'Restricted Roles' through the Customer Services application; however, 'Hold Types' cannot be updated on the Customer Services application Seat|Map page.   Information If users are part of a restricted role, they can load and view the venue and any associated performance through Venue Configuration, but they cannot update the venue or the performances (clicking 'Apply' displays a message indicating that the action is not allowed); users in a restricted role are still able to update seats, holds, price zones and fill zones (best available) through Performance Management.
	Adds selected roles from the Available Roles to the Restricted Roles column.
	Adds selected roles from the Restricted Roles to the Available Roles column.

Suppressed Warnings Section

The suppressed warnings section allows you to prohibit certain warning messages from appearing for a particular role. For example, by default if an order is unpaid, users must enter a reason. Suppressing the warning enables users to create an unpaid order without entering a reason.

The following image illustrates the suppressed warnings section of the Application Security application Roles|Basic page:

If your list of suppressed warnings exceeds the maximum list size set in the Registry application's Registry::EN::Application node's 'Max List Size' field, the icon will appear next to list.

For more information, refer to Suppressing Warning Messages.

Role Data Section

The following image illustrates the role data section of the Application Security application Roles|Basic page:

The role data section of the Application Security application Roles|Basic page contains the following properties:

Field	Description
Data [1-8]	Enables you to store additional information specific to your organization. Any data entered into these fields is searchable through Business Intelligence. To modify a data field label, navigate to the Registry application Registry::EN::Business Objects::TSuserRolesBO::User Role node and select the field that you want to re-label.
Multidata [1-2]	Enables you to store additional information specific to your organization. To add additional fields, click or press CTRL+TAB once you have made an entry. Any data entered into these fields is searchable through Business Intelligence. To modify a multidata field label, navigate to the Registry application Registry::EN::Business Objects::TSuserRolesBO::User Role node and select the field that you want to re-label.