We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For larger organizations, it would be beneficial to allow the owner of the org to be able to see how their team members are using PostHog.
Some possible ideas:
Essentially PostHog for PostHog, like how we have for support.
From: https://posthoghelp.zendesk.com/agent/tickets/20745
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables] - [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide] - [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature request
Is your feature request related to a problem?
For larger organizations, it would be beneficial to allow the owner of the org to be able to see how their team members are using PostHog.
Some possible ideas:
Describe the solution you'd like
Essentially PostHog for PostHog, like how we have for support.
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/20745
Debug info
The text was updated successfully, but these errors were encountered: