Claude Agent for Jira: project-level restriction and per-project GitHub repo mapping?

[Goekhan Sel]

Can Claude Agent for Jira be restricted to specific Jira projects only, and can GitHub repository access be mapped per project? Or is the configuration only site-wide with one shared Anthropic API key and one shared GitHub PAT?

[Marc -Devoteam-]

Hi @Goekhan Sel 

To my knowledge the access the agents has depends on the token used, so if the toekn is based on an admin user in Jria, they can see all if this is based on your user or a service account it depends on the permission this account has and what spaces it can interact with.

I suspect the same applies in Git?

[Goekhan Sel]

Thanks — but that only works if one token is limited to one repo/project scope. What do you do when different Jira projects should work with different GitHub repositories, and teams must not be able to use the same shared setup across unrelated projects? For enterprise governance, we would need a clearer separation model.

[Marc -Devoteam-]

Hi @Goekhan Sel 

That would. e a question to ask to Git.

Permission on what a user can do via AIU in Atlassian are based on their Atlassian permisisons.

Git project/repos are linked to Atlassian projects, but permissions on repo/project permissions are handled there, not by Atlassian or Claude.

[Goekhan Sel]

Thanks — understood. If that’s the case, then the key question is whether each Jira project can have its own dedicated Claude API key and GitHub token/connection. If not, it’s hard to see how this could meet enterprise governance requirements.