Tenant settings

Tenant settings and workspaces

Using the tenant settings, admins with the appropriate permissions can manage the organisation account in Oniva. For all licence tiers—except the Enterprise licence with a dedicated instance—the tenant settings represent the highest configuration level and should only be assigned to selected admins.

At tenant level, both technical settings (such as a custom mail server or API integrations) and organisation-wide standards (e.g. logo, branding, privacy policy or forms) can be defined.

If multiple teams work with Oniva and each team has its own workspace, central elements such as branding, specific media or categories can be defined via the tenant settings. These elements are inherited by all workspaces but can be overridden individually. Workspaces that have already been customised are not affected by changes at platform level.

Settings

Tenant dashboard

The tenant dashboard provides tenant admins with a comprehensive overview of all activities within the application and allows them to see current licence usage at a glance.

Workspaces

Technically sensitive basic settings such as workspace keys, custom domains and access rights per workspace can be defined here—only tenant admins have permission to do so. Less critical configurations, such as default settings or branding, can be managed by workspace admins directly within their workspace. New workspaces can also be created here, provided the licence tier allows additional workspaces.

Campaign groups

If your organisation’s licence supports event-independent campaign groups, they can be created here. Most settings are defined directly within the campaign group by campaign admins. Contact the Oniva support team if your organisation is interested in campaign groups.

Organisations

In the Organisations section, you can record relevant organisations, which can then be used:

• Store in the event information. Organisations added in the event information are displayed on the event website and can be contacted by guests.
• As contact details for payment receipts in the event settings.

Organisations can also be created at workspace level.

Categories

Using overarching categories, events can be categorised independently of the workspace and displayed in the global event library. These categories are available in event libraries for navigation and filtering.

Venues

In the venues section, general locations can be stored. If you want to manage multiple locations, you can do so via the import function. This simplifies event configuration and ensures data quality.

Media

Here you can store general images and other media, such as logos, attachments and mood images. This simplifies the creation of events using standardised image files.

Notifications

Notifications can be configured here and are automatically sent when events are booked, cancelled or triggered by other actions. They can be customised at both workspace and event level. See the article on notifications.

Form templates

Form templates are predefined groups of form fields for registration forms & additional queries, deregistrations or accompanying persons. They can be used across all events so that standard fields do not need to be recreated for each event.

App tokens

App tokens must be created in order to use the Oniva API and serve as the authentication mechanism. See Getting started with the Oniva API.

Domains

Custom domains for events can be set up in Oniva. These domains can then be linked to a workspace. See How to: Set up a custom domain for your workspace.

API clients

API clients allow you to create access credentials for using the Oniva REST API, for example to connect CRM systems. In the API client, you define the permissions and generate the required access credentials.

Webhooks

Webhooks allow data packages to be automatically sent to connected external systems following specific actions, such as when a booking is created or a check-in is recorded. Webhooks with Oniva

Email sender addresses

Email sender addresses for sending emails such as event invitations and newsletters can be defined here. The address must be authorised for sending via the mail server configured in the settings, which is usually done through at least one SPF record for the relevant domain. See How To: Set up your own email sender address for sending event communications.

App connections

Under App connections, you can connect fully and natively integrated apps directly to Oniva. No development work is required for these connections. The following app connection is currently available:

• HubSpot integration

Platform export logs

The export logs provide a historical overview of all export activities on the platform. They show who exported which data and allow potential data leaks to be traced.

Delivery log

The delivery log displays all emails and SMS messages processed across all events and campaigns. Entries can be filtered by successful and failed deliveries. For failed deliveries, the reason for the error is also displayed. If delivery to a recipient fails, the relevant address is temporarily blocked from further deliveries. Email sender addresses may also be temporarily blocked if they have not yet been fully activated and cause errors when sending. This helps protect your sender reputation. Once the cause has been resolved, you can contact Oniva Support to have the temporary block lifted early. Depending on the reason for the block, it may also be lifted automatically after a certain period.

Account types

Account types allow you to create different profile types, for example for employees or members. You can create as many different account types as you need. If Single Sign-On (SSO) is enabled for your licence, you can configure SSO login for the account type. See Set up Single Sign-On (SSO).

Settings

Using the settings, both default settings and technical configurations for the tenant can be defined.

• Styling: Configure tenant-specific branding, including logo, colours and fonts for all events.
• Email template: Define the layout of all event notifications, such as booking confirmations.
• Email addresses: Defines the default sender for all platform emails. New sender addresses must be added by a tenant admin in the tenant settings.
• Email server: Defines the mail server used to send emails. Note that no emails will be sent if the configuration is incorrect. See How to: Set up your own email sender address for sending event communications
• Languages: Defines the languages available for this tenant. Users can create events and campaign groups in the defined languages.
• Account registration: Allows users in the portal to request an account, which must first be activated by an admin. See Edit accounts.
• Single Sign-On (SSO) (if enabled): Here you can configure SSO. The OpenID Connect (OIDC) and SAML 2.0 protocols are supported.
• Artificial intelligence (AI): Activates all AI-powered features. Please note that information entered in prompts is transmitted to the configured AI. Guest data is not shared. By default, Anthropic Claude Sonnet is used. See How to: Event texts with artificial intelligence (AI)
• Fallback forms: Fallback forms are used for events that require a form but do not have a standard form defined.