Required Permissions For GitHub Users And Token

Account

The permissions the app needs to log into your account:

• Personal user data (email addresses - read-only and profile information -read-only)

• Repositories (public and private)

• Code (include: issues, pull requests, wikis, settings, webhooks, and services, deploy keys, collaboration invites, learn more, workflow, update GitHub Action Workflow files).

Permission type	Permission level	Possibilities
Owner	default	Full backup and restore.
	admin	Full backup and restore.
	write	Full backup and restore.
	read	Full backup. Restore only to your own account.
Member	admin	Full backup. Restore only to your own account.
	maintain	Full backup. Restore only to your own account.
	write	Full backup. Restore only to your own account.
	triage	Backup excluding collaborators. Restore only to your own account.
Collaborator (external in the organization)	read	Backup excluding collaborators. Restore only to your own account.
Collaborator (from outside the organization)	default	Backup excluding collaborators. Restore only to your own account.

Personal Access Token

The minimum permission of authorization for the token used, which is required to register the GitProtect application and perform repository backup/restore, is a repo.

You can generate a Personal Access Token by going to the tokens tab on your GitHub account:

GitHubGitHub

With minimal privileges, some metadata may not be included during the backup process. Choose the list of necessary permissions, depending on what data you need to protect.