Table of contents
-
1.
Mividas Meeting Portal
- 1.1. Installation and upgrades
- 1.2. Onboarding
- 1.3. Dashboard
- 1.4. Schedule meetings
- 1.5. Manage
- 1.6. Meeting rooms
- 1.7. Settings
- 1.8. Support
-
1.9.
Backend admin
- 1.9.1. End user scheduling account
- 1.9.2. Account delegate
- 1.9.3. Applications
- 1.9.4. Audit logs
- 1.9.5. Authentication and authorization
- 1.9.6. Access monitoring (AXES)
- 1.9.7. Booking portal API keys
- 1.9.8. Django OAuth toolkit
- 1.9.9. Text content
- 1.9.10. Meetings
- 1.9.11. Meeting types
- 1.9.12. Section
- 1.9.13. Secure meeting
- 1.9.14. Webhooks
1. Mividas Meeting Portal
Mividas Meeting Portal is our product to enable easy scheduling of video meetings directly via the end user’s web browser.
In this section, we assume that you are already working on a working installation of Mividas Meeting Portal, if not, please see the installation documentation before proceeding.
- For a quick overview and more information on what Mividas Meeting Portal is all about, please visit our homepage.
- Release notes for Mividas Meeting Portal can be found here.
- Release notes for Mividas Outlook add-in can be found here.
1.1. Installation and upgrades
The Mividas Meeting Portal installation and deployment process involves three main steps:
- Mividas Virtual Machine (VM): You first need to deploy the Mividas Installer virtual machine to your network. Ensure the VM is deployed and running. If not, refer to the VM deployment documentation.
- Mividas Installer Setup: Mividas Installer must be set up correctly and your license key activated. Refer to the Mividas Installer documentation if needed. After entering your license key, the Mividas Installer displays all product modules accessible with your license. The installation of Mividas Meeting Portal can proceed as a stand-alone installation or alongside other Mividas products.
- Install the Mividas Meeting Portal module: Continue below to install and deploy the Mividas Meeting Portal product module from the Mividas Installer.
Configuration
On the Mividas Installer start screen, click under Mividas Meeting Portal to start configuration before deployment. Choose Mividas Meeting Portal, which will open up the configuration fields below.
Main domain name for management web interface
| Option | Description |
|---|---|
| Configure Hostname/FQDN | Enter the hostname/FQDN for your installation. Must be a valid DNS record. |
| Select existing certificate | Choose one of your previously uploaded certificates to be used for the installation. |
| Opens up a window of the installer certificate management, where you can upload certificates and more. |
Dial info and presentation
| Option | Description |
|---|---|
| Site title for this installation | Set a titel on this installation, often same as organisation name. |
| H323 Gateway IP | If an external H323 gateway exists, this will be displayed next to SIP address as 123.123.123.123##99999 for room number 9999. |
User and login settings
| Option | Description |
|---|---|
| Example login username | Default domain to be appended to usernames to match video rooms in MCU. Usually, the user JID domain for Cisco Meeting Server and the email domain for Pexip Infinity. |
| Video default user-domain | The default domain must be appended to usernames to match video rooms in MCU. Usually, the user JID domain for Cisco Meeting Server and the email domain for Pexip Infinity. |
Note: User/Login related settings. See separate tabs for LDAP- and SAML-related settings
Locale settings
| Option | Description |
|---|---|
| Default language | Set the preferred language for the system. Mividas Meeting Portal uses the browser’s language setting if available; otherwise, it defaults to the language set here. |
| Timezone | Set the preferred time zone for the system. |
Outgoing Email (SMTP) Settings
Configure SMTP details for email notifications and invitations. If you configured this during the initial Installer setup, fields will be pre-filled but can be modified as needed.
| Option | Description |
|---|---|
| Display-name of sender | Enter the name to appear as the email sender. |
| Sender email-address | Enter the email address for outgoing messages (typically a no-reply address). |
| SMTP relay server hostname | Specify the SMTP server’s hostname. |
| TLS mode | Choose your preferred TLS mode. |
| Port | Specify the SMTP server port. |
| Username | Enter the SMTP username. |
| Password | Enter the SMTP password. If no password is needed, enter a hyphen. |
Optional settings
Book API settings
| Option | Description |
|---|---|
| External Mividas Core server domain name | If this Mividas Meeting Portal should be connected to a specific Mividas Core installation, please enter the Mividas Core server domain name here. In case of single server installation, leave this blank. |
| API key | API key to use from Mividas Meeting Portal to Mividas Core |
| Default customer shared key | Use this key to connect a scheduled meeting to a specific customer in Mividas Core |
| Disable dynamic customer shared key | Dynamic value from e.g. LDAP-attribute/ou will never be used |
OIDC (OpenID Connect) provider settings
| Option | Description |
|---|---|
| Enable | Enable OIDC provider support. |
| Select existing certificate | Select any already uploaded certificate to use with OIDC. |
| Click to open a new window where you Manage certificates. | |
| Remove optional setting | Check this box and click save to remove the settings. |
LDAP authentication settings
| Option | Description |
|---|---|
| Server | Enter the hostname of the current LDAP or AD server to use by default. Use “fqdn:389” to use a specific port. |
| Service account DN/username | Here you enter the path to the account to be used as a service account. The path is often unique to your particular organization. |
| Password | Enter the password for your LDAP or AD server. The field will get empty after pressing save. |
| Use LDAPS-connection | Connect to the server using SSL-based LDAPS-connection (port 636 by default). Make sure you have added any custom CA-certificates to make verification work. |
| Ignore TLS/SSL verification errors | Ignore TLS CA verification. TLS over regular LDAP port 389 may be used even if LDAPS is not enabled so unless you have added custom CA certificates for verification login may fail. |
| Disable referral chasing | Referrals occur when the queried server doesn’t have the requested information but points the client to another server that might. The client can then “chase” these referrals to retrieve the needed data. |
| Base dn | Specify where in the tree the initial search for results should begin. |
| User filter | Here you choose how users are filtered out and displayed. |
| End user group DN | Specify which group in the tree that will have access to the system and be able to use the product. |
| Admin group DN | Specify which group in the tree will have elevated admin rights in the system, which opens up additional settings and functions for the logged-in user. |
| Superuser group DN | Specify which group in the tree that will give members superuser status (highest). Use this with caution as these users will have full control over the system and should only be assigned to users with high technical knowledge. |
| Customer attribute | For dynamic multi-tenant Mividas Meeting Portal use. User LDAP-object attribute that contains customer shared keys, e.g. "customerAttribute". |
| Organisation membership attribute | Comma-separated list of user LDAP-object attributes that contains the users place in the organization (for fine organization level statistics). E.g. "topLevelOrganization,secondsLevelOrganization" |
| Username attribute | Attribute to use as ID/owner for scheduled meetings. Default SIP-domain will be added if none is included. Structure: [dap_fieldname[/search/replace]. Example: email/example.com/video.example.com |
| Enable local accounts | Allow logging in to users added to the local user database. |
External database server (beta)
You can choose to run your own database server, instead of the bundled one.
| Option | Description |
|---|---|
| Hostname | Enter the Hostname/FQDN or IP of the database server. |
| Username | Enter the database username. |
| Password | Enter the database password. If no password is needed, enter a hyphen. |
| Authentication type | Choose authentication type. |
| TLS mode | Choose what level of TLS is needed. |
| Create new user/database autmatically for each component | Allows for the creation of a new database for each installation. Mostly useful for service providers to keep customer data in separate databases. |
External Redis server (beta)
You can choose to run your own Redis server, instead of the bundled one.
| Option | Description |
|---|---|
| Protocol | Choose the protocol for the communication. |
| Hostname | Enter the Hostname/FQDN or IP of the Redis server. |
| Username | Enter the Redis username. |
| Password | Enter the Redis password. If no password is needed, enter a hyphen. |
| Use as background task broker | All background task messages will be handled by Redis instead of RabbitMQ. |
SAML SSO settings
| Option | Description |
|---|---|
| Entity URI to pass to SAML server | This will normally be the address to the product you are setting this up for, e.g. https://core.example.com
Ensure this name is exactly the same as configured in idp configuration as “Identifier” for the Relaying Party Trust! |
| URL to autoconfig metadata XML-file | The URL that is used for the product to automatically get the metadata XML-file.
Example for ADFS: https://<ADFS server FQDN>/FederationMetadata/2007-06/FederationMetadata.xml
Example for Keycloak: https://<Keycloak server FQDN>/auth/realms/<REALM>/protocol/saml/descriptor |
| Offline idP metadata XML | This is only needed if auto configuration is not used. Paste the iDP metadata XML in the text field. |
| Offline SP metadata XML | This is only needed if auto configuration is not used. Paste the SP metadata XML in the text field. |
| Select existing certificate | Choose one of you previously uploaded certificates to be used for encryption and signing of requests. |
| Sign SSL-certificate | If you have not yet uploaded a certificate that can be selected in the previous step, choose a Full chain PEM-formatted certificate bundle to upload. |
| Sign private key | Choose the private key of the above chosen certificate to upload. |
| Username claim | SAML Claim to use for creating the username. For Cisco Meeting Server installations, this should correspond to the username in CMS (jid).
Structure: <saml_claim_name>[/<search>/<replace>]. Example: email/example.org/video.example.org |
| Group/role/memberOf SAML claim | SAML Claim where you get the Group/role/memberOf to determine if the login is for a regular user, administrator or Superuser. E.g. OU=Groups,DC=example,DC=com |
| Group/role claim value required for regular users | Enter the path for the group/role that is required for regular users. E.g. CN=regular-users,OU=Groups,DC=example,DC=com |
| Group/role claim value required for admin-users | Enter the path for the group/role that is required for admin-users. E.g. CN=admin-users,OU=Groups,DC=example,DC=com |
| Group/role claim value required for superuser-users | Enter the path for the group/role that is required for superusers-users. E.g. CN=superusers-users,OU=Groups,DC=example,DC=com |
| Customer SAML claim | SAML Claim used in multi-tenant installations, to determin if the login is for a specific Customer |
| Enable single log out (SLO) | Single Logout (SLO) results in all user sessions being terminated simultaneously for the browser that initiated the logout. Closing all user sessions prevents unauthorized users from accessing resources at the Mividas products (SPs). |
| Enable local accounts | Allow logging in using username/password (using backend admin or API) with local accounts. |
| Enable debug-mode | Print more information including SAML Claims in logs, good for troubleshooting. |
SMS settings
| Option | Description |
|---|---|
| Provider | Choose your SMS provider. Currently available: Brevo, Twilio, GatewayAPI, MoSMS and Email. |
| Username | Enter the username of the account at your provider. |
| Password | Enter the password for the username above. If no password is needed, enter a hyphen. |
| Sender | The name of the sender. |
| Default country code | The default country code for your outgoing SMS. |
Save configuration
When you have filled in everything needed for your installation, or just want to save your progress, you need to save theese settings. Do so by clicking in the bottom left corner.
Deployment
Select Version and Deploy
After everything is configured it is time to deploy Mividas Meeting Portal. Choose the Mividas Meeting Portal version from the drop-down list
, then click
. A terminal window will display the installation progress. Once completed, reload the page to verify the correct version.
portal_epm: Running 15/18
portal_epm: Running 15/18
portal_epm: Running 16/18
portal_epm: Running 18/18
Finished
Reload
Update settings post-deployment
Modify Settings Post-Deployment
To update settings after deployment, select Mividas Meeting Portal from the start screen and click
. Adjust settings as needed, save changes, and redeploy by clicking
.
Following these steps, you can complete the Mividas Meeting Portal configuration and deployment while retaining the flexibility to update settings as requirements evolve.
Upgrade
Before upgrading
Before upgrading, we always recommend that you:
- Check your platform health and fix any current alerts affecting your installation.
- Check that you have disk space available.
- Take a snapshot of your installation in your hypervisor.
Upgrading
To upgrade, click
next to Mividas Meeting Portal from the start screen. Select the version you wish to upgrade to in the drop-down list
, and then click
.
1.2. Onboarding
When you log in to your Mividas Meeting Portal installation for the first time, the onboarding wizard will automatically launch to guide you through the essential configuration steps. This manual is intended for installations where the Mividas Meeting Portal is set up on a separate instance.
Prerequisites
Before beginning your Mividas Meeting Portal onboarding, confirm that:
- Mividas Installer installation: Ensure that your Mividas Installer is up and running. Refer to VM Deployment if needed.
- Mividas Meeting Portal installation: Ensure that your installation is up and running. If needed, refer to Mividas Meeting Portal Installation and Upgrade.
Onboarding wizard
When you visit the Mividas Meeting Portal for the first time, you are welcomed by the onboarding wizard.
1. Start

Click to proceed.
2. Choose password

Enter and confirm a new password for user “mividas_fallback”. Please document this password. After you have entered it twice, click to proceed.
3. Settings

| Option | Description |
|---|---|
| Custom logo | Upload a custom logo that will be shown in Mividas Meeting Portal. PNG or SVG. Will be resized to fit in 35px height. |
| Favicon | Upload a custom favicon that will be shown for Mividas Meeting Portal. Square, PNG or SVG. Recommended size 64×64 or 128×128. |
| Bright theme | Check this if you want to use a brighter theme within Mividas Meeting Portal. |
| Hide recording for Outlook addin | Hides the recording button within the Outlook addin. |
| URL user portal | URL to portal/support info about changing users’ passwords. |
| Support e-mail | Enter a support email address that will be visible for users. |
| Support phone | Enter a support phone number that will be visible for users. |
| Support ticket URL | Enter a URL that users can click on to open a support ticket. |
| Documentation URL | Enter a URL that users can click on to read documentation. |
| SIP address for test calls | Enter a SIP URI that users can use for test calls, e.g. [email protected] |
When you are done, click , or click Skip to enter this information later.
Connect Mividas Meeting Portal to Mividas Core
When the Mividas Core and Mividas Meeting Portal are not installed on the same instance, even if they are on the same virtual machine, you have to connect them to each other. Until this is fixed, Mividas Meeting Portal will display an error message.

1. Connect Mividas Meeting Portal to Mividas Core
In the Mividas Installer, where Mividas Meeting Portal is installed, click on Installation in the top menu. There, next to the Mividas Meeting Portal installation, click on followed by .
Under Optional Settings, click on Book API settings.
| Option | Description |
|---|---|
| External Mividas Core server domain name | Enter the FQDN of the Mividas Core installation you wish to connect to, e.g. core.example.com |
| API key | Copy and paste this API Key temporarily in a separate text document, or leave this tab open during configuration. You will need it in the next steps while configuring in the Mividas Core. |
| Default customer shared key | Copy and paste this Default customer shared key temporarily in a separate text document, or leave this tab open during configuration. You will need it in the next steps while configuring in the Mividas Core. |
| Disable dynamic customer shared key | Dynamic value from e.g. LDAP-attribute/ou will never be used |
Click . You will now have to deploy these changes, so click on on the screen you got taken to after yo saved.
If you copied the information temporarily to another document, you can close this tab/window. If not, after the deploy have finished, you can navigate back by clicking and then Book API settings.
2. Configure Mividas Core
Log in to Mividas Core, click Admin and then Backend admin. There, in the menu to the left, locate Scheduling portal API keys and click Add next to it.

| Option | Description |
|---|---|
| Name | Give your API key a name |
| Key | Paste the API key from Mividas Meeting Portal, that you either copied or left open in another tab/window. |
| Limit to customer | Select customer/customers that will be using this Mividas Meeting Portal. |
Click .
Then, locate Customers in the menu to the left and click on it.

On the page you just opened, click on the customer name in the list.
Locate the Customer Keys on the page. Paste the Default customer shared key from the Mividas Meeting Portal, that you either copied or left open in another tab/window.

After you have pasted the key, click in the bottom right corner.
3. Confirm the connection
You can now confirm that the connection works. Do so by logging in to Mividas Meeting Portal. The previous error message that was visible there should now be gone, and you should be able to book your first meeting.
FAQ
Here are some frequently asked questions (FAQs) to help you find the answers you’re looking for.
Please see SAML/SSO for Microsoft ADFS User guide for details.
1.3. Dashboard

After logging in, you will be presented with the Mividas Meeting Portal’s dashboard. This is where you schedule different types of meetings and view your upcoming, ongoing, and past meetings.
Left side menu
Scheduling block

The first part of this dashboard contains a welcome message, followed by a list of all currently available meeting types you have configured for scheduling. All of these are customizable, and the examples shown in this guide are only examples.
1 Only visible if a personal meeting room was created when your user was created in the video platform.
Meeting list

Below the scheduling block, you can find a list of all upcoming and previous meetings.
Your meetings

Delegated meetings

Here you can see all the meetings you have scheduled for other users.
Right side menu

The menu on the right side of this page contains information about ongoing and upcoming meetings, as well as displaying delegation invites. A test link can also be displayed to allow users to test their computers before a meeting.
User delegation

If someone has invited you to schedule meetings on their behalf, you will see a notification here. If there are no active invites, this section will be hidden.
Ongoing meetings

If you have any ongoing meetings, they will be displayed here, including the meeting time and name. Clicking the meeting name takes you to the meeting information page.
Secure invitations

If you have any active Secure meeting invitations, they will be visible here, including the meeting time, name, and who invited you.
Your meetings

Displays your meetings in a calendar view, along with a list of meetings for the selected day below it. A small blue dot indicates that you have a meeting scheduled that day. Clicking a meeting’s name in the list takes you to the meeting information page.
Test meeting

This displays you with a link you can use to test your computer’s video and audio. Clicking the link opens a pop-up with more information.

Whiteglove scheduling

When whiteglove functionality is configured, admin users (staff) and above will see the tabs shown in the picture above. The names of the tabs can, of course, be changed.
Personal
When this tab is active, everything will work as normal, as this is the default scheduling mode in the Mividas Meeting Portal. You handle your own meetings, and the people you have been delegated to handle.
Whiteglove
When this tab is active, you can schedule meetings for any user in your system. This includes all different meeting types presented on the scheduling dashboard.
Scheduling

Now, when you click any button to schedule a meeting, a new field will appear at the bottom of the form on the first page. Here you can search for any user in your system and schedule a meeting as them.
Meeting list

1.4. Schedule meetings

On the Mividas Meeting Portal’s dashboard, you will see an overview of all the available meeting types for booking. These may vary depending on your organization’s needs and configurations.
Schedule meetings
Video meeting

Click to continue or click to cancel.

Click to continue or click to skip this step.

Adds the system(s) to the meeting and proceeds or click to skip this step.
Webinar

Click to continue or click to cancel.

Click to continue or click to skip this step.

Click to continue or click to skip this step.

If you did not choose to enable registration, this step will be skipped.
Click to continue or click to skip this step.

Adds the system(s) to the meeting and proceeds or click to skip this step.
CIP meeting

Click to continue or click to cancel.
Care meeting

Click to continue or click to cancel.
Secure meeting

This guide for Secure meeting will not include SMS verification. To learn about that, see SMS meeting.
Click to continue or click to cancel.

Click to continue or click to skip this step.

Moderators, by email
Click to continue or click to skip this step.
Moderators, via another program
Click to move forward or click to skip this step.

Click to continue or click to skip this step.

Participants, by email
Click to continue or click to skip this step.
Participants, via another program
Click to move forward or click to skip this step.
Meeting with e-ID

This guide for meeting with e-ID will not include SMS verification. To learn about that, see SMS meeting.
Click to continue or click to cancel.

Click to continue or click to skip this step.

Moderators, by email
Click to continue or click to skip this step.
Moderators, via another program
Click to move forward or click to skip this step.

Click to continue or click to skip this step.

Participants, by email
Click to continue or click to skip this step.
Participants, via another program
Click to move forward or click to skip this step.
SMS meeting

This guide for SMS meeting will cover only verification via SMS.
Click to continue or click to cancel.

Click to continue or click to skip this step.

Click to continue or click to skip this step.

Click to continue or click to skip this step.

Click to continue or click to skip this step.
Existing meeting room

Click to continue or click to cancel.

Click to continue or click to skip this step.

Click to continue or click to skip this step.
External video meeting

Click to continue or click to cancel.

Click to continue or click to skip this step.
1.5. Manage

Manage another user’s calendar to schedule meetings on their behalf. For example, this feature can be used by a booking service or an assistant.
Search user

| Option | Description |
|---|---|
| Search for a user. | |
| Applies your search parameters. | |
| User | Displays the name of the user. |
| Displays the email of the user. | |
| Start to control Mividas Meeting Portal as the selected user. |
Search via meeting

| Option | Description |
|---|---|
| Search for a meeting by name. | |
| Select the start and end, date and time for the filter. | |
| Enter the address of a system to search for. | |
| Applies your search parameters. | |
| Upcoming/ongoing/previous meetings | Displays the name of the meeting together with its date and time. |
| Dial out | Displays if there are/were automatic dial-outs in the meeting. |
| User | Displays the name and email of the owner of the meeting. |
| Start to control Mividas Meeting Portal as the owner of the selected meeting. |
Control the other user

When you are controlling another user, a red frame will appear around the portal interface. At the top, it will display the user’s name. When you are done controlling, click at the top.
1.6. Meeting rooms

From this view, you can manage your static meeting rooms and create new ones, provided you are permitted to do so under company policy.
| Option | Description |
|---|---|
| Add a static meeting room | |
| Search for a meeting room in the list. |
Add a static meeting room
CMS

| Option | Description |
|---|---|
| Enter the name for your meeting room. | |
| Select any meeting room template to use for the meeting room (If configured). Selecting a meeting room template changes which settings can be made in the form; it uses the template’s settings instead of letting you set them in the form. | |
| Enter a PIN code for regular participants. | |
| Enter a PIN code for moderators. | |
![]() |
Select between pre-configured layouts for your meeting room. |
| Access to meeting room members only | Check this to see if the meeting room should only be available for members. |
| Mute microphone for new participants | Check this to automatically mute new participants’ microphones upon connecting. |
| Require manual admission of participants from lobby | Check this to enable manual admission to the meeting by a moderator. Regular participants will be placed in a lobby until they are manually admitted. |
Click to create the meeting room or click to cancel.
Pexip

| Option | Description |
|---|---|
![]() |
Enter the name for your meeting room. |
| Select any meeting room template to use for the meeting room (If configured). Selecting a meeting room template changes which settings can be made in the form; it uses the template’s settings instead of letting you set them there. | |
![]() |
Enter a PIN code for regular participants. |
![]() |
Enter a PIN code for moderators. |
![]() |
Select between pre-configured layouts for your meeting room. |
Click to create the meeting room or click to cancel.
Meeting room list

- Meeting rooms – Displays the meeting room name and, if available, the meeting type. Clicking on the name takes you to the meeting room dashboard.
- Room number – Displays the number to your meeting room.
- – Opens the “add meeting room” widget for you to edit the meeting.
- Allows you to delete the meeting room.
1.6.1. Meeting / Meeting room information

This page displays various settings for your meeting/meeting room. The options will vary depending on your settings, meeting platform, and the type of meeting/meeting room you have created.
Static meeting room information
Left side menu

1 Only available for CMS.
Details

Members

NOTE: Only available when using CMS for the meeting room.
Moderator instructions

Displays the instructions and connection details for moderators, based on your templates.
Instructions

Displays the instructions and connection details for guests, based on your templates.
Right side menu

Send invitation by e-mail
Meeting rooms
Scheduled meeting information
Left side menu

Connection

Moderators
This page displays all invited moderators for the meeting. It also allows you to add or remove moderators.

- ID – ID of this invite for troubleshooting purposes.
- E-mail – Displays the email address of the moderator.
- Time – The date and time of when the invitation was sent.
Participants
This page displays all invited participants for the meeting. It also allows you to add or remove participants.

- ID – ID of this invite for troubleshooting purposes.
- E-mail – Displays the email address of the participant.
- Time – The date and time of when the invitation was sent.
Moderator instructions

Displays the instructions and connection details for moderators, based on your templates.
Instructions

Displays the instructions and connection details for moderators, based on your templates.
Right side menu

Layout

If you wish to change the layout of this meeting, select it here and click .
Automatic dialout

Displays system added to the meeting.
Scheduled secure meeting information
Left side menu

Connection

Secure meetings do not display any connection details; that is all handled by Mividas Identify.
Log

Moderators

Participants

Agenda moderator

Agenda participants

Right side menu

Layout

If you wish to change the layout of this meeting, select it here and click .
Automatic dialout

Displays system added to the meeting.
1.7. Settings

Under you can modify the Mividas Meeting Portal’s functions and customize its branding, including the Outlook add-in.
Change password
Allows you to change the password of your currently logged-in account, or takes you to a page or site that explains how to do it.
Change time zone

| Option | Description |
|---|---|
| Timezone | Select your current time zone. |
| Date format | Choose how dates and times are displayed throughout the portal: Year first (2024-04-02 19:00), Day first, slash (02/04/2024 19:00), Day first, period (02.04.2024 19:00), or Month first, 12-hour (04/02/2024 07:00 PM). Leave unset to follow the installation default. |
| Click to change to your selected time zone and date format. | |
| Cancel the change. |
Delegations

Delegations allow you to grant other users permission to manage your video meetings on your behalf. This is useful when assistants, colleagues, or team members need to schedule, change, or cancel meetings for you. The delegation system uses an invitation-based workflow with full audit tracking.
| Option | Description |
|---|---|
| Click to view you history of delegation events. |
Historical delegations

| Option | Description |
|---|---|
| From user | Displays the user who sent the delegation request, including their full name and e-mail address. |
| For user | Displays the user who received the delegation request, including their full name and e-mail address. |
| Created | Displays the day, date, and time the delegation request was created. |
| Confirmed | Displays the day, date, and time the delegation request was confirmed. |
| Removed | Displays the day, date, and time the delegation request was removed. |
Incoming request
If you have an incoming request to manage someone’s meetings, this will be shown at the top of the page:

| Option | Description |
|---|---|
| User | Displays the name and e-mail address of the person who sent the request. |
| Time | Displays the date and time for the received request. |
| Approve the request. | |
| Remove the request, declining it. |
Active delegations

Users with access to manage your meetings
List all users who have access to manage your meetings, including their full names and e-mail addresses. Click to remove that user’s access.
Sent invitations
List all users to whom you have sent an invitation to manage your meetings, but they have not yet accepted the request, including their full names and e-mail addresses. Click to remove that user’s invitation.
Add access

| Option | Description |
|---|---|
| Enter the name of the user you wish to serach for. | |
| Click to search. | |
| User | Displays the full name and their ID in the video platform. |
| Displays the email of the user. | |
| Click to send an invitation to that user. |
Delegation invitations

| Option | Description |
|---|---|
| User | Displays the full name and e-mail of the user. |
| Time | Displays the date and time of the sent invitation. |
| Remove the invitation. |
View your access

| Option | Description |
|---|---|
| User | Displays the full name and e-mail of the user you have access to. |
| Remove your access to this person. |
Global settings

Invitation

| Option | Description |
|---|---|
| Enable advanced invitation | Enables advanced invitations in booking forms that allow adding multiple people at the same time. |
| Searching for users in the invitation 1 | Select how searching for users should work:
Disabled – User search is turned off. Users cannot search for other people when sending meeting invitations (default). |
- Requires activation of advanced invitations.
NOTE: Searching local users does not filter by customer organization (customer_id). All user accounts in the database can be found regardless of affiliation.
Automatic dialout

| Option | Description |
|---|---|
| Force automatic dialout validation | Forces validation on systems added for automatic dialout to ensure they are not already scheduled. |
| Enable automatic dialout search | Enable regular users to view and search for automatic dialouts in the meeting list. |
Demo mode

| Option | Description |
|---|---|
| Enable Demo/QA mode | Demo/QA mode that adds a clear banner around the Mividas Meeting Portal for easier version identification. |
| Demo banner text | Enter the text that you want to appear in the banner. |
| Demo banner color | Choose the color of the banner, in
hex format
. By default, the color is #FF0000. |
| Demo banner text color | Choose the color of the text within the banner, in
hex format
. By default, the color is #FFFFFF. |
Theme settings

Theme settings control the logo, favicon, and colors used across the portal for this section. To meet WCAG accessibility requirements, the interface needs sufficient color contrast between text and its background. If you have not defined your own color set, click to apply a WCAG-compliant color palette automatically before adjusting the individual colors below.
Custom logo

| Option | Description |
|---|---|
| Custom logo, choose file | Choose a file to upload as your custom favicon. PNG/SVG. Will be resized to fit 35px height |
| Custom favicon, choose file | Choose a file to upload as your custom favicon. PNG/SVG. Square icon, recommended size 64x64px or 128x128px |
| Bright interface | Changes the background of the right menu on the scheduling interface to a brighter background color. It also sets the top navigator background color to white and its text to black, unless you set a custom color for it below. |
Color top navigation

| Option | Description |
|---|---|
| Header background color | Choose the background color of the header, in
hex format
. By default, the color is #282828. |
| Header text color | Choose the color of the banner, in
hex format
. By default, the color is #FFFFFF. |
Button and icon color

| Option | Description |
|---|---|
| Button background color | Choose the background color of the buttons, in
hex format
. This also includes the Support field at the top right corner. By default, the color is #F18825. |
| Button text color | Choose the text color of the buttons, in
hex format
. This also includes the Support field at the top right corner By default, the color is #FFFFFF. |
| Link color | Choose the text color of the links, in
hex format
. By default, the color is #F18825. |
| Icon color | Choose the color of the icons, in
hex format
. By default, the color is #F128825. |
| Warning color | Color for error and warning indicators (buttons, badges, alerts, table radiicons, and form validation). The default color is red. |
| To meet WCAG requirements, the interface needs to have sufficient color contrast. If you don’t already have your own set of colors, you can click here to get a predefined profile. |
To save any changes made, click at the bottom.
Support settings

Support information

| Option | Description |
|---|---|
| Support e-mail | Enter the support e-mail that will be visible to users. |
| Support phone | Enter the support phone number that will be visible for users. |
| Support ticket URL | Enter a URL that users can click on to open a support ticket. |
| Documentation URL | Enter a URL that users can click on to read documentation. |
URL user portal

| Option | Description |
|---|---|
| URL user portal | Enter a URL to a page/site with information about changing users’ passwords. |
Download links

| Option | Description |
|---|---|
| Download link to MSI packages | Enter a URL to a MSI package for Windows users to download the video client (CMA). |
| Mac download link | Enter a URL to a file for Mac users to download the video client (CMA). |
| IOS download link | Enter a URL to a file for iOS users to download the video client (CMA). |
| Show download links | Check this box to show the download links on the right menu on the Schedule page. |
Test calls

| Option | Description |
|---|---|
| SIP address for test calls | Enter a SIP URI that users can use for test calls, e.g. [email protected] |
| WebRTC address for test calls | Enter a URL that users can use for test calls over WebRTC, e.g. https://video.example.com/testcall |
To save any changes made, click at the bottom.
Meeting room settings

Settings

| Option | Description |
|---|---|
| Allow scheduling meetings in the user’s existing meeting room directly from the meeting room detail view, provided the meeting type for booking in an existing meeting room is enabled. |
PINs

| Option | Description |
|---|---|
| Require user meeting room PIN | Check this box to require a PIN code when a meeting is scheduled. Note that this also applies when users create or edit a personal meeting room. |
| Require moderator PIN for user meeting room | Check this box to require a moderator PIN code when a meeting is scheduled. Note that this also applies when users create or edit a personal meeting room. |
To save any changes made, click at the bottom.
Outlook addin

Installation instructions

For Office 365, use the direct link for central deployment: Integrated Apps
Watch instructions from microsoft for options on installation. There is the possibility of both testing locally on a single computer and central deployment.
If your administrator enabled Mividas Outlook addin, you’ll be able to access your manifest file below.
Menu-based selection in Outlook
| Option | Description |
|---|---|
| manifest.xml | Click to download your manifest.xml-file based on the settings below: |
| Enable single booking | Enables booking of an ordinary video meeting. |
| Enable booking in existing meeting rooms | Enables booking in an existing meeting room(VMR). |
Predetermined choice
Use the respective link below to activate only one type of booking.
| Option | Description |
|---|---|
| manifest_simple.xml | Allows only booking of an ordinary video meeting. |
| manifest_static.xml | Allows only booking in an existing meeting room(VMR). |
To save any changes made, click at the bottom.
Settings

| Option | Description |
|---|---|
| Allow removing Outlook meetings for users through the portal | Allows users to remove meetings created in Outlook from Mividas Meeting Portal. |
| Type of login | Choose how the users should sign in:
– Via username and password in addin |
| Exchange/Core service account | This will automatically add a person/service account to the invite list to be able to filter meetings in the future |
| Hide video meeting title field | Hides the title/name field in the booking form. The meeting title will be taken from the Outlook calendar event subject instead. |
| Allow meeting locking | Shows the auto-lock option. When a meeting is locked, the moderator must manually admit each participant from the lobby. |
| Show moderator selection automatically | When enabled, the moderator selection panel is always expanded, prompting users to select which attendees should serve as moderators. When disabled, users must manually open the moderator selection. Enabled by default. |
| Automatically send moderator invitation to meeting owner | Automatically adds the meeting organizer as a moderator. |
| Default meeting type | Select the meeting type to use for meetings. |
| Secure meeting type | Select the meeting type to use for secure meetings. |
| Static meeting type | Select the meeting type to use for static meetings. |
| Activate smart events | Enable smart events to let the Outlook add-in try to update the meeting when changes occur in Outlook.
Note: Changing this parameter requires the addin to be redeployed. |
| Enable option to force encryption in Outlook | If this setting is enabled, a checkbox will appear in the Add-In, allowing users to enforce encryption for the meeting. For Cisco Meeting Server: If selected when scheduling a meeting in Outlook Add-In, the needsActivation parameter in the callLegProfile will be set to "require".If not selected, needsActivation will be set to "optional".For Pexip: If selected when scheduling a meeting in Outlook Add-In, the "Media encryption" will be set to "Required".If not selected, the "Media encryption" will be set to "Use global setting:" (Platform > Global Settings). |
To save any changes made, click at the bottom.
Branding

| Option | Description |
|---|---|
| Outlook icon title | The label shown on the add-in button in Outlook. |
| Heading easy booking | The label on the Simple booking button. |
| Heading for booking in static meeting rooms | The label on the Static room booking button. |
| Header to display connection information | The label shown to attendees (non-organizers) for viewing connection information. |
| Override location (Django template) | This lets you customize the Location field in the calendar invitation (iCal) that is sent to participants. By default, the location is automatically set to the SIP dial-in address and meeting join URL. With this setting, you can replace it with a custom value.
The field accepts Django template syntax, meaning you can include dynamic meeting data using How it works: Example variables: Example result: |
| Upload icons | Upload an icon for use in Outlook. The format should be .png and it should be uploaded in 5 different sizes (16x16px, 32x32px, 64x64px, 80x80px, 128x128px). |
To save any changes made, click at the bottom.
Backend admin
Takes you to the backend admin page.
1.8. Support

To reach the support information available for users, click on in the top right corner.
To see what information you can put here and edit those settings, check Support settings.
1.9. Backend admin

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
The Backend admin is the superuser-only administration interface, accessed at /admin/. It exposes low-level configuration that may not be surfaced in the standard product interface.
- End user scheduling account
- Account delegate
- Applications
- Audit logs
- Authentication and authorization
- AXES
- Booking portal API keys
- Django OAuth toolkit
- Text content
- Meetings
- Meeting types
- Section
- Secure meeting
- Webhooks
1.9.1. End user scheduling account

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
An end user scheduling account is automatically created the first time a user signs in to the Mividas Meeting Portal. This works the same for LDAP, SAML, and local users. The account holds the user’s scheduling identity: login name, display name, e-mail address, and personal preferences. Every meeting scheduled in the portal is connected to the organizer’s account.
Note: End user scheduling accounts are not the same as backend users. Sign-in, admin levels, and permissions are managed under AUTHENTICATION AND AUTHORIZATION › Users. Accounts can’t be manually added in the backend admin.
List view

| Column | Description |
|---|---|
| End user scheduling account | The user’s display name, or the login name if no display name is available. |
| User login | The login name that identifies the account, in e-mail format. |
| E-mail address | The e-mail address used for invitations and notifications. |
| TS last login | When the user last signed in. |
| TS first login | When the user first signed in, which is when the account was created. |
Edit an account

Click an account to open it. Most fields are read-only. They’re updated when the user signs in or changes their settings in the portal. Only User login and Ldap dn can be changed.
| Field | Description |
|---|---|
| User login | The login name of the account in e-mail format, e.g. [email protected]. |
| Ldap dn | The distinguished name of the user in the LDAP directory, e.g. CN=Sven Svensson,OU=Users,DC=example,DC=com. Must be a valid LDAP DN. Empty for users that are not in LDAP. |
| ID | Internal ID of the account (read-only). |
| User name | The user’s display name (read-only). |
| E-mail address | The user’s e-mail address (read-only). |
| Ts first login | When the account was created (read-only). |
| Ts last login | When the user last signed in (read-only). |
| Ts email verified | When the e-mail address was verified, for example, by a trusted identity provider. If several accounts have the same e-mail address, an account with a verified address is preferred (read-only). |
| Language | The interface language the user has selected (read-only). |
| Timezone | The personal time zone the user has selected for times and dates in the portal. If empty, the installation’s default time zone is used (read-only). |
Delete accounts
Warning: Deleting an account permanently removes all meetings, invitations, and delegations associated with it from the Mividas Meeting Portal. Meetings are not canceled in Mividas Core, and no cancellation notifications are sent to participants. If you need to, cancel the meetings in the portal first. A new, empty account is created if the user signs in again.
To delete an account, open it and click Delete. To delete several at once, select them in the list and use the Delete selected end user scheduling accounts action.
1.9.2. Account delegate

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
These pages show who may schedule and see meetings on someone else’s behalf. Together, they cover the whole lifecycle: invitations that have been sent but not yet answered, and those that have been accepted and are currently in effect. Revoked delegations are retained for a set period, so the full history of who once had access is preserved.
1.9.2.1. Delegation requests

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
Lists invitations in which one user has asked to manage another user’s meetings, and the other user has not yet responded. Shows who asked, who was asked, the status, and when it was created, confirmed, or withdrawn. This is the page to check when a user says a delegation invitation never arrived or was never accepted.
This page is read-only.
1.9.2.2. Delegations

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
Lists the delegations that were accepted, who may currently schedule and see meetings on whose behalf. Revoking a delegation in the product does not erase the row; it records a removal time, so this page keeps the full history of who once had access.
This page is read-only.
1.9.3. Applications

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
The applications list each external system allowed to call the Mividas Meeting Portal’s API, with its owner, client type, optional allowed IP addresses, and the permission groups that cap what its tokens can do.
| Option | Description |
|---|---|
| Search | Search by name or client ID. |
| Add application + | Add a new OAuth application. |
List view

| Column | Description |
|---|---|
| Name | The descriptive name of the application. |
| Client id | The OAuth client ID. |
| Client type | Confidential or Public. |
| Authorization grant type | The OAuth flow the application uses. |
| User | The owner of the application. |
| Scope groups | The scope selected for this application. |
Add or edit an application

When you add an application, Client id and Client secret are generated automatically. After you click Save, a message appears showing the client secret once. Copy it right away. When Hash client secret is enabled, the secret can’t be shown again.
| Field | Description |
|---|---|
| Client id | The OAuth client ID. It’s generated automatically, but you can replace it. |
| User | The owner of the application. Enter the user’s ID, or click the magnifying glass to look up a user. The owner limits which scopes the application’s tokens can get, see Which scopes can be granted below. Required for the Client credentials grant type. |
| Redirect uris | Allowed URIs list, space separated. Required for the Authorization code and Implicit grant types. |
| Post logout redirect uris | Allowed Post Logout URIs list, space separated. |
| Client type | Choose the OAuth client type.
Confidential – Applications running on protected servers, where unauthorized users can’t access the configuration or source code. These applications can keep the client’s secret safe. |
| Authorization grant type | Choose the OAuth authorization grant type.
Authorization code – A secure, redirect-based flow. The application exchanges a temporary authorization code for an access token. PKCE is required. Use this for applications that act on behalf of a signed-in user. |
| Client secret | Hashed on Save. Copy it now if this is a new secret. To change the secret, enter a new value and click Save. Copy the new value before you save. |
| Hash client secret | When enabled (default), the client secret is stored hashed and can’t be shown again after it’s saved. |
| Name | A descriptive name used to identify the application. |
| Skip authorization | When enabled, users aren’t asked to approve the application in the Authorization code flow. Only use this for trusted applications in your own organization. |
| Algorithm | The signing algorithm for OpenID Connect ID tokens: No OIDC support, RSA with SHA-2 256 or HMAC with SHA-2 256. Keep No OIDC support unless OpenID Connect has been enabled for your installation. |
| Allowed origins | Allowed origins list to enable CORS, space separated. Only needed for browser-based applications that call the OAuth endpoints directly. |
| Restrict to IP addresses | A list of approved IP addresses/networks. Separate the entries with spaces or commas, e.g. 172.16.1.10 10.10.10.0/24. API requests with the application’s tokens are denied from all other addresses. Leave empty to allow all addresses. |
Which scopes can be granted?
A token’s scopes are limited by the user for whom it is issued. For Authorization code and Resource owner password-based, this is the signed-in user. For Client credentials, the application owner (User) is the one. The available scopes are described under AUTHENTICATION AND AUTHORIZATION › Groups.
- By default, the user’s admin level decides. All users can get
web,api:read,api:writeandbook_api:write. Users with Staff status can also getadmin:read, and users with Superuser status can also getadmin:write. - If the application owner is a member of a group with the permission Use group scopes for API permissions (beta), the application’s tokens are limited to the scopes granted to the owner’s groups. If you change the group scopes, tokens that are already issued are also affected from their next request.
- The scopes
book_admin_api:read,book_admin_api:writeandsecure_meeting_api:writeare only available through group scopes. - A Client credentials application must have an owner. Without an owner, no tokens can be issued.
Delete an application
Deleting an application also deletes all access tokens and refresh tokens issued for it. Integrations that use the application stop working immediately.
1.9.4. Audit logs

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
A read-only log of sign-ins, sign-outs, and changes made in Mividas Meeting Portal. This includes changes made in the web interface, via the Outlook add-in, the APIs, and the backend admin.
Entries are created automatically. They can’t be added, changed, or deleted.
What is logged
- Sign-ins, sign-outs, and failed sign-ins.
- All requests that create, change, or delete data, for example, scheduling, rescheduling, or canceling a meeting, sending invitations, or saving a record in the backend admin.
- When a user starts managing meetings on behalf of another user.
Ordinary page views and other read-only requests are generally not logged. Passwords and other sensitive values in the submitted data are redacted before they’re stored.
List view
| Column | Description |
|---|---|
| Ts created | When the event happened. |
| Username | The user who made the request. |
| Delegate username | The user who acted on behalf of Username, for example, through a delegation. Empty if the user acted on their own. |
| Meeting id | The ID of the meeting the event is related to, if any. |
| Scope | The part of the system to which the request was made.
auth – Sign-in and sign-out, including SAML sign-in. |
| Action | What was done, a few examples:
login – A user signed in. |
View an entry

Click the date and time of an entry to see all details.

| Field | Description |
|---|---|
| Ts created | When the event happened. |
| Ip | The IP address of the client. |
| Scope | The part of the system to which the request was made. |
| Action | What was done. |
| Type | For API requests: the type of object that was handled, e.g. meeting. |
| Username | The user who made the request. |
| Delegate username | The user who acted on behalf of Username. |
| Backend username | The backend user of the session, or - if there was none. |
| Path | The URL path of the request. |
| Account | The end user scheduling account the request was made as. |
| Delegate | The end user scheduling account that acted on behalf of Account. |
| Meeting | The meeting the event is related to. |
| Content indented | A summary of the event, e.g. POST portal.example.com/book/ (status 302) or a sign-in message. |
| Extra indented | More details in JSON format. This includes the submitted data (with sensitive values redacted), the affected object, and request headers such as User-Agent and X-Forwarded-For, and request IDs for troubleshooting. |
1.9.5. Authentication and authorization

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the standard Meeting Portal interface when the same setting is available there.
Manage user accounts and permission groups that grant web interface access and granular API rights.
This section contains the following settings pages:
1.9.5.1. Groups

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Manage groups of backend users. In the Mividas Meeting Portal, groups are used for two things:
- Group scopes (beta) – limit what the members of a group are allowed to do in the portal and in the APIs.
- Group mappings – add users to a group automatically when they sign in, based on their LDAP groups or SAML claims.
| Option | Description |
|---|---|
| Search | Search by group name. |
| Add group + | Add a new group. |
Add or edit a group
| Field | Description |
|---|---|
| Name | Required. The name of the group. |
| Permissions | Only used in backend admin. The only available permission is Use group scopes for API permissions (beta). When a user has this permission, either directly or through a group, scoped permissions are enabled for the user. |
Group scopes

Group scopes are a public preview (beta) of scoped user permissions.
By default, a user’s admin level decides what they can do. All users can use the web interface and read and write their own data. Users with Staff status also get read access to admin settings, and users with Superuser status also get write access.
To limit a user, turn on scoped permissions for them. Then the user’s permissions are limited to the scopes granted to all of their groups together.
To turn on scoped permissions for a user:
- Add the scopes the users need to one or more groups.
- Grant the Use group scopes for API permissions (beta) permission to one of the user groups.
- Add the users to the groups.
Important: Please verify your use case before you give users restricted access. Permissions are checked in the backend only. All elements in the user interface remain visible, but will show a permission denied message when used.
| Option | Description |
|---|---|
| Scope | Select a scope to grant to the members of the group. Each scope can only be added once per group. See the list of scopes below.
|
| Delete | If not yet saved: click the delete icon (x) to remove the row. If already saved: check the box and click Save to remove the row. |
| Add another Group scope | Adds another row for another scope. |
Group scopes also limit the tokens of OAuth applications owned by users with scoped permissions, see API_KEY › Applications.
Group mappings

Group mappings automatically add users to the group when they sign in via LDAP or SAML.
| Option | Description |
|---|---|
| Mapping type | SAML or LDAP. The sign-in method the mapping applies to. |
| Value | Claim/attribute value associated with permission in Installer. For LDAP, enter the DN or name of an LDAP group or organizational unit the user is a member of. For SAML, enter a value of the group or role claim. Use * to match all users who sign in with this method. |
| Clear missing | When checked (default), users who no longer match the value are removed from the group at their next sign-in. When left unchecked, users remain in the group until they’re manually removed. |
| Delete | If not yet saved: click the delete icon (x) to remove the row. If already saved: check the box and click Save to remove the row. |
| Add another Group mapping | Adds another row for another mapping. |
Note: Group mappings are applied every time a user signs in. Manual changes to the groups of an LDAP or SAML user can be overwritten by the group mappings at the next sign-in.
1.9.5.2. Users

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Manage local users and users created through external identity providers (LDAP/SAML). The user’s admin level decides what the user is allowed to do in the Mividas Meeting Portal and in the backend admin.
Note: Users are created automatically the first time someone signs in with LDAP or SAML. The user’s scheduling profile and meetings are kept in a separate end-user scheduling account, see ACCOUNT › End user scheduling accounts.
| Option | Description |
|---|---|
| Search | Search by username, first name, last name, or e-mail address. |
| Add user + | Add a local user. |
List view

| Option | Description |
|---|---|
| Username | The user’s login name. |
| Email address | The user’s e-mail address. |
| First name | The user’s first name. |
| Last name | The user’s last name. |
| Staff status | Shows if the user has admin level. |
Add a local user
When you add a local user, start by entering a Username, a Password and a Password confirmation. Then click Save and continue editing at the bottom of the page to stay on the page. After the user is added, more options become available, see Edit a user.
Edit a user

| Option | Description |
|---|---|
| Username | Required. 150 characters or fewer. Letters, digits, and @.+-_ only. |
| Password | Raw passwords are not stored, so there is no way to see the user’s password. To set a new password for a local user, use the link to the password form. |
| First name | The user’s first name. |
| Last name | The user’s last name. |
| Email address | The user’s e-mail address. |
| Active | Designates whether this user should be treated as active. Inactive users can’t sign in. Unselect this instead of deleting the user. |
| Staff status | The admin level. Users with Staff status have read access to admin settings and can view admin-only sections in the portal (white-glove). When delegation is licensed, they can also manage meetings for all users. Staff status alone doesn’t give access to the settings pages in the backend admin. |
| Superuser status | Gives the user access to all functions and settings, including all backend admin pages. |
| Groups | The groups the user belongs to. Groups control scoped permissions (beta), see Groups. |
| Last login | When the user last signed in. |
| Date joined | When the user was created. |
Note: For LDAP and SAML users, Active, Staff status, Superuser status and group memberships can be updated automatically at every sign-in. This depends on the permission and group mappings configured in Mividas Installer and under Groups. Manual changes to these fields can then be overwritten the next time the user signs in.
Generate OAuth2 tokens

Superusers can create an OAuth access token for a user directly, for example, to test an API integration. Click Generate OAuth2 Tokens at the bottom of the user’s page.

| Field | Description |
|---|---|
| Application | Choose the OAuth application for token generation. Applications are configured under API_KEY › Applications. |
| Scopes | Select the scopes to grant to the generated tokens. Only the scopes this user can get are listed. |
Click Generate Tokens. The access token and the refresh token are shown one time in a message, in the format <access token> / <refresh token>. The access token is valid for one hour. Token generation is recorded in the audit log, and the tokens are listed under DJANGO OAUTH TOOLKIT › Access tokens and Refresh tokens.
Delete a user
To delete a user, open the user and click Delete, or select users in the list and use the Delete selected users action.
Warning: Deleting a user also deletes all OAuth applications owned by the user, and all tokens issued for the user and these applications. The user’s end-user scheduling account and meetings are not deleted. To block a user, uncheck Active instead.
1.9.6. Access monitoring (AXES)

Read-only login-security logs from the Axes brute-force-protection module.
This section contains the following settings pages:
1.9.6.1. Access attempts
A log of failed sign-in attempts, recorded by the Axes brute-force protection module. It shows the username, IP address, user agent, and time. Entries are created automatically and can’t be added here.
How the brute-force protection works
All sign-ins that require a username and password are protected for both LDAP and local users. This covers the Meeting Portal and the backend admin. Failed attempts are counted per IP address. After 10 failed attempts, sign-in from that IP address is locked for 5 minutes. The lockout ends automatically after this time.
To unlock an IP address immediately, delete its access attempt entry.
List view
| Column | Description |
|---|---|
| Attempt Time | When the latest failed attempt was made. |
| IP Address | The IP address from which the attempts came. |
| User Agent | The browser or client that was used. |
| Username | The username that was entered. |
| Path | The page or API path where the attempt was made. |
| Failed Logins | The number of failed attempts counted in this entry. |
View an access attempt
Click an entry to see all details. All fields are read-only.
| Field | Description |
|---|---|
| Username | The username that was entered. |
| Path | The page or API path where the attempt was made. |
| Failed Logins | The number of failed attempts. |
| GET Data | The query parameters of the request. |
| POST Data | The submitted form data. Passwords are masked. |
| User Agent | The browser or client that was used. |
| IP Address | The IP address from which the attempt came. |
| HTTP Accept | The Accept header of the request. |
Delete access attempts
To reset the counter and remove a lockout, open the entry and click Delete. To delete multiple entries, select them in the list and use the Delete selected access attempts action.
1.9.6.2. Access failures
A read-only log of individual failed sign-in attempts, recorded by the Axes brute-force protection module. Entries are created automatically and can’t be added here.
List view
| Column | Description |
|---|---|
| Attempt Time | When the failed attempt was made. |
| IP Address | The IP address from which the attempt came. |
| Username | The username that was entered. |
| User Agent | The browser or client that was used. |
| Path | The page or API path where the attempt was made. |
| Access lock out | Indicates whether the attempt resulted in a lockout. |
View an access failure
Click an entry to see all details. All fields are read-only.
| Field | Description |
|---|---|
| Username | The username that was entered. |
| Path | The page or API path where the attempt was made. |
| User Agent | The browser or client that was used. |
| IP Address | The IP address from which the attempt came. |
| HTTP Accept | The Accept header of the request. |
Deleting entries from this log doesn’t remove a lockout. To unlock an IP address, delete its entry under AXES › Access attempts.
1.9.7. Booking portal API keys

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Manage the API keys for the Mividas Meeting Portal admin scheduling API. Integrations such as a calendar or scheduling system use this API to schedule and manage meetings for any user.
| Option | Description |
|---|---|
| Add booking portal API key + | Add a new API key. |
Use an API key
Send the key in the X-Mividas-Token HTTP header with every request to the admin scheduling API under https://<portal-fqdn>/api/admin/.
X-Mividas-Token: <api key>
An API key gives full access to the admin scheduling API. Store it securely and only give it to trusted systems. As an alternative to API keys, you can use an OAuth application with the scopes book_admin_api:read or book_admin_api:write, see API_KEY › Applications.
List view

| Column | Description |
|---|---|
| Name | The descriptive name of the key. |
| Key value | A masked preview of the key, showing the first five and the last three characters. |
| Enabled | Shows if the key is enabled. |
Add or edit an API key

| Field | Description |
|---|---|
| Name | A descriptive name, e.g. the name of the system that uses the key. |
| Update key | Leave empty to generate a random key when you add a new key, or to keep the current key when you edit one. Enter a value to set your own key. To reset the value, enter a hyphen (-). A key that has been reset no longer works. |
| Created | When the key was created (read-only). |
| Last used | When the key was last used in an API request (read-only). |
| Enabled | Shows if the key is enabled (read-only). |
| Key value | A masked preview of the key (read-only). |
After you save a new key, a message displays the complete key once. Copy it right away, because the page only shows a masked preview afterward. The key is stored encrypted.
Revoke an API key
To stop a key from working, open it and enter (-) in Update key, then click Save. You can also delete the key. To delete multiple keys, select them in the list and use the “Delete selected booking portal API keys” action. Systems that use a revoked or deleted key can’t access the API anymore.
1.9.8. Django OAuth toolkit

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
View and revoke the OAuth 2.0 tokens issued to the applications under API_KEY › Applications. Tokens are created automatically when an application signs in via the OAuth endpoints or when Generate OAuth2 Tokens is selected on a user’s page.
This section contains the following settings pages:
1.9.8.1. Access tokens

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
View, and revoke OAuth 2.0 access tokens.
Note: Access tokens are shown in clear text. Anyone who can open this page can use the tokens to access the API as the token’s user. Only give superuser access to people who need it.
Tokens are normally created by the OAuth token endpoint (https://<portal-fqdn>/oauth/token/). To create a token manually, use Generate OAuth2 Tokens on the user’s page under AUTHENTICATION AND AUTHORIZATION › Users, instead of adding it here.
List view

| Column | Description |
|---|---|
| Token | The access token. |
| User | The user the token was issued for. |
| Application | The OAuth application the token belongs to. |
| Expires | When the token expires. Expired tokens can’t be used. |
Add or edit an access token

| Field | Description |
|---|---|
| User | The user the token gives access to. Enter the user’s ID, or click the magnifying glass to look up a user. |
| Source refresh token | The refresh token that was used to create this access token, if any. |
| Token | Required. The access token value. |
| Token checksum | A checksum of the token, used for fast lookups. It’s recalculated automatically from Token when you save. |
| Id token | The OpenID Connect ID token issued together with the access token, if any. |
| Application | The OAuth application the token belongs to. |
| Expires | Required. When the token expires. |
| Scope | The scopes granted to the token, space separated, e.g. api:read api:write. |
Note: Changing Scope changes what the token can be used for, from its next request. If the application’s owner has scoped permissions, the token is still limited to the owner’s group scopes. See Which scopes can be granted under API_KEY › Applications.
Revoke access tokens
To revoke a token immediately, open it and click Delete. To revoke multiple tokens, select them in the list and use the Delete selected access tokens action. Clients that use a deleted token must obtain a new one. If they still have a valid refresh token, they can use it to get a new access token. To stop that, also delete the refresh token under DJANGO OAUTH TOOLKIT › Refresh tokens.
1.9.8.2. Refresh tokens

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
View and revoke the OAuth 2.0 refresh tokens that have been issued for the applications under API_KEY › Applications. A client uses a refresh token to get a new access token when the old one has expired, without signing in again.
Note: Refresh tokens are shown in clear text. Anyone who can open this page can use the tokens to get new access tokens. Only give superuser access to people who need it.
Refresh tokens are created together with access tokens by the OAuth token endpoint or by Generate OAuth2 Tokens on a user’s page. Don’t add refresh tokens manually.
List view

| Column | Description |
|---|---|
| Token | The refresh token. |
| User | The user the token was issued for. |
| Application | The OAuth application the token belongs to. |
Edit a refresh token

| Field | Description |
|---|---|
| User | Required. The user for whom the token is issued. Enter the user’s ID, or click the magnifying glass to look up a user. |
| Token | Required. The refresh token value. |
| Application | Required. The OAuth application the token belongs to. |
| Access token | The access token that is issued along with this refresh token. |
| Revoked | When the refresh token was revoked. A revoked refresh token can’t be used to get new access tokens. The form requires a value here, so saving the form always revokes the token. |
Revoke refresh tokens
To revoke a refresh token, do one of the following:
- Open the token, set Revoked to the current date and time, and click Save. The token is kept but can’t be used anymore.
- Open the token and click Delete, or select tokens in the list and use the Delete selected refresh tokens action. The tokens are removed permanently.
Revoking a refresh token doesn’t affect an access token that has already been issued. Delete the access token under DJANGO OAUTH TOOLKIT › Access tokens to revoke it immediately.
1.9.9. Text content

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Edit the texts shown on pages in the Mividas Meeting Portal and used in emails and SMS messages.
List view

Edit a text

Select a language tab at the top of the form to edit the text in that language. If a text hasn’t been translated into the user’s language, it is shown in the installation’s default language.
| Field | Description |
|---|---|
| System id | Required. A unique name used for reference in the templates. Don’t change the system ID of an existing text, because the portal looks up the text by this name. |
| Subject | An optional header for this content. On portal pages, it’s shown as a heading. In e-mails, it’s used as the subject. |
| Content | The text itself. Texts on portal pages are shown as plain text, and line breaks are kept. E-mail texts marked as HTML in the tables below can contain HTML. |
Note: Don’t delete texts that the Meeting Portal uses. A deleted text is automatically recreated when needed, but it shows its system ID instead of the text. To hide an optional text, clear its content instead.
Texts on portal pages
| System id | Where it’s used |
|---|---|
login.intro |
Introduction on the sign-in page. |
start.intro |
Heading and welcome text on the start page. |
start.test_meeting_description |
Text in the test meeting box on the start page. |
start.test_meeting_question |
Text next to the Test meeting link on the start page. |
start.user_connection_details_label |
Label of the button that shows the user’s personal connection details on the start page. The button is only shown to users who have personal connection details. Clear the content to hide the button. |
testcall.intro |
Instructions on the test meeting page. |
cospaces.intro |
Heading and introduction on the meeting rooms page. |
recording.intro |
Heading and introduction on the recordings page. |
webinar.signup |
Heading and introduction on the page where participants register for a webinar. |
support.user_guide_label |
Label of the user guide button in the support menu. The link is set in the theme settings. |
support.service_ticket_label |
Label of the service ticket button in the support menu. The link is set in the theme settings. |
Texts in e-mail and SMS messages
You can use placeholders, written within curly brackets. They’re replaced with the actual values when the message is sent. Unless stated otherwise, you can also use {system_title} (the name of the portal) and {base_url} (the address of the portal).
| System id | Where it’s used | Format and Placeholders |
|---|---|---|
invite_email.content |
The layout around the body of all meeting invitation e-mails. | HTML. {title} – the invitation title, {invite_html} – the invitation body. |
delegate.delegate_request_email |
E-mail to a user who has been invited to manage meetings for someone else. If the content is empty, no email is sent. | HTML. {user_name} and {user_email} – the user who sent the request, {url} – link to the Delegations page. |
webinar_signup_invite_message |
Default invitation message for webinars that require registration. | HTML. {title}, {date_start}, {time_start}, {date_stop}, {time_stop}, {room_number}, {password}, {dialstring}, {web_url} – the address of the registration page, {web_link} – a clickable link to the registration page. Only these placeholders can be used, and other curly brackets are not allowed in this text. |
webinar.participant_registered_email |
E-mail to the organizer when a participant registers for a webinar. | HTML. {title}, {url} – link to the meeting, {participant_name}, {participant_company}, {participant_email}. {base_url} can’t be used in this text. |
secure_meeting.email |
Default invitation e-mail for secure meeting participants, if the organizer doesn’t write their own message. Also used as a fallback for the other secure meeting e-mail texts. | HTML. {url} – the participant’s personal sign-in link. In the subject: {type} – the meeting type. |
secure_meeting.email_moderator |
The same, for moderators. Falls back to secure_meeting.email. |
HTML. Same as above. |
secure_meeting.email_sms |
Default invitation e-mail for participants who sign in with an SMS code. | HTML. Same as above. |
secure_meeting.email_sms_moderator |
The same, for moderators. | HTML. Same as above. |
secure_meeting.email_eid |
Optional. Default invitation e-mail for participants who sign in with methods other than SMS, e.g., eID. Add this text if you want a different text than secure_meeting.email. |
HTML. Same as above. |
secure_meeting.email_eid_moderator |
Optional. The same, for moderators. | HTML. Same as above. |
secure_meeting.sms |
Default invitation SMS for secure meetings. | Plain text. {url} – the personal sign-in link, {code} – the verification code. |
secure_meeting.sms_moderator |
The same, for moderators. | Plain text. Same as above. |
secure_meeting.sms_eid |
Default invitation SMS for sign-in methods that verify the person’s identity (sso:validate and eid:validate). |
Plain text. {url} – the personal sign-in link. |
secure_meeting.sms_eid_moderator |
The same, for moderators. | Plain text. Same as above. |
secure_meeting.sms_resend |
SMS with a new verification code, sent when the participant’s code has expired. See SECURE_MEETING › Secure meetings settings. | Plain text. {code} – the new verification code. |
secure_meeting.notify_open |
E-mail to the organizer when a participant opens their secure meeting link. Only sent for meeting types with the advanced setting send_open_meeting_notification. |
Plain text. {title} – the meeting title, {url} – link to the meeting. |
Other texts
These texts may also be in the list:
| System id | Description |
|---|---|
secure_meeting.connect_portal_domain |
The domain of Mividas Identify. Only used if no URL is set in SECURE_MEETING › Secure meetings settings. |
login.ldapadmin_intro, reset_password.*, secure_meeting.intro, secure_meeting.error |
Created automatically, but not used in the current version of Mividas Meeting Portal. You don’t need to edit them. |
1.9.10. Meetings

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
A read-only list of all meetings scheduled in the Mividas Meeting Portal. This includes meetings scheduled in the web interface, the Outlook add-in, and the APIs. From the list, you can resend meeting invitations.
Note: Meetings can’t be added or changed in the backend admin. To schedule, change, or cancel a meeting, use the portal.
List view

| Column | Description |
|---|---|
| Meeting | The title of the meeting. |
| Ts start | When the meeting starts. |
| Account user login | The login name of the meeting organizer. |
| Room number | The number used to join the meeting. |
| Ts created | When the meeting was scheduled. |
| Is active | Shows if the meeting is active. Canceled meetings are not active. |
Actions

Select one or more meetings in the list, choose an action in the Action menu and click Go.
| Action | Description |
|---|---|
| Resend emails for selected meetings | Sends the invitations again to all invited participants and moderators. For a recurring meeting, the invitations for the whole series are sent. The e-mails are sent in the background. |
| Resend emails for selected meetings as a new meeting series | First sends cancellations for the existing calendar invitations. Then the meeting gets a new calendar identity, and new invitations are sent to everyone. Use this when the recipients’ calendar entries are out of sync, for example, when updates aren’t applied, or entries are duplicated. The recipients get the old calendar entry canceled and a new entry created. |
| Delete selected meetings | Removes the selected meetings from the Mividas Meeting Portal database. You can also delete a single meeting with Delete on the meeting’s page. |
Warning: Deleting a meeting here doesn’t cancel it in Mividas Core or send any cancellation notifications. The meeting room can still be used, and the participants’ calendar entries are kept. To cancel a meeting, use the portal instead.
View a meeting

Click a meeting to see all details. All fields are read-only.
| Field | Description |
|---|---|
| Meeting title | The title of the meeting. |
| Ts start | When the meeting starts. |
| Ts stop | When the meeting ends. |
| Screen layout | The screen layout of the meeting: Automatic division of space, Speaker is prominent, other participants below, Share space between participants or Speaker only. |
| PIN | The PIN code for guests. |
| Department | The department selected when the meeting was scheduled, if any. See SECTION › Sections. |
| Lobby PIN | The PIN code for moderators. |
| Locked lobby | Shows if guests have to wait in the lobby until a moderator joins. |
| Source | Where the meeting was scheduled from, e.g. outlook for the Outlook add-in. Empty for meetings scheduled in the portal. |
| Record | The recording setting: No, Yes or Webcast. |
| Force encryption | Shows if only encrypted connections are allowed. |
| Existing room name | The name of the existing meeting room in which the meeting was scheduled, if any. |
| Send recording by e-mail | Shows if the recording is sent to the organizer by email. |
| Has recordings | Shows if the meeting has been recorded. |
| Recurrence id | Identifies the occurrence within a recurring meeting series. |
| Ews id | The ID of the calendar item in Microsoft Exchange, for meetings scheduled with the Outlook add-in. |
| Ical uid | The calendar ID used in the meeting invitations. |
| Organizer | The organizer’s address from the calendar, for meetings scheduled with the Outlook add-in. |
| Room number | The number used to join the meeting. |
| Recurring data | For recurring meetings: the recurrence rule and any changes, excluded or canceled occurrences. |
| Type | The meeting type. See MEETING_TYPE › Meeting types. |
| Section | The section in which the meeting was scheduled. |
Below the meeting details, related information is shown:
| Section | Description |
|---|---|
| Recurring meetings | The recurrence settings of the meeting series: rule, time zone, start, duration, exceptions, and changed occurrences. |
| Meeting invites | The invited participants and moderators, with their names, e-mail addresses, types, the dates the invitations were sent, and the dates personal data was removed. |
| Secure meeting invites | For secure meetings, the invited participants and moderators, including their identification and the invitation texts. |
| Meeting invite send logs | A log of each invitation that has been sent, with the time, the type of message, the occurrences it covered, and any errors. |
1.9.11. Meeting types

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure the meeting types users can choose from when scheduling a meeting in the Mividas Meeting Portal. Each enabled meeting type is shown as a booking button on the start page. The meeting type controls the scheduling form, the invitation steps, and how the meeting is sent to Mividas Core.
NOTE: For a complete guide to setting up custom meeting types and access methods, see Configure and use custom meeting types and access methods.
Secure meeting types have their own page, see SECURE_MEETING › Secure meeting types.
| Option | Description |
|---|---|
| Add meeting type + | Add a meeting type. |
Built-in meeting types
The built-in meeting types are created automatically; they vary depending on your license. You can change their settings, but you can’t remove them permanently. A deleted built-in meeting type is created again with its default settings. To hide one, uncheck Enable instead.
| Meeting type | System name in Core API |
|---|---|
| Video meeting | meeting |
| Webinar | webinar |
| Existing meeting room | cospace |
| External video meeting | external |
| Secure meeting | secure |
| Webex | webex |
| Hybrid Webex | webex_hybrid |
| Secure Webex | webex_secure |
| Secure hybrid Webex | webex_hybrid_secure |
List view

| Column | Description |
|---|---|
| Meeting type | The title of the meeting type, as shown on the scheduling button. |
| Enable | Shows if the meeting type is enabled. |
| System name in Core API | The meeting type key that is sent to Mividas Core. |
Add or edit a meeting type

Select a language tab at the top of the form to edit the texts in that language. The fields marked as translatable below have one value per language. Changes take effect in the portal within about ten seconds.
| Field | Description |
|---|---|
| Enable | When unchecked, the meeting type isn’t available in the portal. |
| System name in Core API | Required. The meeting type key sent to Mividas Core when a meeting is scheduled. Mividas Core uses the key to find a meeting type with a matching Meeting type match key, and applies its settings, e.g., call profiles and access methods. |
| Icon | The icon on the booking button. Enter a Font Awesome 5 icon name without the fa- prefix, see Available icons below. |
| Numerically | Required. The sort order of the booking buttons on the start page. Lowest first. |
| Hide booking button on home page | Hides the booking button from the start page. The meeting type can still be used in other ways, e.g., from the Outlook add-in or the API. |
| Enable invitation-step in the scheduling wizard | Shows the steps for inviting participants after a meeting is scheduled, as well as the invitation tabs on the meeting page. |
| Enable scheduled dialout-step in the scheduling wizard | Shows the steps for adding systems that are called automatically when the meeting starts. |
| Turn on moderator pin | Controls the moderator PIN code, see Moderator PIN options below. |
| Force guest PIN | Requires a PIN code for guests. If Mividas Core requires a PIN code, it’s always required. |
| Force moderator PIN to be set | Requires a PIN code for moderators. If Mividas Core requires a moderator PIN code, it’s always required. |
| Advanced settings | More settings in JSON format, see Advanced settings below. |
| Heading, button | The title of the meeting type, shown on the booking button. |
| Help text in button | The help text shown in the booking button. |
| Title in meeting scheduling wizard | The heading of the scheduling form. If empty, Heading, button is used. |
| Instructions title | The name of the participant’s instructions tab on the meeting page. |
| Moderator instructions title | The name of the moderator’s instructions tab on the meeting page. |
At the bottom of the page, Save as new creates a copy of the meeting type with your changes. The original isn’t changed. Only the texts in the selected language tab are copied, so add the translations for the other languages to the copy afterward.
Moderator PIN options
| Option | Description |
|---|---|
| Show choices to the user | The user decides when scheduling. If the user sets a moderator PIN code, the meeting gets moderator functions. |
| Yes, force | The meeting always includes moderator functions, with a moderator PIN code field and a step to invite moderators. |
| No, disable | The meeting never has moderator functions, and the moderator PIN code field is removed. |
Available icons
Only the icons included in the portal can be shown, for example: calendar-alt (default), calendar-check, video, desktop, chalkboard-teacher, comments, door-closed, globe, building, phone, laptop-medical, notes-medical, shield-alt, lock, user, user-cog, address-card, star, rss and th-large.
Advanced settings
The Advanced settings field contains settings for the meeting type in JSON format. For the built-in meeting types, it’s automatically filled with settings that differ from the standard. Only change the settings you need, and keep the rest. If a setting here also has its own field in the form, the value in Advanced settings is used.
Warning: Incorrect advanced settings can prevent users from scheduling this type of meeting.
Example:
{
"enable_recurring": false,
"hide_advanced": true,
"layout": "speakerOnly",
"pin_length": 6
}
Commonly used settings:
| Setting | Default | Description |
|---|---|---|
enable_recording |
true |
Shows the recording option. The option is also hidden if recording isn’t enabled for the user, or if it’s hidden in the theme settings. |
enable_recurring |
true |
Allows recurring meetings. When false, only single meetings can be scheduled. |
enable_wizard |
true |
After scheduling, it guides the user through the invitation steps. When false the user goes directly to the meeting page. |
hide_advanced |
false |
Hides the advanced settings section of the scheduling form. |
disable_advanced |
false |
Removes the advanced settings section of the scheduling form, and always uses the screen layout set in layout. |
layout |
"" |
The default screen layout: automatic, telepresence, allEqual or speakerOnly. |
enable_auto_lock_call |
false |
true shows an option to lock the lobby until a moderator joins, if Mividas Core supports it. "force" always locks the lobby. Requires a moderator PIN code. |
pin_length |
4 |
The length of generated PIN codes. A PIN length set in Mividas Core takes precedence. |
invite_body |
"body_only" |
Which parts of the meeting message are included in guest invitations: "body_only", "intro_and_body" or "intro_only". |
invite_moderator_body |
"body_only" |
The same, for moderator invitations. |
enable_send_email |
true |
Sends invitations by e-mail. |
include_all_participants |
false |
Lists all invited participants as attendees in the calendar invitation, so that they can see each other. |
enable_invite_rsvp |
false |
Asks the recipients to accept or decline the meeting in their calendar. |
attach_extra_ical_file |
false |
Also attaches the calendar invitation as a separate invite.ics file, for older calendar clients. |
override_location |
"" |
The text used as a location in calendar invitations, instead of the meeting link. Django template syntax can be used, e.g. "Video meeting {{ meeting.room_number }}". |
override_organizer_email |
"" |
Replaces the sender address (Reply-To and calendar organizer) in guest invitations. |
override_organizer_moderator_email |
"" |
The same, for moderator invitations. |
dialout_use_display_name |
false |
Includes the name of the called system in scheduled dial-outs sent to Mividas Core. |
remove_old_meetings |
null |
The number of days after a meeting has ended before it’s permanently deleted from the portal. null means that meetings are never deleted automatically. |
1.9.12. Section

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure sections in Mividas Meeting Portal. Sections appear as tabs on the start page and are required for the white-glove option.
| Option | Description |
|---|---|
| Add section + | Add a new section. |
List view

| Column | Description |
|---|---|
| Section | The title of the section. |
Add or edit a section

| Field | Description |
|---|---|
| Title | Required. The name of the section, shown on the tab. |
| Enabled | When unchecked, the section isn’t shown. The default section is always enabled. |
| Index | The sort order of the tabs. Lowest first. The default section is always shown first. |
| Default organizer | Not used in the current version of Mividas Meeting Portal. |
| Is admin only | Is only shown to users with Staff status. In the tab, the meetings of all users in the section are listed, not only the user’s own. The scheduling form has a Schedule as user field, where the administrator selects the user the meeting is scheduled for. |
| List meetings from sections | List the meetings from the selected sections in this section’s tab. Hold down Control, or Command on a Mac, to select more than one. |
| Is system default | Shows if this is the default section (read-only). |
Departments
Departments can be selected when scheduling a meeting in the section. The department is shown in the meeting, see MEETING › Meetings.
| Option | Description |
|---|---|
| Title | The name of the department. |
| Is default | The department that is preselected in the scheduling form. |
| Index | The sort order of the departments. Lowest first. |
| Delete | Check the box and click Save to remove the department. Meetings that used the department are kept without a department. |
| Add another Department | Adds another row for another department. |
Section meeting type overrides
Change the settings of a meeting type, only for meetings scheduled in this section.
| Option | Description |
|---|---|
| Meeting type | The meeting type to change. |
| Advanced settings | The settings to change, in JSON format, e.g. {"enable_recurring": false}. Uses the same settings as Advanced settings under MEETING_TYPE › Meeting types. In this section, these settings replace the meeting type’s own settings with the same name. |
| Delete | If not yet saved: click the delete icon (x) to remove the row. If already saved: check the box and click Save to remove the row. |
| Add another Section meeting type override | Adds another row for another meeting type. |
Delete a section
Deleting a section also deletes its departments and meeting type overrides. Meetings scheduled in the section are kept, but they’re no longer connected to any section, so they’re shown in the default section. The default section can’t be removed permanently.
1.9.13. Secure meeting

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure secure meetings where every participant and moderator must sign in before they can see the connection details. They can sign in through the portal, through Mividas Identify (organization login or eID) or with an SMS code. This section is only available when your license includes secure meetings.
This section contains the following settings pages:
1.9.13.1. Secure meeting types

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure the secure meeting types for Mividas Meeting Portal. In a secure meeting, every participant and moderator receives a personal invitation link and must sign in before they can see the connection details. Sign-in can be done via the Mividas Meeting Portal, Mividas Identify (organization login or eID, e.g., BankID), or with a code sent via SMS.
| Option | Description |
|---|---|
| Add secure meeting type + | Add a secure meeting type. |
Built-in secure meeting types
The built-in secure meeting types are created automatically. A deleted built-in type is created again with its default settings. To hide one, uncheck Enable instead.
| Meeting type | System name in Core API |
|---|---|
| Secure meeting | secure |
| Meeting with e-ID | secure |
| SMS meeting | secure |
| Secure Webex Meeting | webex_secure |
| Secure Hybrid Webex Meeting | webex_hybrid_secure |
List view

| Column | Description |
|---|---|
| Secure meeting type | The title of the meeting type, as shown on the booking button. |
| Enable | Shows if the meeting type is enabled. |
| System name in Core API | The meeting type key that is sent to Mividas Core. |
Add or edit a secure meeting type

| Field | Description |
|---|---|
| Title | The title of the meeting type. |
| Enable | When unchecked, the meeting type isn’t available in the portal. |
| System name in Core API | The meeting type key sent to Mividas Core. You can use a custom key to match a meeting type with its own settings in Mividas Core. |
| Icon | The icon on the scheduling button. Enter a Font Awesome 5 icon name without the fa- prefix, e.g. shield-alt or lock. See Available icons under MEETING_TYPE › Meeting types. |
| Numerically | Required. The sort order of the booking buttons on the start page. Lowest first. |
| Hide booking button on home page | Hides the booking button from the start page. The meeting type can still be used in other ways, e.g., from the Outlook add-in or the API. |
| Enable invitation-step in the scheduling wizard | Shows the steps for inviting participants after a meeting is scheduled. |
| Enable scheduled dialout-step in the scheduling wizard | Shows the steps for adding systems that are called automatically when the meeting starts. |
| Advanced settings | More settings in JSON format. Uses the same settings as Advanced settings under MEETING_TYPE › Meeting types. |
| Default login type moderator | The sign-in method that is preselected for moderators. |
| Selectable login modes, moderator | The sign-in methods the organizer can choose from for moderators, separated by commas. See Sign-in methods below. |
| Optional login method, moderator | Can be added for individual participants after the meeting is created. |
| Default sign-in type | The sign-in method that is preselected for participants. |
| Selectable login methods | The sign-in methods the organizer can choose from for participants, separated by commas. See Sign-in methods below. |
| Optional login method | Can be added for individual participants after the meeting is created. |
| Enable meeting agenda | Shows the agenda (instructions) tabs on the meeting page. |
| Enable separate agenda for moderator and participant | Lets the organizer write one agenda for moderators and another one for participants. |
| Enable sending invitations via another program | Shows the option to copy the personal invitation links and send them using another program, rather than via e-mail or SMS from the portal. |
| Replace sender address in moderator invitation email | Replaces the sender address (Reply-To and calendar organizer) in invitations to moderators. |
| Replace sender address in participant invitation email | Replaces the sender address (Reply-To and calendar organizer) in invitations to participants. |
| Number of days before meeting log is hidden in interface | The meeting log on the meeting page shows who has signed in. Entries older than this number of days are hidden. Default 7. Leave empty to show all entries. |
| Number of days before meeting log is deleted | Log entries older than this number of days are anonymized. The personal data in the invitations (name, e-mail address, mobile number, and identification) is also removed after this number of days has passed since the meeting ended. Leave empty to keep the data. |
| Heading, button | The title of the meeting type, shown on the scheduling button. |
| Help text in button | The help text shown on the scheduling button. |
| Title in meeting scheduling wizard | The heading of the scheduling form. If empty, Heading, button is used. |
| Description of form field for identification | The label of the identification field in the invitation form, e.g., Personal identity number. |
Sign-in methods
Use these values in the sign-in method fields. You can also enter only the first part of a value to include all methods of that kind. For example, eid includes both eid:identify and eid:validate. The default value is sso:portal, eid, sms.
| Value | Description |
|---|---|
none:none |
No extended sign-in. |
portal:login |
Regular login type in the booking portal. The person signs in with their ordinary portal account. |
sso:portal |
SSO login in Identify or the booking portal. |
sso:login |
Organization login via Mividas Identify. |
sso:all |
Organization or eID login. |
sso:validate |
Verify the person at the organization’s login. The signed-in person must match the identification entered in the invitation. |
eid:identify |
Log in with eID via Mividas Identify. |
eid:validate |
Verify the person at the eID login. The signed-in person must match the identification entered in the invitation. |
sms:code |
SMS invitation with verification code. |
guest:code |
Anyone who accesses the link can log in. |
You can change the names of the sign-in methods that users see under SECURE_MEETING › Secure meetings settings. The default invitation texts for secure meetings are edited under FLATBLOCKS › Text content.
1.9.13.2. Secure meetings settings

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure the connection between Mividas Meeting Portal and Mividas Identify, which handles organization and eID sign-in for secure meetings, as well as the SMS code settings. You can also change the names of the sign-in methods that are shown to users.
There should only be one record in this list. Click on it to edit it.
Edit the settings

| Field | Description |
|---|---|
| URL to Identify | The address of Mividas Identify, e.g. https://id.example.com. |
| Enable | Turns secure meetings on or off. When unchecked, the secure meeting types are not available. |
| Api key | The shared key that Mividas Identify uses to authenticate to the Mividas Meeting Portal. A random key is generated automatically. The same key must be configured in Mividas Identify. If you change it here, update Mividas Identify accordingly. |
| Enable automatic resending of SMS code on expired code | When enabled, a participant who tries to sign in with an expired SMS code automatically gets a new code by SMS. The text of the SMS is set in FLATBLOCKS › Text content, system id secure_meeting.sms_resend. |
| Number of minutes before SMS code expires | How long an SMS verification code is valid. Default 10. |
Note: The API key grants access to the portal’s secure meeting API. Keep it secret and share it only with Mividas Identify.
Secure meeting authentication types
Change the names of the sign-in methods, as they’re shown to organizers and participants. All sign-in methods are listed automatically and cannot be added or deleted here. Select a language tab above the list to edit the names in that language.
| Option | Description |
|---|---|
| Standard text | Displayed for all languages that do not have their own translation. |
| Text | Translated text for the selected language. Leave empty to use the standard text. |
1.9.14. Webhooks

Warning: Changes made here affect low-level platform behavior and can disrupt service if misconfigured. Only make changes if you understand their impact, and always use the regular Mividas Meeting Portal interface when the same setting is available there.
Configure webhooks to notify external systems of events in the Mividas Meeting Portal, e.g., when a user signs in or a meeting is scheduled, modified, or canceled. Webhooks can also be used to send SMS messages through your own SMS gateway.
| Option | Description |
|---|---|
| Add webhook + | Add a new webhook. |
List view

| Column | Description |
|---|---|
| Title | The descriptive name of the webhook. |
| Enabled | Shows if the webhook is enabled. |
| Url | The address to which the events are sent. |
Add or edit a webhook

| Field | Description |
|---|---|
| Title | A descriptive name, e.g., the name of the receiving system. |
| Enabled | When unchecked, no events are sent to this webhook. |
| Url | The address to which the events are sent. Use an https:// address. |
| Secret | The key used to sign the events. See Verify the signature. A random secret is generated automatically. The secret is stored encrypted. |
| User events | Send the events user.login and user.delegate. |
| Meeting events | Send the events meeting.book, meeting.rebook and meeting.unbook. |
| Sms events | Used only when SMS provider is set as webhook in the Installer. Send the event sms.invite. |
| Other events | Send other types of events. |
| Ts last error | When the latest delivery error occurred. For a new webhook, this is set to the webhook’s creation time. |
| Ts last success | When the last event was successfully delivered. |
| Last error | The error message of the latest failed delivery. |
| Error count | The number of failed deliveries since the last successful one. |
Events
| Event | Description |
|---|---|
user.login |
A user signed in. The event includes is_first_login, which is true the first time the user signs in. |
user.delegate |
A user started managing meetings on behalf of another user. |
meeting.book |
A meeting was scheduled. |
meeting.rebook |
A meeting was changed. |
meeting.unbook |
A meeting was canceled. |
sms.invite |
An SMS invitation to a secure meeting should be sent. The receiving system sends the SMS. |
Request format
Each event is sent as an HTTP POST request with a JSON body. Example of an meeting.book event:
{
"event": "meeting.book",
"created": "2026-10-05T07:30:00+00:00",
"user": {
"username": "[email protected]",
"email": "[email protected]",
"video_username": "[email protected]",
"ldap_dn": "CN=Sven Svensson,OU=Users,DC=example,DC=com"
},
"delegate": null,
"site": {
"domain": "portal.example.com"
},
"meeting": {
"id": 1234,
"title": "Project meeting",
"public_title": "Project meeting",
"type": 0,
"type_api_name": "meeting",
"ts_start": "2026-10-06T08:00:00+00:00",
"ts_stop": "2026-10-06T09:00:00+00:00",
"recurring_rule": null,
"api_id": "…",
"source": "",
"sip_uri": "…",
"moderator_sip_uri": "…"
}
}
| Key | Description |
|---|---|
event |
The name of the event. |
created |
When the event happened. |
user |
The user the event concerns. For meeting events, this is the meeting organizer. |
delegate |
The user who acted on behalf of user, e.g., through a delegation. null if the user acted for themselves. |
site |
The domain of the portal that sent the event. |
meeting |
Meeting events and SMS events: information about the meeting. |
recipient, message, sender |
SMS events only: the mobile number in international format without +, the text of the SMS, and the sender name. |
The request includes these headers:
| Header | Description |
|---|---|
X-Mividas-Signature |
An HMAC-SHA256 signature of the request body in hexadecimal format, created with the webhook’s secret. |
X-Mividas-Webhook |
The ID of the webhook. |
X-Mividas-Delivery-Try |
The delivery attempt, starting at 1. |
Verify the signature
To ensure an event comes from the Mividas Meeting Portal, calculate the HMAC-SHA-256 of the raw request body using the webhook’s secret. Then compare the result with the X-Mividas-Signature header. Example in Python:
import hashlib
import hmac
def is_valid_signature(body: bytes, signature: str, secret: str) -> bool:
expected = hmac.new(secret.encode('utf-8'), body, hashlib.sha256).hexdigest()
return hmac.compare_digest(expected, signature)
Delivery and errors
- The receiving system must respond with HTTP status
200within 10 seconds. Any other response counts as an error. - A failed event is resent up to 5 times after about 1, 2, 4, 8, and 16 minutes. SMS events are sent directly and are not retried.
- After 50 consecutive failed deliveries, the webhook is paused. Events that occur during the pause are not delivered. The webhook is retried after an hour has passed since the last error.
- Error count is reset when an event is delivered successfully or when you change the URL.




















