AdminA.37568 (Customer) asked a question.
How to read user's groups and list custom attributes from the information
Hi,
My company is using custom attributes for group profiles. I would like to create a workflow that retrieves users' groups and lists certain custom attributes and sends that information to the user as a list via Slack message. The idea is to give an insight to the users of which kind of applications they are using each month.
I have tried to use the Okta action get user's groups, but this action does not seem to work with custom attributes. Would anyone happen to have an idea how to be able to list all the custom attributes and send them to the user?
So there are two ways of looking at your problem (from my point of view). You select the group(s) you want to evaluate memberships of and then read each user, or you look at users and then their group memberships. The former makes sense if you have fewer groups you care about for the above purpose, but I wanted to suggest as a potential option not knowing too much about your org.
Beyond that, assuming you want to read each user's group memberships, then I can only assume you are leveraging the "Get Users Groups" card and carrying out your intent beyond that. At some point you would know the user's ID to be able to read their group memberships, and thus, I would leverage that information for a "Read User" card where you can then extract the custom attributes you want.
If we could see an image of the flow that would help me better understand where we might want to suggest you place it as well, but seems to be your best option at this point. Thanks much! Hope this helps.
Thanks Don, I agree with your point of view. In my case I would like to send each user a monthly report of all of their groups as a list and also list some custom attributes from each group. So I approach it by running a helper flow individually for each user. I can very easily get each user's groups and send that list out to them as a list, but this only works with general attributes such as group name and description. Cannot get custom attributes to work the same way for some reason. I think this might a feature limitation but also interested to hear if anyone has a workaround for this. This sounds like quite a basic thing that a lot of organisations would like to do yet it seems to be surprisingly complex.
I am a bit confused by the use case.
When you are saying "certain custom attributes" are you talking about custom "Group" attributes?
Those are a schema change that make the properties able to be leveraged by any Okta group and the values of those properties are per group not per user. Those properties can definitely be pulled with the "Read Group" card (as long as you define the output which won't be selected by default) or using Custom API Action which will return the full profile object and values for the specified group (GET /api/v1/groups/${groupId} )