I would like to be able to enter the name of a user group in a User-type relation to link automatically all members of the group.
What is the context for this?
Assuming that the membership of a user group might change over time, why do you want to link users to an entity based on a static snapshot at one moment in time?
Or am I missing the point?
Itâs a handy shortcut to gain some time when linking people to an entity.
Filling out attendees in a meeting? If they are all in user group (same team for instance), itâs super easy and the fact that the user group can evolve is not relevant in this case.
We use some entities to record âagreementsâ to certain document (like a watered down e-sign). The intended audience is a User relation that needs to be pre-filled by hand and it could so much easier with user groups.
Itâs not critical, just a small quality of life kind of feature ![]()
But the twin feature youâre alluding to (linking to a user group that stays in sync) would probably be interesting also
OK, gotcha. I guess we could improve the âsearchâ function so that it could search for specific entity properties (it currently searches only for Name and ID) so that when trying to select users, you would type a group name, and all users who belong to that group would show up.
And then the other functionality needed would be to bulk link based on the results from a specific âsearchâ.
![]()
I guess the current workaround is to add a relation to the user group database, and then have an automation that populates the user collection based on something being chosen for the group field.
For this use case, I might suggest replacing the user relation with a group relation, and then using a lookup field to get the users.
For this use case, I might suggest replacing the user relation with a group relation, and then using a lookup field to get the users.
Yeah, I was thinking the same ![]()