Articles by topic

Online Events & Live Streaming

Table of contents

Last updated:
September 5, 2025

Authorisation groups

Authorisation groups define which persons can participate in an event under which conditions and how access to the event website is permitted.

Screenshot of authorization groups in Oniva.

Authorisation groups

With authorisation groups, you can define which guests can register for your event and under what conditions. You can create as many authorisation groups as needed to address the specific requirements of your target audiences. For example, you can set up special conditions for VIPs, individual registration deadlines, or other tailored rules for different groups.

Each authorisation group must have at least one registration and access setting configured. These groups can be enabled either for access via personal accounts or for public access.

Screenshot of authorisation groups in an event

How does Oniva know which authorisation group a contact belongs to?

Oniva identifies contacts using their personal event links. If you use more than one authorisation group within an event, you must always assign the appropriate authorisation group when creating or importing contacts.

Selecting an authorisation group when adding a contact

Public access to the event website (without a personal link) is automatically assigned to the authorisation group that has "public" defined as its access method. If no authorisation group has public access enabled, the event can only be accessed with personal links. In this case, any access attempts without a personal link will be denied.

Error message "Access denied" when trying to access the event website

Restrict authorisation groups to accounts

If you restrict access to your event to accounts, only those who have an Oniva account will be able to register. This increases security, as only registered users gain access. However, this functionality is exclusively available to users with a premium licence. For instance, you could utilise this option to ensure that only your internal employees, who are already registered in the system, can participate in specific events.

Screenshot of an authorisation group restricted to accounts

In this case, the login is hidden behind a login screen. If you use single sign-on (SSO) for your organisation, for example, only access with SSO can be guaranteed to further increase security.

Login page for an event restricted to accounts

If you choose to set up the authorisation group for public access, various access methods are available under registration and access settings, which can be specified. You can choose between options such as public, private with password, or only with personal link to determine how your guests can access the event registration. This flexibility allows you to adjust access controls to fit the requirements and security policies of your event.

Restricting access for exclusive events

For events aimed at external guests without an account (e.g. customer events), access can be restricted by first deactivating all access methods under the menu item Login and access settings. An Excel list can then be imported under Event contacts. A personal event website link is then generated for each of the imported contacts, which can be sent with the invitation. This means that the event website can only be opened with a personal link.

For events aimed at users with accounts, an account group can be used or created to restrict access. Account groups can be created and edited in the workspace. Once the group has been created, it can be stored in the event under login and access settings to restrict access. If no account group is stored, all users of the account type can book.

Registration and access settings

Each authorisation group requires at least one registration and access setting. This defines the conditions under which the group can make bookings.

Tip: Multiple registration and access settings
In most cases, one registration and access setting per authorisation group is sufficient. However, an authorisation group can have multiple registration and access settings, but they must be clearly distinguishable. For example, different times could be used for different registration and access settings.
  • Start date & time: Specifies the start date from which these registration and access settings should be activated.
  • End date & time: Defines the date from which the registration and access settings will be stopped and thus no longer bookable. This date serves as the registration deadline for the authorisation group.
Tip: No date necessary
In most cases, no start date is needed. The start date is only important if registration is to be automatically opened at a certain time. If no registration deadline is configured, the end time can be left empty. The event will then be bookable until the last minute of the last booking options.
  • Booking note: Defines a note that appears above the booking options for this authorisation group. Example: "Please register for one session and one workshop each."
  • Maximum available slots: Sets the maximum number of possible guests for the corresponding registration and access settings. This capacity is used to limit the guests of an authorisation group (e.g., if only a limited number of employees or account managers can register for a customer event). The capacity of booking options can be set directly in the option. See also our article on capacities.
  • Costs: The costs specified in the registration and access settings are charged once per booking regardless of the selected options. To be able to record costs for a registration and access setting, payment settings must be enabled under event settings.
  • Discount: Defines a discount on the prices of the booked options in the form of an amount or a percentage for the respective registration and access settings. Example: Partners can book for free or at a reduced rate.

Access methods

Access methods can only be selected for authorisation groups without accounts.

  • Public: The event link can be opened by all users without authentication.
  • Private with password: A general, generic password is required to open the event. The password can be defined directly.
  • No access method activated: The event can only be opened and booked via the personal event link for each contact.

Deregistrations

