Understanding Permissions and Their Usage

CUR8 Permissions provide security and flexibility for your Organization and individual Projects by providing segmented access levels to view and edit information.

This article explains the CUR8 Permission structure and how it can be leveraged to provide security and privacy. 

What are CUR8 Permissions?

We know it takes a village to make a Project happen. Your community may have many people, and they each need access to certain details of your Project while keeping other aspects confidential.

You do not want everyone to have access to your financial reports or have access to creating a Project, but you may have people you'd like to have access to ticketing for your project. CUR8's varied permission levels allow nuanced levels of accessibility for all your Participants. 

What types of Permission Levels does CUR8 have?

CUR8 permissions are structured into two main levels: Organization Level and Project Level. Each level has its own set of roles and responsibilities, ensuring a clear and organized system of access management.

• Organization Level:
  • Admin
  • Admin Moderator
  • Project Creator
• Project Level:
  • Project Managers
  • Ticketing Managers
  • Box Office Sales

Permission Level Examples:

These are suggestions only. Please consider your organization's unique structure and people when deciding permission levels.

CUR8 Permission Example Chart

What tasks and access do Organization-Level Permissions have?

Admins

• Admin requires a CUR8 login.
• This is account-level permission with full access to the organization(s).
• Create and manage Projects.
• View and edit all schedules, people, locations, assets, communications, etc.
• View and download account reports, including donation reports.
• Add other Admins and project creators and assign all other permission levels.
• Can create coupons.
• Can issue refunds even when organization refunds are off.
• Admins can purchase CUR8 credits.
• Access to view/change Join Code
• Access to view/restore Archived Projects
• Admins can scan tickets.
• Admins cannot update another CUR8 user's person detail, including:
  • profile picture
  • contact information

Admin-Moderator

Admins can have additional permission to be Moderators for Headshots and Communication. The first admin for an organization is automatically assigned as a Moderator - all further Admin Moderators must be assigned.

Project Creator

• Project Creator requires a CUR8 login.
• Project Creator (PC) can create Projects and Flex Passes on the Organization's behalf.
• A PC can Create Locations
• A PC cannot view projects they did not create.
• Being a Project Creator automatically assigns the PC as a Project and Ticketing Manager for any project they create.
  • An Admin may adjust these permissions after a project is created.

What tasks and access do Project-Level Permissions have?

Project Manager

• Project Manager requires a CUR8 login.
• Project Managers can access only the projects for which they are a Project Manager.
  • scheduling creation and management
  • communication creation and management
  • asset management
  • location management
  • marketing material
  • people management
• PMs cannot manage or edit Projects for which they are not Project Managers.
• Users at this permission level can only change another person's project management permission level. They cannot change a ticketing manager or make themselves an Admin.
• PMs can request additional notification credits from an organization's Admin.
• PMs cannot scan tickets
• Cannot issue refunds.
• Cannot create coupons.
• PMs do not have permission to view:
  • attendee ticketing information
  • adjust ticketing permissions
  • accounting reports
  • create coupons

Ticketing Manager

• Requires a CUR8 login.
• Ticketing Managers (TM) can access sales and attendance reports on their assigned Project(s).
• TMs can process attendee tickets.
• TMs can create coupons.
• TMs cannot adjust access or allow access for Project Management.
• TMs can scan tickets.
• Can issue refunds for their projects, even when organization refunds are off.
• Calendar Access
  • TM can see ticketed event dates
  • their own schedule.

Box Office Sales

• Requires a CUR8 login.
• Box Office Sales users can access ticket sales and attendance reports.
• They can scan tickets.
• Can issue refunds for their projects, even when organization refunds are off.
• Limited access to the Project.

What about People who do not have any Permission access?

There are also two other groups within CUR8 to be aware of. While these users do not specifically require permission to be granted, they do have limited permission to access the CUR8 platform.

Participant

• • Requires a CUR8 login.
  • This person has logged in to CUR8 because they are participating in an event associated with an organization.
  • Limited access to information that pertains to them:
    • Their headshot, bio, contact information, notification preferences
    • Their tickets, their calendar, their communications, their assets

Attendee

• • Does not require a CUR8 login
  • This person has come to CUR8 to purchase tickets for your project.

How do I manage permissions for an Organization or Project?

For step-by-step instructions and more information, please head over to Managing Permissions.

How many Admins can I have? What about the other permission levels?

As many as you need—there isn't a limit to the number of people who can be assigned at any given permission level. Do whatever works best for your organization.

Your organization may have one or several People assigned as Admins, multiple project managers for a single event, or several People who need access to ticketing to assist with Attendee ticket sales without having access to financials. You can set permissions in a way that works best for your organization.

How do I view/change a Person's Permissions?

Managing Permissions walks you through how to view or update permissions at both the project and organization levels. 

Creating a CUR8 Project