
Define the meeting types (templates) that users can choose when scheduling meetings or creating static meeting rooms.
NOTE: For a more complete guide on how to properly set up custom meeting types and access methods, see Configure and use custom meeting types and access methods
| Option | Description |
|---|---|
| Recover deleted meeting types | Allows you to recover previously deleted meeting types. |
| Add meeting type + | Add a meeting type. |
Add a meeting type

Start by entering a Title and selecting a Cluster for the meeting type, then click to reveal the remaining options.

| Option | Description |
|---|---|
| Key | Enter a key to use to match this meeting type from Mividas Meeting Portal and invite templates. E.g. custom_meeting_1 |
| Delete | If not yet saved: Click (
) to remove that row. If already saved: Check the box and click to remove that row. |
| Add another Meeting type match key | Adds another row to add another meeting type match key. |

| Option | Description |
|---|---|
| Customer | Select the customer this override applies to. Each customer can only have one override per meeting type. |
| Show in Core | Override whether this meeting type is visible when creating static meeting rooms in Mividas Core for this specific customer. Unknown – Use the default setting from the meeting type. Yes – Show this meeting type in Mividas Core for this customer. No – Hide this meeting type in Mividas Core for this customer. |
| For all users | Override whether this meeting type is visible in the Mividas Meeting Portal for all users of this customer. Unknown – Use the default setting from the meeting type. Yes – Show this meeting type in the Mividas Meeting Portal for all users in this customer. No – Hide this meeting type in the Mividas Meeting Portal for this customer. |
| Meeting type key | A customer-specific key that can be used to look up this meeting type instead of the default match keys. This allows different customers to reference the same meeting type using different keys. |
| Delete | If not yet saved: Click (
) to remove that row. If already saved: Check the box and click to remove that row. |
| Add another override for customer | Adds another row to add another override. |

| Option | Description |
|---|---|
| Enabled | Check to enable this access method. |
| Title | Enter a title for this access method. |
| Call leg profile | Select which call leg profile to use for this access method. |
| Lobby profile | Select which lobby profile to use for this access method. |
| Always create | When enabled, this access method will always be created for rooms using this meeting type, regardless of other conditions. When disabled, the access method is only created when matching conditions are met, such as a moderator PIN being set. |
| Fallback setting | When enabled, this access method is used as the fallback for all additional addresses matching the same member scope. When disabled, the access method is only used when explicitly matched. |
| Is the default address for room | When enabled, this access method will be used as the primary address for the meeting room. Only one access method per meeting type can be set as the default. Enabling this will automatically unset the default flag on other access methods in the same meeting type. |
| System ID | Defines the role of this access method. Only one guest and one moderator access method can exist per meeting type; any additional access methods must be set to None. None – No specific role assigned. Used for additional access methods such as member or directory entries. Guest – This access method is for guest participants joining without moderator privileges. Moderator – This access method is for moderator participants with full meeting control. |
| Member scope | Defines who can use this access method to join the meeting. None – No specific scope. The access method is not restricted. Public – Anyone can join using this access method. Private – Only specific members or moderators can join. Member – Only organization members can join. Directory – Only users listed in the directory can join. |
| Overrides for values sent via API to MCU | A JSON object with additional or overriding values that will be sent to the provider API for this specific access method. These values are not synced to the provider template. |
| Delete | If not yet saved: Click (
) to remove that row. If already saved: Check the box and click to remove that row. |
| Add another access method | Adds another row to add another access method. |