Runzivo runs GitHub Actions jobs for repositories owned by GitHub organizations, including GitHub Free organizations. It does not run jobs for repositories owned by a personal account, and it will not ask for the permission that would make that possible.
What the earlier guide said
The setup guide previously stated that personal-account repositories would need the GitHub App permission Administration: Read and write, and that support was planned. Runzivo withdraws that statement. The Runzivo GitHub Apps keep their current permissions.
Why Runzivo will not request it
GitHub only lets an app register a self-hosted runner on a personal repository if the app holds Administration: Read and write. There is no narrower option. That permission also lets an app change repository settings, branch protection, collaborators and deploy keys, and rename or archive a repository.
Runzivo does not need that level of control. Organizations can use organization-level runners, which need only the narrower Self-hosted runners organization permission. Adding Administration to the Runzivo App would also send a new permission request to every existing installation, including the organizations that never need it.
What this means for you
If your repository belongs to a personal account, create a free GitHub organization, move or fork the repository into it, and connect that organization to Runzivo. Your job then runs on an isolated Runzivo runner with the same permissions every organization uses.
The full list of permissions Runzivo requests, and what each one is for, is in the GitHub App permissions guide.