Configure Access Groups
What is Access Groups?
Moveworks Group Access enables users to self-service the management of distribution list (DL), also known as email groups.
Groups Access is composed of these key features:
- Create and manage email groups
- Add yourself or others to email groups
- Remove yourself or others from email groups
Learn more about group access here : Group Access
Overview of the Access Groups module
This module enables you to configure the behavior of the 'access group' skill. The access account configuration is primarily divided into two parts:
-
Configuring Ingestion: This involves setting up the process to intake groups from an external system and then feed them into the internal system.
-
Managing the Provisioning System: This includes the following subtasks:
- Selection: Choose a provisioning system that will execute necessary actions.
- Group Action Settings Creation: Draft the configuration for actions related to group management.
- Addition to Group Action Settings: Enhance the existing group action settings by adding new configurations.
- Removal from Group Action Settings: Update the group action settings by taking out redundant or unnecessary configurations.
This structure allows for a more organized and straightforward approach to managing access.
![](https://files.readme.io/9b298c7-Screenshot_2024-01-25_at_4.12.57_PM.png)
Configuring Access Groups
Ingestion
This configuration enables a connection between Moveworks and your external Identity and Access Management (IDAM) system, where your user groups are located.
- In the section Set Up System for Group Ingestion, you are required to specify the system where your user groups reside.
- Click "Add" to incorporate a new system. In this section, you can define the following:
- Ingest Attributes: These are attributes from your external system. Here, you need to list down the attributes you wish to ingest, such as 'distinguishedName'.
- Select System: Choose the IDAM system connector.
- Group Filters: Insert the filters here to fine-tune the groups being ingested from the external system.
- These filters can be established in two ways:
- Group Email Filter: Input the emails to be excluded. Incase for group based email filters these groups are still ingested under moveworks but aren't actionable. The bot will reply with "sorry, I can't help with this group" if this group is referenced.
- Rule-Based Filter: Employ Domain Specific Languages (DSLs) to filter out emails to be excluded. Learn more about this writing this DSL rule here :
- These filters can be established in two ways:
- Configure General Settings:
- Choose Joining Key: If identical groups are being ingested from multiple systems, you need to select the joining key. This is typically necessary when you're dealing with multiple Microsoft systems such as Active Directory (AD) and Exchange Online. By default, 'Email' is selected.
- Set Up Common Filters: These are universal group filters, and setting them up follows the same process as the system-specific group filters.
Manage provisioning system
Selecting Provisioning system
In this section you have to select which integrations can be used to provision access group skill.
- Click on the Add button to add a new integration.
- Select the system.
- Provide the post provision URL : This is you portal link that will be shown to user if the user is added to the access group. This a non-mandatory field.
- Select if you want to use this integration for DL creation : Only one system will be used for this action. If multiple systems are selected the skill action might fail.
Create DL action settings
In this section you have enable the settings for create DL action skill and select the moveworks approval model it will follow.
- Select if you want the user to provide description while creation DL action. This context will be recorded in the resultant ticket getting created.
- Select the moveworks approval model to follow. To learn more on native approvals click here : Moveworks native approvals . For adding a custom approval model also refer to this documentation.
- DL validation JSON payload : This is a advance setting which will enable validations while a DL is created and also enable you to add a pre-fix or change the domain. Refer to the JSON bender documentation for more examples here :
Add user to DL settings
In this section you have enable to settings for Add to DL action skill and select the moveworks approval model it will follow.
- Select the moveworks approval model to follow. To learn more on native approvals click here : Moveworks native approvals . For adding a custom approval model also refer to this documentation.
- Select to hide details on group add : Enable this to hide DL request details from the user e.g. 'you can now receive emails from [email protected]'. Recommended to leave this off.
Remove user from DL settings
In this section you have to enable setting for removing users from DL. These action is only supported into the following integrations.
- G-suite
- Active Directory
Here you have to select :
- Select the moveworks approval model to follow. To learn more on native approvals click here : Moveworks native approvals . For adding a custom approval model also refer to this documentation.
How to guides
How do I enable the create DL skill/ Add user to DL skill/ Remove user from DL skill ?
Plugin controls can be used to enable or disable a skill.
- Navigate to the advanced configs and go through the available plugin controls.
- Enable the plugin for the respective skill using the plugin control.
How do I select the approval model for the create DL skill/ Add user to DL skill/ Remove user from DL skill ?
- Navigate to the sub-section for the each skill.
- Select the approval model that skill will follow.
Updated 12 days ago