We should be able to limit a user action to the app scopes

[blanchonvincent]

Problem

We would like to create a user action that is restricted to the users that have registered to specific app(s).

Solution

We could add a the list of the apps with checkbox

This action will be displayed only to the user that are registered to the app we have checked.

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

[robotdan]

To clarify, the User Action is scoped to an application at the time it is applied. You would like to create the User action as scoped to a particular application(s) ahead of time such that it may ever only be applied to the pre-determined applications?

[blanchonvincent]

To clarify, the User Action is scoped to an application at the time it is applied
I am not sure to understand that. Where in FusionAuth can we scope a user action to an application?

[robotdan]

Hi @blanchonvincent sorry for the delay, this one fell under the radar.

When the action is taken on a user, an Application can be specified with the exception of an action that restricts login. For example, in the attached screenshot, I am taking an action on a user, and selecting just one application.

Will this satisfy your requirement? Or are you asking to create the action with a pre-determined, one or more applications that the action can ever be taken on?

[blanchonvincent]

Or are you asking to create the action with a pre-determined, one or more applications that the action can ever be taken on?

yes exactly.

Let's say I have three app, X, Y and Z.
When I create the action "Mute", I will say (during the creation) that this action can be taken on user that have subscribed the app X or Z.

So if I go to the profile of the user A that subscribe app X, Y, I can use this action on him.
If I go to the profile of the user B that subscribe app Y, I cannot use this action on him.

[robotdan]

Ok, thanks @blanchonvincent for that additional context, I understand the feature request.