Goals

Q2 2026 objectives

• Yasen

  • Platform features data as inputs to AI tools
  • Expose Metalytics to select orgs as part of the sales toolkit
  • Guest mode - allow orgs to share a specific object with a user and nothing else
  • Explore platform packages midpoint options
  • Access control scopes
    • Destinations or Workflows
  • AI tools
    • auditing-instance-security — guided posture review and prioritized hardening steps
    • enforcing-2fa-sso — lock down auth org-wide before something bad happens
    • configuring-approval-policies — add change-control gating to risky actions
    • reviewing-pending-approvals — triage and decide on pending approval requests
    • setting-up-reminders — offload recurring or time-based check-ins to PostHog
    • cleaning-up-unused-dashboards — prune stale dashboards cluttering the workspace
    • discovering-value-add-features — surface relevant capabilities the user doesn't yet know exist
    • reviewing-team-usage — usage picture of a team for renewal / churn calls

• Alex

  • Survey/experiment about white-labeling
  • Update the docs about the B2B2C case
  • Agent-native notebooks
  • Fix notebook papercuts
  • Help with data access control
  • SQL editor access control
  • AI tools
    • invite-a-user — get a teammate into the org without leaving chat
    • setting-up-saml — wire up SSO end-to-end without misreading a doc
    • setting-up-reverse-proxy — improve capture reliability and ad-blocker resistance
    • dumping-research-to-markdown — turn a sprawling chat session into a clean notebook summary
    • running-notebook-analysis — run a structured analysis (e.g. correlation) inside a notebook

• Reece

  • Access control
    • Customer analytics
    • Field-level access control
  • Fix settings
    • Entire products in settings
    • Notifications
  • Expand project->project transfers to more resources
  • Help with notebook papercuts
  • AI tools
    • granting-access — bestow or inspect roles on people, projects, and resources
    • creating-access-rules — carve out scoped project access for members or roles
    • auditing-permission-anomalies — spot users whose access drifted broader than it should be
    • explaining-created-resources — leave future readers context on agent-created resources
    • exploring-integrations — discover and turn on the right integration for the user's stack
    • suggesting-resource-access — recommend who should see a new resource so the user doesn't have to guess
    • sharing-with-roles — hand a dashboard or insight to the right people in one step

Q1 2026 objectives

• Yasen

  • Approvals GA
  • Activity logs -> Posthog AI
  • In-app notifications
  • Email MFA improve UX

• Alex

  • Roll out SCIM to all Enterprise customers and improve the docs
  • Make event definitions available to everyone, ship image previews for custom events
  • Finish PostHog AI access control
  • Run an email upsell growth experiment

• Reece

  • Passkeys
  • Project to project resource transfers (haha jk..unless... 😳)
  • RBAC UI redesign
  • Platform packages revenue optimization

Handbook

What the Platform features team does

• Authentication
  • Login and sign up
  • Invites
  • 2FA
• Enterprise features
  • SAML and SSO
  • Organization domains
  • SCIM
• Platform features
  • Organization settings
  • Access control and RBAC
  • Managed reverse proxy (with infra)
  • Authenticated domains
  • Organizations / Projects / Environments
  • Activity logs (audit logs)
  • Approvals (coming soon)
  • Emails / notifications

Who are we building for?

We've built 3 platform packages for companies at different stages of growth.

Boost

Best fit: Early-stage startups gaining traction that need access control, white labeling, or HIPAA compliance without enterprise complexity.

Persona: Technical founders

Reasons to upgrade to Boost:

• The team started running more experiments and feature flags in parallel, need to protect them from accidental changes -> access control
• Started using embedded surveys and want to remove PostHog branding -> white labeling
• A healthtech company needs to be HIPAA compliant -> BAA agreement
• User data protection becomes critical -> 2FA and SSO enforcement
• An agency or embedded analytics startup needs to keep customer data in separate projects -> unlimited projects

Scale

Best fit: Growing companies with multiple teams that need role-based access, audit trails for compliance, and centralized authentication.

Persona: Managers and team leads

Reasons to upgrade to Scale:

• The company has decided to get SOC 2 compliance -> activity logs as audit trails
• A startup has grown from a single team to several teams using PostHog, need visibility into who changed what and when -> activity logs and approvals
• The company started using identity provider for managing access -> SAML auth

Enterprise

Best fit: Large organizations that need automated identity management, SCIM provisioning, and full audit trails.

Persona: IT security officers and IT admins

Reasons to upgrade to Enterprise:

• The org has outgrown manual user management (hundreds of users) and needs to automate admin processes -> role-based access control, SCIM provisioning
• Security team needs to detect and respond to any issues -> audit logs with alerts

Who we're NOT building for

• Solo builders and hobbyists using PostHog for personal projects, don't need collaboration features, don't have budgets for platform packages
• Small teams (<10 people) at early-stage startups without compliance requirements, happy managing users manually, and prefer everyone-has-full-access setup
• Traditional enterprises requiring dedicated one-off feature development, or on-premise deployments