The deregistration option allows contacts to decline the event invitation. Contacts who have deregistered will be removed from the contacts without confirmed bookings group and will not receive any further communications. This feature enables event managers to maintain a clear overview between outstanding invitations, acceptances, and deregistrations. For further information, please refer to our article on deregistrations.

File attachements

File attachments can be configured as a requirement for registration or as an attachment to the booking confirmation.

Restrict booking options to one authorisation group

If at least two authorisation groups have been created, individual booking options can be restricted to one or more authorisation groups. These options are then only visible and bookable for guests in this group. To do this, the option under ‘Advanced options’ can be restricted to one of the two authorisation groups.

Screenshot of restricting a booking option to an authorisation group


Frequently asked questions

  • How can I allow access for existing account types, such as external employees?
    In the authorisation group, access to accounts must be restricted, and the corresponding account type must be selected.
  • An account type or an account cannot (anymore) register. What could be the reason?
    If an event is fully booked or not available for individual users of an account type, the account typically lacks the permission to book the event. The lack of permission could be due to the following reasons:
    - Account groups are restricted to events with accounts, excluding the account,
    - only one option can be booked for the event, and the user has already booked an option (thereby not being eligible for others),
    - there are no authorisation groups for this account type,
    - the authorisation group has no registration and access settings,
    - options are excluded for this account type through additional booking rules or exclusions under authorisation groups, or
    - there is a capactity limit on booking options or the authorisation groups, which has been reached.
  • 'Access denied' is displayed. What could be the reason?
    The account used to access the event website lacks permission to open the website. This can also occur when the user is authorised for the event in the admin area (see article on access denied).
  • Why can't my authorisation group be deleted anymore?
    Authorisation groups cannot be removed if event bookings exist on them (including expired or canceled ones). As an alternative, you can disable authorisation groups by setting the end date in the past. The group will then expire and become unusable.
Download

By submitting, I agree that Oniva may process and store my data in accordance with the Oniva
Privacy Policy
.

Was this article helpful?

Thank you very much! Your feedback has been recorded.
Huch! Beim Absenden des Formulars ist etwas schief gelaufen.

Helpful information for event managers

Discover exciting articles about creating unforgettable events.

Didn't find an answer?

If you couldn't find the information you were looking for, our support team is happy to help. Create a ticket, and we will get back to you as soon as possible.
Time icon
Support hours
Monday to Friday, 08:00 to 17:00(excluding public holidays in the city of Zurich)

Contact support

Your contact details

Only requests from existing admins will be processed. Please enter your own contact details in the section below.

Request details

Please provide all information regarding your request. The more detailed your input, the faster we can process it.

Insert the link to your event or campaign – this helps us locate it more quickly.
Describe your issue as precisely as possible: What exactly do you need help with? Which function or area of the application is affected? If something didn’t work as expected, what happened and what steps did you take beforehand?

⚠️ Please do not provide
any personal data of guests
(e.g. names, e-mail addresses or phone numbers). Use
booking numbers
and
links
only to describe your request. Note: If you enter personal data, it will be transmitted to and
processed by our external support provider
 as part of handling your request.

By submitting, I agree that Oniva may process and store my data in accordance with the Oniva Privacy Policy.

Thank you for your support request! 🎉

What happens next?

A member of our support team will contact you as soon as possible to help you with your issue. In the meantime, visit our knowledge base and explore helpful articles and guides that may already provide the answers you need.

Refunds

Your contact details

Only requests from existing admins will be processed. Please enter your own contact details in the section below.

Request details

⚠️ Please do not provide
any personal data of guests
(e.g. names, e-mail addresses or phone numbers). Use
booking numbers
and
links
only to describe your request. Note: If you enter personal data, it will be transmitted to and
processed by our external support provider
as part of handling your request.

Fees

In addition to the usual processing fees, an extra fee of
CHF 2.50 / EUR 2.40 per transaction
 will be charged for refunds. This amount will be deducted from the total proceeds. For more information, please refer to the
Terms of Use
.

By submitting, I agree that Oniva may process and store my data in accordance with the Oniva Privacy Policy.

Thank you for your support request! 🎉

What happens next?

A member of our support team will contact you as soon as possible to help you with your issue. In the meantime, visit our knowledge base and explore helpful articles and guides that may already provide the answers you need.