- Products & services Products & services
- Resources ResourcesCustomer resources
- Customer resources
- Customer support Find more information about engaging support and get help
- Services guide Find more information about working with Services teams
- Free resources Leverage our free tools and trainings
- Modernize to Identity Security Cloud Transition to the cloud for advanced capabilities and a future-ready security posture
Learning- Learning
- Identity University Get technical training to ensure a successful implementation
- SailPoint professional certifications & credentials Advance your career or validate your identity security knowledge
- SailPoint recertification program Get recertified by demonstrating ongoing learning
- Training onboarding guide Make of the most of training with our step-by-step guide
- Training FAQs Find answers to common training questions
- Community Community
- Compass
- :
- Discuss
- :
- User Groups
- :
- Identity University - Identity Security Cloud
- :
- Forum
- :
- Re: Enabling - Natural Language Query
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content to Moderator
Enabling - Natural Language Query
We are exploring the possibility of enabling Natural Language Query (NLQ) capabilities within our Identity Governance & Administration (IGA) platform to improve the search experience for administrators, auditors, managers, and business users.
We're interested in understanding:
- What capabilities or components would need to be developed or enhanced to support NLQ effectively?
- What are the key technical considerations (search indexing, AI/LLM integration, metadata enrichment, observability, etc.)?
- What challenges have you encountered when implementing NLQ in identity or governance platforms?
- What business value or operational benefits have you observed from enabling natural language search?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content to Moderator
Hi @athuljs You posted this inquiry in the Identity University forum, and we use this forum to discuss Identity University courses and education services typically.
I am answering here, but if you seek additional community input, I recommend posting in the Identity Security Cloud forum.
- With the native, integrated Natural Language Search capability in ISC, there is nothing to configure. Simply toggle it ON in Admin > Global > Feature Settings > GenAI options.
- I haven't noticed any technical considerations, as far as indexing, speed of query, etc. It operates just as fast as the Search query. I also haven't noticed bubbling up metadata in my own personal usage of it. I would say that the application of it in the tenant structure is "fixed."
- The same considerations for any AI/LLM/GenAI solution apply here: You ALWAYS want to verify the data you see in the result set of the query. Sometimes it does not devise the right query, which is why it is important to toggle field to QUERY to investigate the query syntax.
- The business value to Natural Language Search is definitely felt for those who don't feel as confident with their Elastic Search query skills OR may be new to the organization and don't have granular details about the identity population or access model yet (i.e. when using in Identity Graph). Again, it it important to verify the search query and results, which can be challenging without any Search query skills. So, it is still recommended to have a base line knowledge of Search when using Natural Language Search.
I hope you find this helpful!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Content to Moderator
@athuljs, NLQ (implemented in Identity Security Cloud Admin as Natural Language Search) is available in the user interface - you only need to enable it as shown in the attached screen capture and can read more details about using it here.
Regarding key technical considerations, because it's a SaaS application, items like the ones you mentioned are taken care of on the backend in the ISC tenant.
Since I'm not in the field, I haven't experienced any challenges with it. And In terms of business value, I'd expect it to save a lot of time and effort!
