|
Worksheet Use this worksheet to plan your group configuration before you start building them or updating them.
For more information about configuring groups, refer to Application Security - Groups. |
Groups control what things users can do. For example, for users to sell tickets they must be given access to the event (by means of their roles) and access to sales functionality (by means of their groups).
Groups consist of three components which control everything you can do within AudienceView Unlimited. They are:
•Content: The specific pages users can see. Ticket sellers would only see the Customer Services pages, for example, while a member of your Development team would see Customer Services and Funds Management.
•Permissions: Which buttons and functions users can use on visible pages. Ticket sellers may not have permission to refund tickets, but a supervisor may have that permission and can override the ticket seller’s session.
•Attributes: Allows you to make fields visible or not, as well as make fields required or optional. Attributes override any settings you may have configured in the Registry.
Depending on the size of your organization, there are two typical ways to configure group permissions:
•A single group assigned to a user.
•Multiple groups assigned to a user.
Single Group Per User
The most common approach is to create a group for each department and ensure that they have the content and permission to do everything required for their day-to-day jobs. This approach works well for larger organizations where staff typically work exclusively in a single department and their responsibilities are clearly defined.
You would have a group for your ticket sellers, another for ticket office management, and groups for development, marketing and financial departments.
Multiple Groups per User
An alternative method is to create groups that build onto each other. Every user starts with basic access to the application (typically Customer Services), and groups are created with the content and related permissions that are added to the user. This approach works well for more nimble organizations where staff may work for multiple departments and will need access to multiple areas. You’ll want to ensure that you properly document your groups so that you can remember your groups’ configuration.
Regardless of which approach you take, you should have a small set of users with all content and permissions. Typically, it would be your system administrators since they’re the people involved in managing your system.
For new clients, both types of groups are included. Here are the groups that are typically preloaded in a new installation:
•Single Group per user:
oAgent: A possible group for your ticket agents.
oAV Administration: This group has all content and permissions.
oCustomer Service: Another option for your customer service staff.
oGate Management: For scanning-only users.
oMigration: Typically used for migrating legacy system data.
oSched: Assigned to the Scheduler user for running reports and scripts.
oStubHub Administration: No longer used.
oTicket Office Manager: A group for Ticket Office Management.
•Multiple groups per user:
oBusiness Intelligence and Reports.
oContent Management.
oCorrespondence.
oSaved Business Intelligence and Reports.
•Website-related Groups:
oAnonymous WebSales.
oAnonymous WebSales - Give.
oCreate Event Owner Profile.
oWebSales.
The Websales Groups
There are two groups that are included that work together to control your site: Anonymous Websales and Websales. When customers arrive at your site they’re browsing anonymously using the Websales user. The Websales user belongs to the Anonymous Websales group. Once a customer has logged in, they move to the Websales group and are granted all of its permissions. When you’re making changes to labels, fields, and other attributes it may or may not be necessary to make the changes to both groups.
The AV Administration Group
This group is necessary to update your system to new versions of the application. Do not adjust its name. When new features are introduced, this group is assigned the new permissions. If you want to try out new features when you’re ready, you can save a copy of this group and add your system administrators to it.
Refer to our product documentation for further information.
