Users & security
Dockyrd has team accounts, roles and two-factor sign-in from the first release.
Roles
| Permission | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| View everything except secrets | ✓ | ✓ | ✓ | ✓ |
| Reveal secrets | ✓ | ✓ | ✓ | – |
| Deploy, restart, view logs | ✓ | ✓ | ✓ | – |
| Create and delete services | ✓ | ✓ | ✓ | – |
| Domains, GitHub, instance settings | ✓ | ✓ | – | – |
| Invite users and change roles | ✓ | ✓ | – | – |
| Transfer ownership | ✓ | – | – | – |
Sign-in
- Passwords are hashed with argon2id.
- TOTP two-factor with ten recovery codes. The owner can require it for everyone.
- Optional GitHub sign-in through your GitHub App. It links to existing accounts; it never creates one without an invite.
- Sign-in attempts are rate-limited per IP and per account.
Secrets and isolation
- Variables, database passwords, S3 keys and the GitHub App key are encrypted with AES-256-GCM.
- User containers never get the Docker socket and run with
no-new-privilegesand a memory limit. - Projects cannot reach each other's networks.
- Every change is written to the audit log with user, target and IP.
Reporting a vulnerability
Please report security issues privately as described in SECURITY.md in the repository. We follow a 90-day disclosure policy.