Support

A focused route to the answer you need.

Start with the connection, permission, or account choice that is closest to the problem. Branch Manager keeps the Git provider in control of provider-side access and repository behavior.

Start here

Three quick checks before you reconnect.

Most connection and visibility questions resolve at the Git provider boundary: the server URL, your credential scope, and the provider account that owns the resource.

Confirm the server

Make sure the selected GitHub, GitLab, or Gitea endpoint is reachable and is the server where the repository actually lives.

Check provider permissions

Your personal access token and provider membership determine which repositories and organizations Branch Manager can request.

Choose the right target

When creating a repository, select the personal account or organization that is available through that connected server.
Frequently asked questions

The practical details.

These answers describe Branch Manager’s current workflow and where the Git provider remains responsible.

Which Git providers can I connect?

Branch Manager supports GitHub, GitLab, and Gitea. A self-hosted GitLab or Gitea server needs a reachable HTTPS endpoint in production.

Why is an organization missing?

Organization choices depend on what the credential for that connected server can access. Check the token scope and your membership in the Git provider, then refresh the available choices in the product.

What permission should my personal access token have?

Use the least privilege that supports the repository actions you need. The exact provider scopes vary by GitHub, GitLab, or Gitea configuration, and the provider remains the authority for those permissions.

What happens if I delete a repository?

A guarded delete action sends the request to your selected Git provider. The provider controls deletion, recovery, retention, and audit behavior for that repository.

How do I delete my Branch Manager account?

Use the public account-deletion page after signing in. It removes the Branch Manager account and saved server connections, but does not change your Git-provider account, organizations, or repositories.

Account and connection removal

You can remove an individual server connection in the product. To close your full Branch Manager account and remove all saved connections, use the deliberate account-deletion flow after signing in.

Account deletion

Security and privacy guidance

Use a minimally scoped provider credential, rotate it with the provider if it may be exposed, and consult the product’s security and privacy pages for how saved connections are handled.

Direct support

Need help that is not answered above? Reach the Branch Manager team at branch-manager-support@cyberstreamstudios.app.