Integrations and AI · Taskending editorial team
GitHub sign-in versus repository integration
GitHub sign-in verifies identity. Repository integration requests access to development events. They use different permission scopes even with the same account.
Updated: · 1 min read
How to apply it
Use GitHub on the Taskending sign-in screen to authenticate. Link it to an existing account through personal connected-account preferences. Connect a company repository separately through authorized Git settings.
A concrete example
A team member may sign in with GitHub without being allowed to manage company Git integration. An administrator may see an existing company repository connection without linking their personal sign-in provider. The screens describe different scopes.
What to watch for
Successful sign-in does not automatically share private repositories. Read permissions in the context of the operation. Do not change company roles merely to make connection labels match.
How to check the outcome
Verify identity on the personal screen and repository/project mapping on the company screen. Sign-out/sign-in and webhook delivery are separate tests.
Try it in your own workflow.
Create a company workspace and your first issue. Taskending is currently free.
Start for free