--- title: "Auto Provisioning Token" slug: "administrator-help-auto-provisioning-token" updated: 2025-07-29T20:27:24Z published: 2025-07-29T20:27:24Z canonical: "support.nvoq.com/administrator-help-auto-provisioning-token" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.nvoq.com/llms.txt > Use this file to discover all available pages before exploring further. # Auto Provisioning Tokens On the Auto Provisioning Token page system or tenant level administrators can create accounts and tokens to be used with an identity provider to create nVoq accounts through that provider that can sign in using SSO. Tokens can also be deleted on this page. Account provisioning on this page currently only works with Okta and Microsoft Entra ID.Account provisioning is not supported with any other identity management service at this time. ## Create a New Token 1. Click on the actions icon![Accounts-actions-icon](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/Accounts-actions-icon.png)next to an identity provider on the Identity Providers page and select **Auto Provisioning Token**. 2. On the Auto Provisioning Token page, click the **Create new token** button. ![Create-new-token-button](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/Create-new-token-button.png) - When a new token is created for the first time a provisioning account with a **Generated Administrator Username** (near the top of the page) is created. - This non-billable account is visible on the Accounts page at the tenant level. - The actual JSON Web **Token** (JWT) is displayed in an un-editable text area. **You will only be able to see this token once. When you close this page (or click the Create New Token button again), it is gone forever.** ![IdentityProvider-create-new-token-page](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/IdentityProvider-create-new-token-page.png) - You can create a maximum of two (2) tokens per provisioning account. The second one allows you to update to a new token before the first one expires and stops working. If you attempt to create a token when two already exist, a red popup notification will appear in the top right of the screen stating, "Could not create token." A notification message (under the bell icon![Notifications-icon](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/Notifications-icon.png)in the upper-right corner) explains that a token could not be created because "too many provisioning tokens already exist." 3. Click the **Copy token to clipboard** icon next to the token to copy it to your computer's clipboard. ![IdentityProvider-copy-token-to-clipboard](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/IdentityProvider-copy-token-to-clipboard.png) 4. Use the *copied token* together with the *generated administrator username* with your identity provider to create nVoq accounts that can be accessed via SSO. - Using the provisioning account the Okta or Microsoft Entra ID provider can send SCIM data to the nVoq system.  (The nVoq system does not send SCIM data to Okta or Microsoft Entra ID.) 5. Your token will automatically expire one year from the date it is created. Tokens are deleted from this page seven (7) days after they expire. - An email will be sent to all administrators with a Customer Administrator role at the tenant level to notify them of an upcoming identity provider token expiration. - Notifications are sent 30, 14, 7, 3, and 1 day before the token expires. ## Delete a Token 1. Click on the actions icon![Accounts-actions-icon](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/Accounts-actions-icon.png)next to an identity provider on the Identity Providers page and select **Auto Provisioning Token**. 2. Click the **trash icon**![trash-icon](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/trash-icon.png)next to the token you want to delete. 3. You will be asked to confirm that you want to delete the token. Click **Yes, delete Provisioning token** to permanently remove the token. ![IdentityProvider-delete-token-confirmation](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/IdentityProvider-delete-token-confirmation.png) 4. For troubleshooting purposes deleted token information remains on the Auto Provisioning Token page (along with the username of the person who deleted it) until the token's expiration date.![IdentityProvider-deleted-token-page](https://cdn.us.document360.io/03b5534a-5f9a-42ce-852d-08bf09105da4/Images/Documentation/IdentityProvider-deleted-token-page.png) Single Sign-On (SSO) lets users access multiple applications with one username and password. nVoq supports SSO with Microsoft Entra ID (formerly Azure AD) or Okta. System for Cross-domain Identity Management (SCIM) is an open standard that simplifies cloud identity management and allows user provisioning to be automated across multiple domains.