If you manage analytics for multiple products, you know the friction: logging in and out of different PostHog organizations, remembering which project belongs to which client, context-switching between dashboards.
On desktop, this is manageable. On mobile, it's painful. Here's how to handle multi-project PostHog workflows efficiently.
When You Need Multi-Project Support
Agency and Consulting Work
Client work often means juggling multiple PostHog accounts. Each client has their own organization, their own projects, their own dashboards. Checking analytics means:
- Log into Client A's PostHog
- Find the right project
- Check the relevant dashboard
- Log out
- Log into Client B's PostHog
- Repeat
On mobile web, this process involves multiple authentications, password managers, and waiting for full page loads. It's slow enough that you probably don't check as often as you should.
Multiple Products Under One Team
Even without client work, you might manage multiple apps. A company with three mobile apps and a web platform has four sets of analytics to monitor. Different products, different metrics, but one person responsible for keeping an eye on all of them.
Side Projects and Main Work
Many developers have both their employer's products and personal side projects using PostHog. Keeping these separate while still monitoring both requires quick context switching.
Development vs. Production Environments
Some teams maintain separate PostHog projects for development and production data. Checking production metrics shouldn't require accidentally viewing development noise, and vice versa.
The Mobile Challenge
PostHog's web dashboard handles multiple organizations, but mobile web browsers make this awkward:
Session management: Logging into a different organization often logs you out of the previous one. You're constantly re-authenticating.
Password manager friction: Each organization might have different credentials. On mobile, invoking the password manager, finding the right entry, and completing authentication takes time.
No persistent context: Close the browser tab, lose your session. Mobile browsers aggressively purge tabs and sessions.
Slow transitions: Each organization switch involves full page loads, re-rendering dashboards, waiting for data.
How HogWatch Handles Multiple Projects
HogWatch Pro supports unlimited PostHog projects. Here's how it works:
Adding Projects
Each PostHog project is added with:
- A friendly name you choose (e.g., "Client: Acme Corp" or "Side Project: Budget App")
- The PostHog API host (usually app.posthog.com, or your self-hosted URL)
- Your personal API key for that project
Each project's credentials are stored separately and securely on your device. Adding a second project doesn't affect the first.
Switching Contexts
Project switching is two taps:
1. Tap the project selector
2. Tap the project you want
No re-authentication. No waiting for login. The switch is instant.
Visual Organization
Give projects clear names that help you identify them at a glance. Color coding or emoji prefixes can help:
- "🏢 Work: Main App"
- "🏢 Work: Admin Dashboard"
- "🎯 Client: Acme Analytics"
- "🎯 Client: Globex Metrics"
- "🔧 Personal: Budget Tracker"
When you glance at the project list, you immediately know which world you're about to enter.
Per-Project Home Screen
HogWatch Pro lets you customize the home screen—pinning specific metrics for quick viewing. These customizations are per-project. Your main work app might show daily active users and conversion rate. Your side project might show total signups and error events.
Switch projects, see different dashboards. The context switch is complete.
Workflow Patterns
Morning Check-In
Start the day by cycling through projects:
- Open HogWatch
- Check primary work project: any issues overnight?
- Switch to secondary work project: quick health check
- Switch to client projects: anything needing attention?
- Switch to side project: any activity?
Total time: under two minutes. You now know the state of everything you're responsible for.
Client Meeting Prep
Before a client call, switch to their project. Review recent metrics so you can discuss performance knowledgeably. No fumbling for credentials, no asking to share screens while you log in.
Incident Response
Alert fires for one of your projects. Open HogWatch, switch to that specific project, check the relevant metrics. Know whether traffic is affected before you even open your laptop to investigate.
End of Day Review
Before closing out, quick check across projects. Anything unexpected? Anything to flag for tomorrow? Multi-project support makes this a 60-second habit instead of a 10-minute ordeal.
Security for Multiple Projects
Each project's credentials are stored separately and securely on your device. HogWatch connects directly to PostHog—your credentials never pass through a third-party server.
If you're handling client credentials:
Use dedicated API keys. Each project should have its own API key, not a shared key across clients.
Scope permissions appropriately. Read-only keys for viewing, minimal permissions for the use case.
Rotate when off-boarding. When you stop working with a client, they should rotate the API key you had access to.
The Bottom Line
Managing multiple PostHog projects is inherently complex. The goal isn't to eliminate that complexity—it's to reduce the friction of switching between contexts.
Mobile multi-project support means you can stay informed across all your responsibilities without the overhead of repeated authentication and slow page loads.
HogWatch Pro supports unlimited projects. If you manage analytics for more than one thing, the $4.99/month is worth it for the context-switching efficiency alone.
Try the 7-day free trial. Add all your projects. See how it changes your monitoring workflow.
HogWatch is an independent app and is not affiliated with or endorsed by PostHog Inc.