We're updating the issue view to help you get more done. 

Need role "action" to restrict "Add object" in Set items bundle


Use case is: an access role is created that prevents a user from doing anything in the database except opening up sets shared with their account. They can not search/browse the system.

Issue is: they can still search system contents via the "Add object" in Set items.

Can we add an action access role setting to remove this "Add object" segment of the Set items bundle?




User known
May 3, 2019, 3:41 PM

I changed the lookup across the board to honor the "can search" action. This means that if you don't have privs to search objects then any type-ahead that searches objects will now refuse to search. This would be in the set editor as well as in the various record editors. This seems reasonable to me. What do you think?

I've made the change in dev/locMerge only for now.

Julia Weist
May 7, 2019, 1:11 PM

This works well.

Julia Weist
May 22, 2019, 3:57 PM

As a result of this work admin roles are now getting "You do have access to search list items" in the lookup drop-down for Manage > Lists and Vocabularies > Search.

User known
May 22, 2019, 4:30 PM

On what system is this happening? I've tried a couple and they don't exhibit this behavior.

User known
May 22, 2019, 5:21 PM

It just needed a pull to current code. It works now!


User known


Julia Weist




Fix versions

Affects versions