Access to App from Connectors

Hello, I am reaching out to request your help with ticketing connector access for a member of our team in Amazon Quick.

Issue: The team member currently cannot see one of the application connector in their Connectors view at all, while others still can see. They need full access to the ticketing integration to perform their work.

Do you know how to add the application in order to connect? If not, do you have any POC for this issue?

Hi,

As far as i know, When a connector is completely absent from one person’s Connectors view while colleagues still see it, it’s almost always one of a few things — here’s how to narrow it down:

1. Have them check “Browse all” first (most common - Desktop). A connector usually has to be installed before it appears in the Connectors list. Ask the team member to open Customize → Connectors → Browse all and look for the ticketing integration there. If it’s listed, they just need to Install it, then Sign in on its row. If colleagues installed it and they didn’t, that alone explains why it’s missing for them.

2. Admin / group access policy (most likely if it’s not even in “Browse all”). If the connector doesn’t appear even under Browse all, it’s likely restricted at the account/admin level — connector availability can be scoped to specific users or groups. In that case the person needs to be added to the group that’s been granted the ticketing connector. This is an admin action (Manage Quick / admin console), not something they can self-serve.

3. Confirm they’re on the same surface. Availability can differ by surface and rollout. Make sure they’re checking from the same client the others use (e.g. desktop app vs. web) — if the integration is a local/desktop connector, it only shows while their connected desktop is online.

Fastest way to verify:

  • Ask them to look in Customize → Connectors → Browse all:
    • It’s there → Install + Sign in; done.
    • It’s not there → it’s an admin/group-scoping issue — we’ll need an admin to grant their user/group access to the ticketing connector.

Hope this helps narrow down the issue

Cheers,

Deep