--- title: How To Guide for Access Software Plugin excerpt: '' deprecated: false hidden: true metadata: title: '' description: '' robots: index next: description: '' --- # How To Configure Active Directory Group Based Software Provisioning ### Pre-Requisites * Please ensure the required Active Directory Connector has been created with the necessary permissions. Please refer the **[Active Directory / LDAP Access Requirements Doc](/docs/active-directory-ldap-access-requirements)** for details. * Please ensure the required **Grant Software Access Plugin** is set to **TRUE** within the **Copilot Plugin Management** settings. There should be **no Deflection Message** listed. * The **distinguishedName** of the Active Directory group that controls access to this software is needed. The full OU path to this group will be required. ### Configuration Start by navigating to **Software Access > Connector Settings** 1. Click on the **Setup provisioning systems** toggle to expand the settings. ![](https://files.readme.io/9c744ffa668678ec77ee6701a43041f739d44fe8e444fc81a95be939ddabdcf2-image.png) 2. Under the **Provisioners** settings, click on **Add +** to add in a new software provisioning system. 3. Select your Active Directory connector within the **Select connector** dropdown. 1. *Optionally*, you can provide a **Post Provisioning URL** to your software portal which will be served to the user once the workflow is completed. ![](https://files.readme.io/b6aa83591edd5487fbfc2fbaa082f6ae72f81f8fd53e162551a06f18d09ff500-image.png) 4. Click **Submit** at the bottom of the page Next, navigate to **Software Access > Software Catalog** 1. Type in your software name within the **Software/Application Name** text box to search across all of the Moveworks software entities. When your software is shown, click on it from the dropdown to select it. ![](https://files.readme.io/95f7dfb87015a1ab50cfc94f44cf0a9fb6886499e8e80f17b68161d35ef0ca14-image.png) 2. Toggle on the **Enable software provisioning in the bot** checkbox to enable this software to be provisioned by the AI Assistant. ![](https://files.readme.io/b18b06683e584209e9a77f9ca3259e056981b2aa1bb880983ce9643bcb6e6fa7-image.png) 3. *Optionally*, enter a DSL rule within the **Access Rule** DSL box. To activate this skill for all users, set the DSL value to **TRUE**. To only have this skill be available to certain users, leverage the Moveworks DSL Syntax in the [Guide here](/docs/moveworks-dsl-reference) . By default, the DSL rule is set to **TRUE**. ![](https://files.readme.io/cd26685280179556401b92941bc187ce27475ae1c7082f7b908304325abb8e00-image.png) 4. Set the **Provisioning Strategy** to **Group Based Provisioning** ![](https://files.readme.io/ced2cceba3abd0c07380d6e37dadde8a1bfb934c4a1d5ca03c3dc668fff6042c-image.png) 5. Choose your Active Directory connector within **Provisioning System**. ![](https://files.readme.io/7dc5df4dfeb179ec1455671899605eb0c46cd57d0f87ea99bf6b6a39242598d6-image.png) 6. Set the **External ID** to the **distinguishedName** of the group that controls access to this software. ![](https://files.readme.io/c57bccd176660f1dc142054d9b0930d344412b2695aaaeb35b6bd2b5db1abaa2-image.png) 7. Choose an **Approval Workflow** which will define the approval needed before provisioning the application to the the user. There are pre-defined approval workflows or custom approval workflows. 1. Below are the most common pre-defined approval workflows. You can learn more about all possible pre-defined approval workflows and custom approval workflows within the [Configure Approvals Engine doc](/docs/moveworks-setup-native-approval-settings#custom-attributes-configuration). 1. **AUTO\_APPROVE**: Here, asks or requests are automatically approved, bypassing the need for an approving authority. 2. **APP\_ADMIN**: The Application Administrator's approval is necessary to carry out certain functions. 3. **MANAGER**: This type of approval requires the consent of the individual's Manager. 4. **APP\_ADMIN\_THEN\_MANAGER**: A two-step approval process. First, the App Admin needs to approve. If approved, the workflow moves to require the Manager's approval. 5. **Custom Approval Method**: This is more suited, if pre-defined approval method workflows do not suffice your org’s requirements for software provisioning. Customer Approval workflows are created separately in Moveworks Native Approvals module. ![](https://files.readme.io/978884d679a13460f62204e5134e702c6e25f6b19e872ffebec5c66dc4661a91-image.png) 7. Click **Submit** at the bottom of the page. ### Validation The defined software is now available within the AI Assistant. This can be verified by requesting the software within the AI Assistant. The AI Assistant should do the following if fully configured: 1. Confirm that you want to provision the certain software. 2. Create a ticket within the ITSM system to track the provisioning request. 3. Add you to the Active Directory group. 4. Confirm with you that the process is completed. *** # How To Configure Active Directory Role Based Software Provisioning ### Pre-Requisites * Please ensure the required Active Directory Connector has been created with the necessary permissions. Please refer the **[Active Directory / LDAP Access Requirements Doc](/docs/active-directory-ldap-access-requirements)** for details. * Please ensure the required **Grant Software Access Plugin** is set to **TRUE** within the **Copilot Plugin Management** settings. There should be **no Deflection Message** listed. * The **distinguishedName** of the Active Directory groups that controls access to the software roles is needed. The full OU path to these groups will be required for each role. ### Configuration Start by navigating to **Software Access > Connector Settings** 1. Click on the **Setup provisioning systems** toggle to expand the settings. ![](https://files.readme.io/9c744ffa668678ec77ee6701a43041f739d44fe8e444fc81a95be939ddabdcf2-image.png) 2. Under the **Provisioners** settings, click on **Add +** to add in a new software provisioning system. 3. Select your Active Directory connector within the **Select connector** dropdown. 1. *Optionally*, you can provide a **Post Provisioning URL** to your software portal which will be served to the user once the workflow is completed. ![](https://files.readme.io/b6aa83591edd5487fbfc2fbaa082f6ae72f81f8fd53e162551a06f18d09ff500-image.png) 4. Click **Submit** at the bottom of the page Next, navigate to **Software Access > Software Catalog** 1. Type in your software name within the **Software/Application Name** text box to search across all of the Moveworks software entities. When your software is shown, click on it from the dropdown to select it. ![](https://files.readme.io/95f7dfb87015a1ab50cfc94f44cf0a9fb6886499e8e80f17b68161d35ef0ca14-image.png) 2. Toggle on the **Enable software provisioning in the bot** checkbox to enable this software to be provisoned by the AI Assistant. ![](https://files.readme.io/b18b06683e584209e9a77f9ca3259e056981b2aa1bb880983ce9643bcb6e6fa7-image.png) 3. *Optionally*, enter a DSL rule within the **Access Rule** DSL box. To activate this skill for all users, set the DSL value to **TRUE**. To only have this skill be available to certain users, leverage the Moveworks DSL Syntax in the [Guide here](/docs/moveworks-dsl-reference) . By default, the DSL rule is set to **TRUE**. ![](https://files.readme.io/cd26685280179556401b92941bc187ce27475ae1c7082f7b908304325abb8e00-image.png) 4. Set the **Provisioning Strategy** to **Role Based Provisioning** ![](https://files.readme.io/5e7b6a9b69ba84f4c85049885a459ae29655df36d4f3c458647c7ebb12cb46ad-image.png) 5. Choose your Active Directory connector within **Role Based Provisioning Integration Id**. ![](https://files.readme.io/a45a3d401a73f631b7c17214baf7cb207386a0dc36b4d2d9e628005c0b52351f-image.png) 6. Define the Unique role name, Description, User facing name, and External ID of the roles within the software app. ![](https://files.readme.io/d843dd017495ca746dac44577a89593a1f0a60f4370548e2286dbe744d434aff-image.png) 7. Choose an **Approval Workflow** which will define the approval needed before provisioning the application to the the user. There are pre-defined approval workflows or custom approval workflows. 1. Below are the most common pre-defined approval workflows. You can learn more about all possible pre-defined approval workflows and custom approval workflows within the [Configure Approvals Engine doc](/docs/moveworks-setup-native-approval-settings#custom-attributes-configuration). 1. **AUTO\_APPROVE**: Here, asks or requests are automatically approved, bypassing the need for an approving authority. 2. **APP\_ADMIN**: The Application Administrator's approval is necessary to carry out certain functions. 3. **MANAGER**: This type of approval requires the consent of the individual's Manager. 4. **APP\_ADMIN\_THEN\_MANAGER**: A two-step approval process. First, the App Admin needs to approve. If approved, the workflow moves to require the Manager's approval. 5. **Custom Approval Method**: This is more suited, if pre-defined approval method workflows do not suffice your org’s requirements for software provisioning. Customer Approval workflows are created separately in Moveworks Native Approvals module. ![](https://files.readme.io/978884d679a13460f62204e5134e702c6e25f6b19e872ffebec5c66dc4661a91-image.png) 7. Click **Submit** at the bottom of the page. ### Validation The defined software is now available within the AI Assistant. This can be verified by requesting the software within the AI Assistant. The AI Assistant should do the following if fully configured: 1. Confirm that you want to provision the certain software and ask to distinguish which role is desired. 2. Create a ticket within the ITSM system to track the provisioning request. 3. Add you to the Active Directory group. 4. Confirm with you that the process is completed. *** # How To Configure Okta Group Based Software Provisioning ### Pre-Requisites * Please ensure the required Okta Connector has been created with the necessary permissions. Please refer the **[Okta Access Requirements Doc](/docs/okta-access-requirements)** for details. * Please ensure the required **Grant Software Access Plugin** is set to **TRUE** within the **Copilot Plugin Management** settings. There should be **no Deflection Message** listed. * The **Okta group** that controls access to this software is needed. This group name will begin with *00g*. ### Configuration Start by navigating to **Software Access > Connector Settings** 1. Click on the **Setup provisioning systems** toggle to expand the settings. ![](https://files.readme.io/9c744ffa668678ec77ee6701a43041f739d44fe8e444fc81a95be939ddabdcf2-image.png) 2. Under the **Provisioners** settings, click on **Add +** to add in a new software provisioning system. 3. Select your Okta connector within the **Select connector** dropdown. 1. *Optionally*, you can provide a **Post Provisioning URL** to your software portal which will be served to the user once the workflow is completed. ![](https://files.readme.io/f0331836aaddc21d01db12fd8d303b78461ac08bb581c4f31dce109328a5be55-image.png) 4. Click **Submit** at the bottom of the page Next, navigate to **Software Access > Software Catalog** 1. Type in your software name within the **Software/Application Name** text box to search across all of the Moveworks software entities. When your software is shown, click on it from the dropdown to select it. ![](https://files.readme.io/95f7dfb87015a1ab50cfc94f44cf0a9fb6886499e8e80f17b68161d35ef0ca14-image.png) 2. Toggle on the **Enable software provisioning in the bot** checkbox to enable this software to be provisioned by the AI Assistant. ![](https://files.readme.io/b18b06683e584209e9a77f9ca3259e056981b2aa1bb880983ce9643bcb6e6fa7-image.png) 3. *Optionally*, enter a DSL rule within the **Access Rule** DSL box. To activate this skill for all users, set the DSL value to **TRUE**. To only have this skill be available to certain users, leverage the Moveworks DSL Syntax in the [Guide here](/docs/moveworks-dsl-reference) . By default, the DSL rule is set to **TRUE**. ![](https://files.readme.io/cd26685280179556401b92941bc187ce27475ae1c7082f7b908304325abb8e00-image.png) 4. Set the **Provisioning Strategy** to **Group Based Provisioning** ![](https://files.readme.io/ced2cceba3abd0c07380d6e37dadde8a1bfb934c4a1d5ca03c3dc668fff6042c-image.png) 5. Choose your Okta connector within **Provisioning System**. ![](https://files.readme.io/3a152160e06c475b6b8cb308739973c36e242058d1d1a4b5aff287b59f1cf958-image.png) 6. Set the **External ID** to the **Okta group** that controls access to this software. ![](https://files.readme.io/4713917a3cbf68bb342d489626fdb0cf518954a3ca1a93a165dd3c3afad98711-image.png) 7. Choose an **Approval Workflow** which will define the approval needed before provisioning the application to the the user. There are pre-defined approval workflows or custom approval workflows. 1. Below are the most common pre-defined approval workflows. You can learn more about all possible pre-defined approval workflows and custom approval workflows within the [Configure Approvals Engine doc](/docs/moveworks-setup-native-approval-settings#custom-attributes-configuration). 1. **AUTO\_APPROVE**: Here, asks or requests are automatically approved, bypassing the need for an approving authority. 2. **APP\_ADMIN**: The Application Administrator's approval is necessary to carry out certain functions. 3. **MANAGER**: This type of approval requires the consent of the individual's Manager. 4. **APP\_ADMIN\_THEN\_MANAGER**: A two-step approval process. First, the App Admin needs to approve. If approved, the workflow moves to require the Manager's approval. 5. **Custom Approval Method**: This is more suited, if pre-defined approval method workflows do not suffice your org’s requirements for software provisioning. Customer Approval workflows are created separately in Moveworks Native Approvals module. ![](https://files.readme.io/978884d679a13460f62204e5134e702c6e25f6b19e872ffebec5c66dc4661a91-image.png) 7. Click **Submit** at the bottom of the page. ### Validation The defined software is now available within the AI Assistant. This can be verified by requesting the software within the AI Assistant. The AI Assistant should do the following if fully configured: 1. Confirm that you want to provision the certain software. 2. Create a ticket within the ITSM system to track the provisioning request. 3. Add you to the Okta group. 4. Confirm with you that the process is completed. *** # How to Configure Okta Role Based Software Provisioning ### Pre-Requisites * Please ensure the required Okta Connector has been created with the necessary permissions. Please refer the **[Okta Access Requirements Doc](/docs/okta-access-requirements)** for details. * Please ensure the required **Grant Software Access Plugin** is set to **TRUE** within the **Copilot Plugin Management** settings. There should be **no Deflection Message** listed. * The **Okta groups** that controls access to the software roles is needed. This group names will begin with *00g*. ### Configuration Start by navigating to **Software Access > Connector Settings** 1. Click on the **Setup provisioning systems** toggle to expand the settings. ![](https://files.readme.io/9c744ffa668678ec77ee6701a43041f739d44fe8e444fc81a95be939ddabdcf2-image.png) 2. Under the **Provisioners** settings, click on **Add +** to add in a new software provisioning system. 3. Select your Okta connector within the **Select connector** dropdown. 1. *Optionally*, you can provide a **Post Provisioning URL** to your software portal which will be served to the user once the workflow is completed. ![](https://files.readme.io/731d1ed33fb2ae635403a0dc33d731e0af9ed9f3c92018c85c22f1b32da91e24-image.png) 4. Click **Submit** at the bottom of the page Next, navigate to **Software Access > Software Catalog** 1. Type in your software name within the **Software/Application Name** text box to search across all of the Moveworks software entities. When your software is shown, click on it from the dropdown to select it. ![](https://files.readme.io/95f7dfb87015a1ab50cfc94f44cf0a9fb6886499e8e80f17b68161d35ef0ca14-image.png) 2. Toggle on the **Enable software provisioning in the bot** checkbox to enable this software to be provisoned by the AI Assistant. ![](https://files.readme.io/b18b06683e584209e9a77f9ca3259e056981b2aa1bb880983ce9643bcb6e6fa7-image.png) 3. *Optionally*, enter a DSL rule within the **Access Rule** DSL box. To activate this skill for all users, set the DSL value to **TRUE**. To only have this skill be available to certain users, leverage the Moveworks DSL Syntax in the [Guide here](/docs/moveworks-dsl-reference) . By default, the DSL rule is set to **TRUE**. ![](https://files.readme.io/cd26685280179556401b92941bc187ce27475ae1c7082f7b908304325abb8e00-image.png) 4. Set the **Provisioning Strategy** to **Role Based Provisioning** ![](https://files.readme.io/5e7b6a9b69ba84f4c85049885a459ae29655df36d4f3c458647c7ebb12cb46ad-image.png) 5. Choose your Okta connector within **Role Based Provisioning Integration Id**. ![](https://files.readme.io/6dd576c794b53182d2e9d15b0217189f46d3e0e478724fc35b1d7a2cf8876c02-image.png) 6. Define the **Unique role name**, **Description**, **User facing name**, and **External ID** of the roles within the software app. ![](https://files.readme.io/527e1db58c0a5d8799bb1b0888f69b95156c906fc5cdcd6698a84290b118f282-image.png) 7. Choose an **Approval Workflow** which will define the approval needed before provisioning the application to the the user. There are pre-defined approval workflows or custom approval workflows. 1. Below are the most common pre-defined approval workflows. You can learn more about all possible pre-defined approval workflows and custom approval workflows within the [Configure Approvals Engine doc](/docs/moveworks-setup-native-approval-settings#custom-attributes-configuration). 1. **AUTO\_APPROVE**: Here, asks or requests are automatically approved, bypassing the need for an approving authority. 2. **APP\_ADMIN**: The Application Administrator's approval is necessary to carry out certain functions. 3. **MANAGER**: This type of approval requires the consent of the individual's Manager. 4. **APP\_ADMIN\_THEN\_MANAGER**: A two-step approval process. First, the App Admin needs to approve. If approved, the workflow moves to require the Manager's approval. 5. **Custom Approval Method**: This is more suited, if pre-defined approval method workflows do not suffice your org’s requirements for software provisioning. Customer Approval workflows are created separately in Moveworks Native Approvals module. ![](https://files.readme.io/978884d679a13460f62204e5134e702c6e25f6b19e872ffebec5c66dc4661a91-image.png) 7. Click **Submit** at the bottom of the page. ### Validation The defined software is now available within the AI Assistant. This can be verified by requesting the software within the AI Assistant. The AI Assistant should do the following if fully configured: 1. Confirm that you want to provision the certain software and ask to distinguish which role is desired. 2. Create a ticket within the ITSM system to track the provisioning request. 3. Add you to the Okta group. 4. Confirm with you that the process is completed.