Okta Groups suppor for Creator Studio Workflow Access

Hi Andrew! Currently the launch options in Creator Studio support using a Moveworks DSL Rule to launch your use case (reference: https://developer.moveworks.com/creator-studio/administration/launch-options/#4-launch-to-users-matching-the-rule).

The rules can be written based on data on the Moveworks profile, which can be mapped from the user’s Okta Profile. 

So if you can run a job or automation that calls this API (https://developer.okta.com/docs/api/openapi/okta-management/management/tag/Group/#tag/Group/operation/listGroupUsers), and the updates the user’s Okta profiles with an attribute, then Moveworks can key off of that attribute in the launch option.

Hey @neal , 

Thanks for sharing that info, and sorry for the delay.   For a few reasons, the team that runs our identity and auth prefers we use Okta groups for items like this.  Is there a way to officially request group support as a feature? 

Happy to chat about it more if that will help. 

Thank you! 

Hey @onlyawave,

The request definitely makes sense and it’s something that we want to support in the platform one day.

Currently, making an external API call while the Copilot is deciding what plugins to select would hurt the ability of the Copilot to do effective reasoning & planning. 

We will continue to think about how to approach this with our engineers, but we don’t have a game plan just yet.

This is good feature to have. To avoid an external API call, Can Moveworks ingest user’s associated OKTA groups as well during SSO/AD sync? So that these groups will be referred via DSL?