Subscribing to Saved Searches

[Kurt_Ramsey]

Saved Searches:
- Are private (visible only to the creator)
- The public attribute was never implemented
- Ownership cannot be changed, even via API
- To disassociate search from a user, search has to be created/maintained via API by a non-human identity

If we have standard set of ‘subscriptions’ (saved searches) that we want for others to get access to, what are others doing to enable this for their teams?

The two options I have come up with, don’t work that well:

Option 1: Everyone is responsible for setting up their own search. This feels bad as it requires knowledge of the filter and of what attributes should be selected, which leads to inconsistency for those that need same information

Option 2: Searches are created via API upon request, owned by a non-individual account. Since there is not a direct means of subscribing to the search, we would use a distribution list/shared email. This however requires setting up a source where an Identity that exists for this specific purpose is created, so that it can be ‘subscribed’.

[sharvari (Sharvari Bharatiya)]

We had similar use case and decided to go with Option 2.

Option 2 is better to go with so the query is maintained centrally in one account so if any modifications etc needed in future, it’s easier to make change in one place rather than have everyone make changes on their side. You can create an Identity Now Admin specially for reporting and have all these queries saved under this account and then subscribe to them and mail it out to a DL/shared mailbox.

[edmarks]

We use Option 2 with nearly all the clients we work with also. Not a “great” solution, but provides a consolidated source. We have also had clients extend this to “Departmental” non-human ID’s so the department can create/modify their own reports vs. being dependent on IT to do this.