posthog-enterprise-rbac
PostHog enterprise access control: organization/project hierarchy, member roles, scoped API keys, SSO/SAML configuration, and activity audit logging. "posthog roles", "posthog permissions", "posthog SAML", "posthog access". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-enterprise-rbac --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PostHog Enterprise RBAC ## Overview PostHog access control uses a three-level hierarchy: Organization > Project > Resource. Organizations contain multiple projects (e.g., production, staging), and each project has its own data, feature flags, and dashboards. Members are assigned roles at the organization level and can be restricted to specific projects. ## Prerequisites - PostHog Cloud or self-h
What does the posthog-enterprise-rbac skill do?
PostHog enterprise access control: organization/project hierarchy, member roles, scoped API keys, SSO/SAML configuration, and activity audit logging. "posthog roles", "posthog permissions", "posthog SAML", "posthog access". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-enterprise-rbac --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.