Skip to content

Custom chat agent not visible to team members in the Quick Suite Extension

0

I created a custom chat agent for our team’s investigation project. My colleague can access other teams’ custom agents in her Quick Suite browser extension, but she cannot see mine in the agent list. She can only access my agent through a direct share link, but we need it visible in the browser extension on every tab for our workflow. I’ve verified sharing settings and she has the same permissions as others who can see different custom agents. Why is my agent not appearing in her extension when other shared agents do? What configuration am I missing to make it discoverable like the others?

asked 8 months ago190 views

1 Answer
1
Accepted Answer

The issue you're experiencing with your custom chat agent not appearing in your colleague's Quick Suite browser extension could be related to several factors:

  1. Regional Availability: Amazon Quick Suite's AI-powered features, including Chat Agents, are currently only available in specific AWS regions: US East (N. Virginia), US West (Oregon), Europe (Dublin), and Asia Pacific (Sydney). If your account or your colleague's account is using a different region, this could explain why the chat agent isn't appearing consistently.

  2. Account-Level Restrictions: There might be account-level restrictions in place. When Chat Agents are disabled at the account level, the Chat Agents option is removed from the navigation panel, and all custom chat agents within Quick Suite browser extensions become unavailable.

  3. Permission Settings: Even though you've verified sharing settings, there might be specific custom permissions applied at the user, role, or account level that are affecting visibility. In Quick Suite, user-level permissions override role-level permissions, which override account-level permissions. Your colleague might have specific user-level restrictions that prevent them from seeing your custom agent.

  4. Extension Configuration: The Quick Suite browser extension might need to be reconfigured or refreshed to recognize newly shared agents.

To resolve this issue:

  1. Confirm that both you and your colleague are using Quick Suite in one of the supported regions.
  2. Check if there are any account-level restrictions for Chat Agents.
  3. Review the custom permissions assigned to your colleague at all levels (user, role, and account).
  4. Have your colleague try refreshing or reinstalling the Quick Suite browser extension.
  5. Ensure that your custom agent is properly associated with the appropriate spaces or knowledge bases that your colleague has access to.

If the issue persists, you might need to contact AWS Support for further assistance, as there could be specific configuration details unique to your environment.
Sources
Quick Suite features not available on my account | AWS re:Post
Establishing enterprise governance in Amazon Quick Suite using custom permissions | AWS Business Intelligence Blog
Deploy Quick Suite Chat Agent to websites | AWS re:Post
Reimagine business intelligence: Amazon QuickSight evolves to Amazon Quick Suite | AWS Business Intelligence Blog

answered 8 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.