Portal sync connections forward calendar meetings that Mividas Core has synced to a Mividas Meeting Portal. Mividas Core posts every matched meeting to the Mividas Meeting Portal’s calendar-sync import API, where it is connected to a user and appears like any other meeting. For example, a meeting added to a room’s calendar, or a user’s meeting caught in a catch-all mailbox, is automatically pushed to the Mividas Meeting Portal, and subsequent edits and cancellations follow.
Each connection authenticates against one Mividas Meeting Portal in one of two modes: an OAuth application (Client ID + Secret) or a static API key (X-Mividas-Token).
| Option | Description |
|---|---|
| Add a Portal sync connection + | Add a Portal sync connection. |
Add a Portal sync connection
| Option | Description |
|---|---|
| Customer | Select the customer this record applies to. |
| Application (Client) ID | The Portal OAuth application’s Client ID. Fill in for OAuth authentication; leave empty when using an API key. |
| Client secret | The Portal OAuth application’s client secret. Used together with the Client ID for OAuth authentication. |
| Portal address | Base URL to the Mividas Meeting Portal, e.g., https://portal.example.org. |
| Name | A label for this connection. |
| Enabled | Turn the connection on or off. A disabled connection is skipped and never blocks other syncs. |
| API key | Used for static X-Mividas-Token authentication instead of OAuth. Leave empty when using Client ID and Secret. |
| Sync all meetings | Send all matched meetings to the Mividas Meeting Portal, not only those for systems with a calendar connection. Enable this to also forward meetings that only pass through a catch-all service account. |
| Catch-all organizer filter (regex) | Only meetings whose organizer matches this regular expression are synced from catch-all calendars. Blank = all. Matched case-insensitively. E.g. @example\.org$ syncs only that domain’s organizers. Rooms meetings are never filtered. |
| Trigger address | The address to match in the meeting’s location/attendees, e.g., @mividas. |
| Meeting type | The meeting type to book with; leave blank for the default type. |
| Calendar connections | Select which calendar connections’ meetings are sent to the Mividas Meeting Portal. |
Portal service accounts
Optional. Add a shared mailbox that captures all users’ meetings (for users without a room device). Saving provisions a catch-all calendar for that mailbox automatically. Use together with Sync all meetings so its non-room meetings are actually forwarded.
| Option | Description |
|---|---|
| Calendar connection | The EWS/Graph connection that can read the mailbox. |
| Service account | The service-account mailbox address (UPN/SMTP) that catches all meetings. |
| Add another Portal Service Account | Add another Portal Service Account. |