Authentication

Guardix supports GitHub and Google sign-in. Pick the option that matches how your organization manages identity.

GitHub

• Used for repository access when you connect private repos via the GitHub App.
• Your GitHub identity is linked to your Guardix account so permissions stay explicit.

Google

• Useful when your team standardizes on Google Workspace accounts.
• You can use Google-only sign-in; repository access still flows through GitHub when you connect code.

Sessions

• Sessions are designed to persist across browser restarts until you log out or a policy expires — you should not need to sign in on every visit.
• Always log out on shared machines.

Permissions

• Guardix only accesses repositories you explicitly connect or authorize through the GitHub App.
• Review org/repo access in GitHub’s settings if you need to narrow scope.

For connecting repos after sign-in, see Connecting repositories.

API keys (automation)

Interactive sign-in covers the dashboard. For scripts, CI, or direct HTTP calls, create an API key under User menu → API keys (/settings/api-keys). Keys use Authorization: Bearer <key> against the same /api/v1/... API the app uses. See API keys for details, examples, and security practices.