Limit application scopes available in application picker for non-admin user

[chanhe]

Hello,

Is there a way to limit the available application scopes showing/selectable from the application picker for a non-admin user who is given the ability to see/use the application picker using Delegated Developer ?

Specifically, the scenario is as follows:

1. We create a custom application "MyApp" to allow creation of scoped knowledge bases as an example.

2. "MyApp" is configured for application administration using the custom application role "myapp.admin"

3. Say we have a non-admin user, "User1" who normally is in the "security incident response" application scope (e.g., they have only the sn_si.analyst role).  Normally "User1" does not have the application picker and is always in the "security incident response" application scope.

4. If we allow "User1" to have the "myapp.admin" role and also set Delegated Developer (say to allow Tables/Forms) from the custom application then "User1" will have the application picker.  However, "User1" sees all the available application scopes including "MyApp".

It would be nice if we could limit the application scopes to just "security incident response", and "MyApp" to minimize any confusion resulting from inadvertently picking some other application scope.

Is this possible?

I've looked on the community site but didn't find (hopefully didn't miss) any question similar to this.

Regards,

Henry

[Alex Tod1 · Accepted solution]

Hi @chanhe,

  You could try to create an ACL with the read operation on the "sys_scope" table, more specific on "sys_scope.name" field, this way you could restrict the list in the picker application, probably you need more than that, to create special roles just for this.

[chanhe]

Thanks for the reply and suggestion Alex (especially with the table reference)!  I'll give it a try.

Best regards,

Henry