Offboarding a teammate
When someone leaves the team, revoke their access and rotate whatever they could read.

Revoke and rotate in one step
Section titled “Revoke and rotate in one step”murk circle revoke carol --rotateThis removes carol as a recipient, re-encrypts the shared secrets she had
access to without her key, and, with --rotate, prompts you for a new
value for each of them in the same session. Commit and push the result:
git commit -am "revoke carol, rotate secrets" && git pushWithout --rotate on an interactive terminal, murk circle revoke offers to
rotate anyway; run non-interactively (e.g. in a script) it just prints a
hint instead.
Import rotated values from a file
Section titled “Import rotated values from a file”If you already have replacement values staged in a file, revoke first and bulk-import instead of answering prompts one at a time:
murk circle revoke carolmurk import .env.rotatedWhy rotation matters
Section titled “Why rotation matters”Revocation re-encrypts the vault going forward: carol’s key is dropped from future shared-secret ciphertexts. It does not touch git history:
So always rotate after revoking someone whose access mattered. murk circle revoke --rotate does both in one motion; if you skip --rotate, follow up
with murk rotate KEY (or murk rotate --all) for anything sensitive they
could read.
Checking what needs rotating
Section titled “Checking what needs rotating”murk rotate --list # keys needing rotation: overdue, expiring, post-revokemurk rotate --list --jsonThis flags secrets that are overdue for rotation, approaching an expiry, or
still outstanding after a past revoke (useful as a periodic hygiene check
independent of any single offboarding event). See murk doctor for broader
repo hygiene scanning, and the CLI reference
for the full flag surface on circle revoke and rotate.
For adding and authorizing teammates in the first place, see working in teams.