Git Security Overview

Capable lets Confluence users display Git content while respecting each viewer’s existing repository permissions. Users connect their own Git account, and content is only shown when that user has access.

#How access works

Each user connects their own Git account. Capable uses that user’s existing permissions when showing repository content.
There are no shared accounts or service tokens that grant extra access.
If a user cannot access a repository in Git, they will not be able to view it in Confluence.

#Using multiple accounts

Users can connect more than one Git account, such as work and personal accounts.
The selected account controls which repositories and files Capable can display.

#Organization access

Some organizations require an owner or admin to approve third-party app access before repositories can be shown.
After approval, each user still needs their own Git access to the repository.

#What viewers see

If the viewer has access, the Git content renders in Confluence.
If they are not signed in, they are prompted to connect their Git account.
If they do not have repository access, the page still loads but the Git content is restricted.

#Troubleshooting

Prompted to connect? Sign in with the Git account that has repository access.
Repository missing? Check that the account has access and that any required organization approval is complete.
Access error? Request repository access from the repo owner, then refresh the page.