16.01.2026
10:45
Hello!
How can I prevent, in Webcon, that despite the existing permission structure, all users are able to see and receive suggestions for all instances in the applications they have access to via "Analysis" -> "Suggestions" at the top level (see screenshot)?
16.01.2026
15:51
Hi Celina,
Suggestions' visibility depends on privileges. A user will only see instances to which they have privileges.
Also, this data is not taken from a SQL database, but from a Solr index, which is updated asynchronously (in case of some specific actions it is not updated at all: see https://community.webcon.com/forum/thread/5383?page=1 ).
Based on the above, I'd assume two possibilities:
- the permission structure is too wide and user's have access to instances they shouldn't see
- data in Solr is not up to date (example scenario: a group of users was granted process-wide permission, the Solr index was manually updated, then the the permission was revoked, but this time index was not updated).
This could be easily checked by clicking on a suggestion - if a user can open it, then they have permissions; if they cannot ("Access to the selected workflow instance is denied!"), then Solr index is not up to date and stores security tokens that no longer exist.
An easy solution in such case is to enqueue "Clear and reindex process or entire database" task in SOLR indexer queue (https://docs.webcon.com/docs/2026R1/Studio/Reports/Reports_Basics/Reports_SOLRIndexerQueue#6-add ).
Last, but not least, due to low usefulness of "Suggested" report, some customers hide the navigation button using global CSS styles :)
Hope you found above information useful and will be able to solve your issue.
