In Oniva, you can restrict event bookings to internal accounts. This ensures that only people with an Oniva account can access the registration – ideal for internal or confidential events.
For events that are not restricted to accounts, registration is either fully public via the event website or private via a personalised invitation link. In both cases, no further authentication is required: guests do not have a user account and do not need to log in.
For events restricted to accounts, participants must authenticate with their account to access the event registration. This significantly increases security for internal events. Instructions on creating and managing accounts are available in the corresponding article.
Registration for internal events occurs behind a login screen. If your organisation uses Single Sign-On (SSO), access can be further secured through this system.
Certain default configurations can be adjusted for internal events – for example, registration forms or privacy statements may not be required, as this information has already been provided during account creation. It is therefore recommended to create a dedicated workspace for internal events. For questions or support, contact support@oniva.events.
Setting up internal events in Oniva is generally the same as for public events. The main difference is in configuring authorisation groups, which determine who can participate under which conditions and how access to the event website is managed.
For events restricted to accounts, access is only possible via a registered user account.
When you limit event access to accounts, only registered users can sign up. This improves security and ensures that only internal participants, such as employees already registered in the system, can attend.
To restrict access even further, for example to specific departments, account groups can be used. Once an account group is created, it can be linked to the event’s authorisation group. Without a linked account group, all users of the corresponding account type can register.
Since authentication for internal authorisation groups is handled via the account and users are already known to the system, registration forms are not required for internal events. Only additional information, such as menu preferences or other details not stored in the account, needs to be collected via a form.
For events that include both internal and external participants, multiple authorisation groups can be created. In addition to the group for users with an account, a group for participants without an account can also be set up. Guests without an account can be imported via Excel and invited using their personalised link.
For events restricted to accounts, contacts are imported via account groups rather than Excel. Instructions for creating and managing account groups are available in the corresponding article.
When importing account groups, all data from the accounts is included, such as location, phone number, or profile picture. This ensures that no information needs to be maintained outside the accounts.
