Time-limited logins are a time-limited permission to enter a specific dial alias. Each authorization is valid between two timestamps, can be capped to a set number of uses, and can carry meeting-setting overrides such as a PIN, an enforced display name, or moderator status. In practice, you’ll rarely create these manually.
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 Core/Rooms interface when the same setting is available there.
| Option | Description |
|---|---|
| Add a time-limited login + | Add a time-limited login. |
Add a time-limited login
| Field | Description |
|---|---|
| Customer | Select the customer this record applies to. |
| Cluster | Select the video cluster this record applies to. |
| Local alias | The exact alias of the incoming call must be dialed. |
| Valid from | The date/time from which this record is valid. |
| Valid to | The date/time until which this record is valid. |
| Require fields | JSON conditions the call must satisfy, e.g., {"remote_display_name": "Test"}. |
| Settings override | JSON that is applied to the meeting when this record matches (PIN, moderator role, enforced display name, layout, etc.). |
| Usage limit | The number of times this login can be applied. Note: This will be automatically doubled for new objects when using Pexip due to the two-step handshake. |
| Usage count | How many times this login has been used. |
| Created | When this record was created. |
| User | The user associated with this record. |
| System | Displays how the logion was created, e.g., book_api. |
| External ID | The external ID of the login. |
| First use | The time when this login was first used. |