Skip to main content
Participating Frequently
May 2, 2024
4. Future Consideration

Ability to Group People for any skill/KB deployment

  • May 2, 2024
  • 8 replies
  • 34 views

It will be good if we have the ability to group users per need for example

  1. Sending campaign to a group of people only.
  2. Testing new bot skill or integration to a group of people (test people or UAT)
  3. Ability to NOT serve KB to a group of people, 
  4. etc.

8 replies

dluckadoo
Employee
May 13, 2024

Hi @ferdinand.codizal!

Thanks for your post. Today, Moveworks has the capability to limit who has access to resources and creator studio use cases using any ingested user values, such as department or location. Do you have a specific scenario where the OOTB filtering is not sufficient?

Dray

Dray
dluckadoo
Employee
May 13, 2024
1. New3. Existing Functionality/Native Skill
Dray
dluckadoo
Employee
May 13, 2024

I’m marking this as existing functionality for now, but let’s dig deeper into your request to make sure this is the case. Additionally, I can help you with configuring this for your specific use case.

Dray

Dray
Participating Frequently
May 15, 2024

Hi Dray,

But that is reliant on the user attributes. What I meant is to create a group inside MW setup and then use this group for the use case I mention. This way the admi has the control of all things not related to attributes

dluckadoo
Employee
May 15, 2024

Oh, I think I understand. You’re looking for Moveworks-native groups that can be leveraged for building rules? How would you envision defining these groups? Would it be a list of emails, or something different?

Dray

Dray
Participating Frequently
May 16, 2024

Yes, it can be an email or since we already have the ingested user. We can simply create native group and then have a button to add manually users either via email or searching using First name or last name. Similar to how we add user in AD groups

dluckadoo
Employee
May 22, 2024

Thank you for walking me through your concept! I agree this is not exactly existing functionality, so I will move this to future consideration.

Dray

Dray
dluckadoo
Employee
May 22, 2024
3. Existing Functionality/Native Skill4. Future Consideration
Dray