Complete SSO approval
After installing the app, GitHub may require SSO approval for the org.
Ask an org admin to approve ReleaseMind in the SSO settings.
SSO approval is required even if you already selected the repos.
Confirm access in GitHub
Return to GitHub and confirm ReleaseMind shows as SSO authorized.
If approval expires, GitHub will prompt you to reauthorize.
Confirm access in ReleaseMind
Return to ReleaseMind and refresh your repo list.
If you still see auth loops, log out and sign in again.
If approvals keep looping
Clear cached sessions in your browser and retry the sign-in flow.
Try a private window to confirm the issue is not a stale cookie.
Contact support with the redirect URL if the loop persists.
Review and introspect
SSO issues are often organizational, not technical.
- Which admin owns SSO approvals for ReleaseMind?
- Do you have a process for reauthorizing after org-wide SSO changes?
- Are users aware that SSO can hide repos until approved?