Skip to main content

​
After this article

You’ll be able to connect Dialpad to Lumos to sync users and their roles for visibility, Access Reviews, and offboarding, including suspending and deprovisioning Dialpad users directly from Lumos.

​
Capabilities

Status mapping: Lumos maps Dialpad user statuses to account statuses as follows. Suspending a user in Lumos sets their Dialpad state to suspended, which marks the Lumos account Suspended and blocks login. Deprovisioning permanently removes the user from Dialpad. The account record still exists, but all metadata is removed, so the user becomes effectively faceless. Both actions reclaim a Dialpad license.

​
Required plan and roles

  • Dialpad plan: no minimum Dialpad plan is required to connect this integration.
  • Dialpad role: your Dialpad user must be the Company Admin to connect the integration.
  • Permission scoping: you accept the requested scopes in Dialpad during setup. The connection lists users (read) and, when you trigger it, suspends or deletes users (write).

​
Read-only access vs provisioning

Is read-only possible? No. You accept a single set of requested scopes during setup, and that connection covers both listing users (read) and, when you trigger it, suspending or deleting them (write). What full provisioning requires. The connecting Dialpad user must be the Company Admin, since other roles can’t grant the requested scopes. Once connected, Lumos can suspend or delete Dialpad users, both of which reclaim a license. Follow the steps below to connect and accept the scopes. Watch out for. Deletion is permanent in Dialpad, the account record remains but all metadata is stripped, so you’d need to re-create the user’s details if you delete by mistake. Suspending, by contrast, is reversible and still reclaims the license.

​
Instructions

Phase 1: Connect in Lumos
  1. Find the Dialpad card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Click Connect.
  3. Accept the scopes in Dialpad to finish connecting the integration.

​
API Endpoints Used

​
Troubleshooting

Connection fails during setup. Confirm the Dialpad user authorizing the connection is the Company Admin. Other roles can’t grant the requested scopes. A user shows as Deprovisioned unexpectedly. Dialpad reports the user’s state as deleted or cancelled, so Lumos marks the account Deprovisioned. Check the user in the Dialpad admin console. Deprovisioned a user by mistake. Deletion is permanent in Dialpad. The account record remains but all metadata is removed, so you’ll need to re-create the user’s details in Dialpad.