How to restrict supplier/vendor access in Agile from viewing Global Searches?

Today my organization have several vendors accessing into our Agile PLM with limited privileges (Read/Modify certain attributes in a change object only) but they can still able to view Global Searches.
Is there a way ‘hide’ Global searches and its folders from the external users (supplier/vendor)?
Please advise?
Thanks.

Add Comment
4 Answer(s)

Adriex, I am not aware of any way to limit this view.  Do you have concerns that the Discovery privileges cannot manage for you?  Search names, etc…

Agile Angel Answered on October 26, 2015.
Add Comment

Adriex –
This is an interesting question, and I can definately think of some reasons that you may not even want suppliers to see the names of some Global searches. 
After doing some digging – I have found that you can make additions to the “Sear

Agile Angel Answered on October 29, 2015.

Can you update your answer?  What did you find?

on October 30, 2015.
Add Comment

Sorry about that – hopefully this bug has been fixed and will post my full answer.
The short answer is that you cannot set limits to as to who has access to the searches in the OOB Global Search folder.  As Patrick pointed out – you can put restrictions on the search results using appropriate Discovery privileges, but you can’t limit the Global Searches themselves.

My  thought as a potential work-around was to try and create a second Global-ish search folder to house any Saved Searches that you wouldn’t want suppliers to see.
I have found that additional values can be added to the system “Searches List” and those new values can then be assigned to a User’s ‘Searches’ property.  This, unfortunately doesn’t seem to have any impact, as of yet, in making any new search folders available.  It is possible that something may also need to be added on the server level as well in order for this to work, or perhaps it is a design flaw and these edits shouldn’t actually be allowed.  I haven’t had time to take it to that level yet, but probably will at some point to satisfy my own curiosity.

In the meantime – I would suggest renaming any sensitive global searches and/or using the Discovery privilege to limit the objects returned for Supplier accounts.

Agile Angel Answered on November 11, 2015.
Add Comment

So sorry folks it took so long to be back here!!
Thanks a lot for the inputs and feedback on this matter.
Well, till today it is not able to restrict . It is dependent on User Profile’s setting by ‘Searches’ and Role.
If we allow external users to access the Agile, then any sensitive information/searches created should be move into specific searches type for internal users or just removed if not needed. 
Internal users by functional group or department can create their own personal searches or we Search access like “Component Engineer” and “Change Analyst” searches.

So keep it to bare minimum on what we put into Global Searches if we have external users accessing the system.

Agile User Answered on June 15, 2017.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.