Skip to content

PostHog lets admins revoke anyone's personal API key

Organisation admins can now roll or permanently revoke a teammate's personal API key from the Security page, with the change logged and the key owner emailed.

Source: PostHog

PostHog shipped a change on 16 November that lets organisation admins manage personal API keys centrally. Previously, a personal API key belonged entirely to the person who created it: nobody else could see it, rotate it or kill it if it leaked.

Now an admin can roll or permanently revoke any teammate’s personal API key from the organisation’s Security page. Every change is logged, and the key’s owner gets an email when it happens, so revocation isn’t silent.

Why it matters: personal API keys are exactly the kind of credential that ends up pasted into a script, committed by mistake, or still active long after someone leaves a team. Before this, dealing with a leaked key meant waiting on its owner or asking them to rotate it themselves. Now it’s an admin action with an audit trail, which is the difference between a credential incident taking minutes to contain versus hours.

The caveat: this only covers personal API keys inside PostHog’s own Security page. It doesn’t do anything about where those keys end up once they’re copied out, so the usual secret-scanning hygiene still applies.

Share

More from The Wire

All briefs