Permissions, keys & secrets
Per-file encryption, policies, access, and the key hygiene that makes it survivable.
- How per-file permissions actually workEncryption at snapshot time, not a server check.
- Solo, Team or Enterprise: which tier am I on?The three crypto tiers, what changes between them, and what is actually shipping.
- Write your first policytovio policy set, and watching a file become ciphertext.
- Policy expressions: attributes, globs, read and writeThe real grammar, at the level you need to write one.
- Test a policy before you rely on ittovio policy test, offline.
- Give someone accesstovio access grant, and the one thing everyone assumes wrongly about it.
- Take access awaytovio access revoke, the commit it writes, and what revocation cannot undo.
- Check whether someone can read a pathtovio access check, the diagnostic behind most permission questions.
- Ask for access you do not havetovio access request.
- Where your keys liveThe wrapping-key model, and the rule that keeps secrets out of history.
- Back up your key todayThe five minutes that prevents the one unrecoverable failure.
- Rotate your keytovio key rotate, and what it re-wraps.
- I lost my keyWhat is recoverable, what is not, and where your recovery phrase probably already is.
- My key or certificate is expiringThe warning, and renewing before it bites.
- Add a new deviceThe two-sided pairing flow, the code you must actually compare, and revoking a lost one.
- Store a provider credential safelytovio config secret set, and why it only reads from a pipe.
- Move a repository from Solo to Teamtovio identity init — what it does, and the re-encryption it deliberately does not do.
- Secret scanningThe default-on plugin that catches credentials before they are committed.
- Read a permission error and act on itTVO-PERM-001 and TVO-PERM-002, line by line.
- Every tovio policy subcommandThe complete verified surface, and which ones you will actually use.
- Require signed commits and protected-ref updatestovio policy signing, and the flag name people guess wrong.
- Your policy manifest is unattestedTVO-SYNC-008, and the one-command fix.
- Require a justification for sensitive operationstovio policy audit, and the lockout it can cause.
- Keys on a headless or CI machineTOVIO_KEYSTORE_KEY, and the two failures it causes when you get it wrong.