
ChrisR.96969 (Customer) asked a question.
We are trying to standardize and automate some of our Resource Set provisioning in Okta. There is no way to create dynamic resource sets with a designation such as "myorg.suborg.*" or similar so that *any* application or group or any other Okta object that follows that naming convention will be automatically placed into that Resource Set.
This would also help us greatly with some reporting requirements as you can imaging.
Our alternative approach is to run a cron job or similar job to automatically place applications or groups with specific "tags" or meta data into the appropriate resource set. This would be MUCH cleaner than relying on standard naming convention for Okta objects and would also allow us to apply this retroactively to long existing groups and applications by simply adding tags to those objects rather than having to rename them.
I do not see any way via UI or indeed even vs the API to add tags or other classification data of any kind, which seems odd to me for any SAAS solution that deals with hierarchical structures. (groups, resource sets, users, apps, etc).
Does anyone know of a way to apply tags/metadata to objects in Okta to achieve this?

Hello @ChrisR.96969 (Customer) Thank you for reacting out to our Community!
At this time Okta does have this type of functionality. You could use group rules where users can be assigned to groups/apps based on attributes/group membership for this please see our doc below:
https://help.okta.com/en-us/content/topics/users-groups-profiles/usgp-about-group-rules.htm
You can always add a Feature Request on our Idea section, for a chance that this functionality to be added in the future.
https://support.okta.com/help/s/ideas
Community members help others by clicking Like or Select as Best on responses. Try it today.
What you missed: new product releases and other announcements
@Paul S. (Okta, Inc.) This is completely not the question/function I asked about.
Hello @ChrisR.96969 (Customer), unfortunately the functionality you are looking for does not exist on Okta's end. We recommend to submit a feature request for such functionality.