Required permissions

Required permissions for integrating GitHub Enterprise with Xopero ONE and protecting its resources.

Connecting GitHub Enterprise with Xopero ONE requires appropriate permissions to access and protect repositories and their associated metadata. The required permissions depend on the type of data that needs to be protected.

---

General permissions

Xopero ONE supports backup and restore for GitHub Enterprise Cloud deployments that are separated from the main GitHub environment (for example, your-org.ghe.com). You can integrate isolated GitHub Enterprise Cloud instances as GitHub Enterprise Cloud with Data Residency.

Integrating GitHub with Xopero ONE to back up and restore repositories, projects, and associated metadata requires an account with full administrative privileges.

To authenticate and access your account, Xopero ONE requires the following permission scopes:

• Personal user data (read-only): access to email addresses and profile information.

• Repositories: access to both public and private repositories.

• Code and resources: access to issues, pull requests, wikis, settings, webhooks and services, deploy keys, collaboration invites, and workflow management (including updating GitHub Actions workflow files).

---

Permissions for personal access tokens (PAT)

Personal access tokens are generated in GitHub Enterprise account settings under Tokens and can be assigned different permissions.

Registering the Xopero ONE application and executing full repository backup and restore tasks requires a token configured with at least repo and workflow permissions.

With minimal privileges, certain metadata may not be included in the backup. Select the permissions based on the specific data you need to protect.

---

Useful links and items

Managing your personal access tokens - GitHub DocsGitHub Docs