Reducing scope of what Teamwork Graph can access using Zendesk connector

[Michael Smith]

Hi,

I'd like Rovo to be able to search Zendesk knowledge base articles but not access tickets. How can I control the scope that's requested when connecting Zendesk to Teamwork Graph following this guide: https://support.atlassian.com/organization-administration/docs/connect-zendesk-to-teamwork-graph/

The connector asks for read access to everything, but I don't want Rovo to ingest our support ticket contents.

When authorizing the connection, I tried changing the URL on the Zendesk approval site to change the scopes to:

 hc%3Aread%20webhooks%3Aread%20webhooks%3Awrite

It worked on the Zendesk side, and I was able to see it issued a token with the scopes I wanted, but the Atlassian side displayed a generic message like "Error authorizing OAuth".

Also, why does it request webhook write access?

[Gabriela]

Hi @Michael Smith,

Gor's right that the connector uses a fixed OAuth scope set, which is exactly why editing the scopes on the authorize screen throws "Error authorizing OAuth." There's no Atlassian-side toggle to index articles but skip tickets. The lever sits on the Zendesk end. Teamwork Graph only ingests what the connecting identity can read, so complete the connection as an agent whose Zendesk custom role has Help Center/Guide article access but no ticket permissions, and tickets never enter the graph. The webhook write is what registers the change subscription so the index stays current instead of re-crawling your whole Zendesk API.

Connect Zendesk to Teamwork Graph

[Gor Greyan]

Hi @Michael Smith

Welcome to the Atlassian Community!

As far as I'm aware, the Teamwork Graph Zendesk connector currently requests a predefined set of OAuth scopes, and I haven't come across any documentation indicating that those scopes can be customized during the authorization process.

If your goal is to allow Rovo to search only Zendesk Guide articles without indexing support tickets, I'd be interested to know whether Atlassian supports that level of granularity. It may be worth hearing from the Teamwork Graph or Rovo team, as they could clarify whether more fine-grained scope selection is on the roadmap.

I'm also curious about the requirement for the webhook-write scope. Hopefully someone from Atlassian can explain why it's needed for the connector.