Pirsch User Management | OpsBlu Docs

Pirsch User Management

Manage user roles, permissions, and team access in Pirsch — step-by-step admin guide.

User Management Overview

Pirsch provides a privacy-first approach to team collaboration, allowing you to grant access to analytics dashboards while maintaining strict GDPR compliance and data protection standards. The platform's user management system is designed for simplicity and security.

Understanding Pirsch User Management

Platform Overview

Pirsch is a privacy-focused, cookie-free analytics platform that emphasizes:

  • GDPR and CCPA compliance by design
  • No use of cookies or personal identifiers
  • Server-side analytics for accuracy
  • Privacy-respecting visitor tracking
  • Simple, straightforward reporting
  • Fast, lightweight dashboard performance

User management in Pirsch is intentionally streamlined to maintain the platform's focus on simplicity while enabling team collaboration on website analytics.

Account Structure

Pirsch uses a straightforward access model:

  • Each Pirsch account can have multiple team members
  • Team members are invited by email address
  • Access is granted at the account level (all websites in the account)
  • Role-based permissions control what team members can do
  • The account owner has ultimate control over all settings

Available User Roles

Pirsch offers two primary role levels:

Owner

The Owner role has complete control over the Pirsch account:

  • Full access to all analytics dashboards and reports
  • Can manage billing and subscription settings
  • Can add, remove, and modify team members
  • Can create, edit, and delete websites
  • Can configure tracking settings and filters
  • Can access API tokens and integrations
  • Can delete the entire account
  • Only one Owner per account (the original account creator)

Member

The Member role provides standard analytics access:

  • Can view all analytics dashboards and data
  • Can access visitor statistics and page views
  • Can view traffic sources and referrers
  • Can see events and conversion data
  • Cannot modify account or billing settings
  • Cannot add or remove other team members
  • Cannot delete websites or the account
  • Cannot access sensitive billing information

Pirsch uses a simple Owner/Member access model across all plans. There are no additional granular permissions — Owners have full control, Members can view analytics but cannot modify settings or billing.

Common Use Cases

Team Collaboration

For marketing and analytics teams:

  • Add team members as Members for analytics access
  • Maintain Owner access for the account administrator
  • Grant Members access to view traffic and engagement data
  • Enable cross-functional teams to access website performance metrics

Typical team structure:

  • Marketing Manager: Owner
  • Marketing Analysts: Member
  • Content Creators: Member
  • Executives: Member (for reporting access)

Agency Client Reporting

For agencies managing client analytics:

  • Create separate Pirsch accounts for each client
  • Add agency team members as Members to client accounts
  • Grant clients Member access to view their own analytics
  • Maintain Owner access for account management

Best practices:

  • Use professional email addresses for team invitations
  • Document which agency members have access to which client accounts
  • Remove access when team members change client assignments

Contractor and Freelancer Access

When working with external team members:

  • Add contractors as Members for limited, view-only access
  • Remove access immediately when contracts end
  • Use email-based invitations for easy onboarding
  • No elevated permissions needed for most contractor scenarios

Internal Stakeholder Access

For executives and cross-functional visibility:

  • Add executives as Members for reporting access
  • Grant product teams Member access to understand user behavior
  • Provide customer support Member access for traffic insights
  • Enable data-driven decision-making across departments

Best Practices for User Management

Security and Privacy

  1. Email Verification: Always use verified business email addresses
  2. Regular Audits: Review team members quarterly to remove inactive users
  3. Immediate Removal: Remove access when employees leave the organization
  4. Owner Protection: Safeguard Owner credentials with strong passwords
  5. Privacy First: Ensure team members understand Pirsch's privacy-focused approach

Access Control

  1. Least Privilege: Member role is sufficient for most team members
  2. Owner Limitation: Only grant Owner access to trusted administrators
  3. Document Access: Maintain records of who has access and why
  4. Review Regularly: Audit access levels during team changes
  5. Use Cases: Align access levels with actual job responsibilities

Team Organization

  1. Clear Roles: Define who needs Owner vs. Member access before inviting
  2. Email Standards: Use company domain emails for all invitations
  3. Onboarding: Provide brief training on Pirsch interface and features
  4. Support Resources: Share Pirsch documentation with new team members
  5. Communication: Notify team members of access changes

Data Governance

  1. Privacy Training: Educate team on privacy-first analytics approach
  2. GDPR Compliance: Ensure team understands regulatory requirements
  3. Data Minimization: Explain Pirsch's cookie-free tracking model
  4. Responsible Use: Clarify acceptable use of analytics data
  5. Reporting Standards: Establish guidelines for sharing analytics insights

Troubleshooting Common Issues

Team Member Cannot Access Account

If a team member can't access Pirsch:

  1. Verify they accepted the email invitation
  2. Confirm they're using the correct email address to log in
  3. Check that their account wasn't removed or suspended
  4. Ensure they're logging into the correct Pirsch account
  5. Have them check spam folder for invitation email

Invitation Not Received

If invited users don't receive the invitation email:

  1. Check that email address was entered correctly
  2. Ask them to check spam/junk folders
  3. Verify corporate email filters aren't blocking Pirsch emails
  4. Resend the invitation from team management settings
  5. Try an alternative email address if available

Cannot Remove a Team Member

If you're unable to remove someone:

  1. Verify you have Owner permissions
  2. You cannot remove yourself as Owner
  3. Ensure you're not trying to remove the last Owner
  4. Check for any platform-specific restrictions
  5. Contact Pirsch support for assistance

Wrong Role Assigned

If someone has incorrect permissions:

  1. Roles can typically be changed after invitation
  2. Navigate to team settings
  3. Find the team member and edit their role
  4. Changes take effect immediately
  5. User may need to log out and back in

Multiple Websites, Wrong Access

If team members need different access to different websites:

  1. Pirsch typically grants access at the account level
  2. For website-specific access, consider separate accounts
  3. Use sub-accounts or organizations if available in your plan
  4. Contact Pirsch support for enterprise access options

Privacy and Compliance Considerations

GDPR Compliance

Pirsch is built for GDPR compliance:

  • No cookies or personal data collection
  • Server-side analytics without visitor tracking
  • Privacy-first design by default
  • Team members should understand these principles

Data Access

Team members with access can view:

  • Aggregate visitor statistics
  • Page views and traffic sources
  • Event data and conversions
  • Geographic and device data (non-personal)

Team members cannot view:

  • Individual visitor identities
  • Personal information (Pirsch doesn't collect it)
  • Tracking cookies or user IDs
  • Behavioral profiles of specific users

Responsible Analytics

Best practices for team members:

  1. Understand Pirsch's privacy-focused approach
  2. Use aggregate data for decision-making
  3. Follow organizational data governance policies
  4. Respect visitor privacy in reporting and analysis
  5. Align analytics usage with privacy regulations

Subscription and Team Management

Plan Limits

Different Pirsch plans may have:

  • Varying limits on team member counts
  • Different numbers of websites per account
  • Tier-specific features and capabilities
  • Check your plan for team member allowances

Managing Team Size

Best practices:

  1. Review your plan's team member limit
  2. Remove inactive members to free up seats
  3. Upgrade plan if you need more team members
  4. Contact Pirsch support for enterprise options
  5. Consider multi-account strategies for large organizations

Additional Resources

返回顶部