[Security Solution] [Serverless] User without privileges can see the Chat option on the Quality Dashboard

[MadameSheema]

Describe the bug:

• User without privileges can see the Chat option on the Quality Dashboard

Preconditions:

• To have a user with AI assistant set to none.
• To have a complete project
• To have indices with incompatibles fields

Steps to reproduce:

1. Navigate to Data quality dashboard
2. Click on Check all
3. On the index with incompatible fields, expand the dropdwon

Current behavior:

• The chat option is displayed

Expected behavior:

• The chat option should not be displayed

Additional information:

• The behavior should be fixed on ESS as well if present.

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)

[kapral18]

hey @MadameSheema the Chat has (correct me if I am wrong @andrew-goldstein) an upsell builtin for when no privilege or when on lower tier.

I additionally double checked with @dhru42 and the understanding is it's ok for us in DQD to show the button and allow it to handle the restrictions.

Additionally from what I noticed alerts page also exercises the same behavior, but correct me if I am wrong.

[MadameSheema]

Hey @kapral18 this was brought in one of the serverless testing parties that have been executed as well as per Kibana team, this is more about the UX rather than the functionality.

There are places where we don't allow the user to perform an action if they don't have the privileges, it would be great if we have a unified experience in the application, no idea who needs to take that decision :)

[kapral18]

hey @einatjacoby can you share your perspective on how to proceed with this UI from consistency perspective?

[kapral18]

@asnehalb can you please help get this unstuck? :) Thanks

[einatjacoby]

@kapral18 From what I recall, this was the decision on the designer side:
The button stays there, enabled,
but the assistant flyout displays a message about requiring an enterprise license

[kapral18]

Hey @MadameSheema I've discussed this with designers and the consensus is this change is not needed. Is this enough to close the ticket? If not let us know who else should we discuss this with? Thanks. cc: @asnehalb