Organizations

Multiple organizations and projects aren't available on open source hobby deployments.

Organizations

An organization is the highest abstraction level within a PostHog instance. It's made up of projects (see more in the project settings guide) and members.

Most commonly a PostHog organization represents a real-world company or other type of isolated grouping.

Use the organization dropdown in the top bar to switch between organizations or create a new one.

PostHog Cloud users can create, manage, and join organizations without limits.

Organization members have different access levels based on their membership type. See more in our access control docs.

Adding new members

By default, any organization member can create and view organization invites. Admins and owners can restrict this by disabling Members can invite in organization settings – when disabled, only admins and owners can create and view invites. Members can only see invites at or below their own membership level. Invites are valid for 3 days after creation and only for the specified email. Emails can be resent by removing and re-adding the invitee.

In an email-enabled PostHog instance (including PostHog Cloud) the invite is sent automatically to the specified email. If the PostHog instance can't send emails, remember to share the invite link yourself.

If there's no account associated with that email, the invited person will have to create an account. Otherwise, they'll be able to join with their existing account.

If you sign up with an email that has a pending invite, PostHog automatically detects it and shows the inviting organization's name with an option to resend the invite email. You can skip this and create your own organization instead.

If you already have an account, pending invites for your email appear in the project switcher. Open the project switcher from the organization dropdown in the top bar to see and accept them.

Newly-joined users get the basic Member access level.

Deleting an organization

An organization can be deleted by any organization Owner. This action is irreversible. See the Danger Zone in your organization settings for more information.

Deletion is processed asynchronously in the background. While it completes, all organization members are redirected to a blocking screen – this typically takes a couple of minutes. From this screen, you can switch to another organization (if you belong to one) or contact support.

IP data capture default

Organizations can set a default IP data capture policy that automatically applies to all new projects created within the organization. This setting helps ensure consistent privacy controls across all environments.

• IP data capture enabled: New projects will capture client IP addresses by default
• IP data capture disabled: New projects will automatically discard client IP data for enhanced privacy

This setting is particularly useful for organizations with GDPR compliance requirements, as it ensures all new environments are configured with appropriate privacy settings from the start.

Note: EU organizations automatically default to IP data capture disabled for GDPR compliance. Existing projects are not affected by this setting - only newly created projects will inherit the organization's default.

Individual projects can override this organization default by configuring their own IP data capture setting in Settings > Project > General under the IP data capture configuration setting.

Notifications

By default every time a member joins an organization in an email-enabled PostHog instance (including PostHog Cloud), all existing members of the organization get notified about this with an email. This increases security by making it explicit who gains access to your product data.

If you'd rather not get such notifications, you can disable them in the "Notification Preferences" section of organization settings.

Personal API key access

Organization admins and owners can view all personal API keys that have access to their organization or its projects. This includes organization-scoped keys, project-scoped keys, and fully unscoped keys held by any member.

Find this under Settings > Organization > Security > Personal API key access. For each key, you can see:

• Owner – the member who created the key
• Masked value – a display-safe hint (e.g. phx_***1234) to help identify the key
• Scopes – the API scopes granted (e.g. insight:read, or * for full access)
• Access scope – whether the key applies to the whole organization, specific projects, or all projects (unscoped)
• Last used and Created timestamps

The secret key value and key label are never exposed.

Note: This feature requires a plan that includes organization security settings. Only admins and owners can access this section.