Security and access boundaries
Understand account verification, workspace authorization, encrypted credentials, and audit history.
Account boundary
Every new Tnion.SH account requires email confirmation before it can receive a session. Password reset does not activate an account, and OAuth provider verification does not replace the Tnion.SH confirmation link.
Sessions are host-only application credentials. Sign out on shared devices and do not share activation, reset, invitation, or session links.
Workspace boundary
Workspace membership scopes access to servers, projects, instances, repositories, and activity. Owner, admin, and member roles establish increasing permission levels, while mutating infrastructure operations require a manager role.
Keep membership current and grant admin only to people responsible for operations. Platform-wide administration is separate from workspace roles.
Server credential boundary
Stored server passwords are encrypted at rest with AES-256-GCM using the platform deployment key and a fresh nonce. Normal API responses do not return the stored password.
The connection test is read-only and reports the SSH host-key fingerprint. Provisioning and instance actions use a separate mutating connection. Confirm fingerprints through a trusted channel and use a dedicated deployment account with controlled privileges.
Repository boundary
The GitHub App installation belongs to a workspace and can see only repositories granted through GitHub. Deployment tokens are short-lived and are not left in the repository remote configuration or deployment output.
Signing in with GitHub does not install the workspace GitHub App. These are separate authorization boundaries.
Customer responsibilities
Tnion.SH does not own your VPS provider, domain registrar, GitHub organization, Odoo Enterprise license, or external backup storage. Your organization remains responsible for:
- Provider ownership, billing, recovery, and region selection.
- Operating-system patching and network policy.
- Deployment-account privileges and credential rotation.
- Domain and DNS correctness.
- Repository review, licensing, and release approval.
- Off-host backup retention and recovery exercises.
Use workspace activity alongside provider, GitHub, and organizational audit records when investigating a change.