Add Users to Crazy Egg: Step-by-Step | OpsBlu Docs

Add Users to Crazy Egg: Step-by-Step

Invite team members to Crazy Egg with Admin, User, or Viewer roles -- step-by-step invitation process, role capabilities, and site-level access...

Crazy Egg Team Roles

Crazy Egg uses three permission levels. All roles can view heatmaps and recordings, but editing and administrative capabilities differ:

Capability Admin User Viewer
View heatmaps, scrollmaps, confetti reports Yes Yes Yes
View session recordings Yes Yes Yes
View A/B test results Yes Yes Yes
Create and manage snapshots Yes Yes No
Start and stop A/B tests Yes Yes No
Configure recording settings Yes Yes No
Manage team members Yes No No
Manage billing and plan Yes No No
Install/modify tracking script Yes No No
Delete account data Yes No No

Admin -- Full account control including billing, team management, and script configuration. Limit to account owners and senior stakeholders.

User -- Can create snapshots, run A/B tests, and configure recordings. Best for UX designers, marketers, and optimization specialists who actively run experiments.

Viewer -- Read-only access to all data. Ideal for executives, clients, and stakeholders who review reports without making changes.

Inviting a New Team Member

  1. Log in to Crazy Egg with an Admin account
  2. Click your account avatar (top right) > Account > Team
  3. Click Invite Member
  4. Enter the user's email address
  5. Select role: Admin, User, or Viewer
  6. Click Send Invite

The invited user receives an email with a link to create a Crazy Egg account (or log in if they already have one) and join your team.

# Invitation email subject line:
"You've been invited to join [Your Account Name] on Crazy Egg"

# The link directs to:
https://app.crazyegg.com/invitation/accept?token=<invitation_token>

Managing Invitation Status

Track pending invitations on the Team page:

Status Meaning Action
Pending Email sent, not yet accepted Wait or resend
Accepted User active on the account No action needed
Expired Invitation not accepted within 7 days Remove and re-invite

To resend an expired invitation, remove the pending entry from the Team page and create a new invite.

Plan Limits on Team Size

Team member slots depend on your Crazy Egg plan:

Plan Team Members Included
Basic 1 (owner only)
Standard 5
Plus 10
Pro 20
Enterprise Unlimited

If you reach the team member limit, you must upgrade or remove an existing member before inviting someone new.

Site-Level Access

Crazy Egg does not support per-site permissions within a single account. All team members see all sites and snapshots tracked by the account. If you need to restrict access by site:

  1. Create separate Crazy Egg accounts for each site or client
  2. Invite users only to the accounts they need access to
  3. Each account has its own tracking script and snapshot configuration

This is the only way to enforce site-level isolation. Within a single account, all team members have visibility into all tracked pages.

Bulk User Onboarding

Crazy Egg does not offer a bulk invite API or CSV upload. For onboarding multiple users:

// No official API -- invitations must be sent one at a time via the UI
// For teams with many members, consider this workflow:

// 1. Prepare a list of emails and roles
const newMembers = [
  { email: 'designer@company.com', role: 'User' },
  { email: 'vp-product@company.com', role: 'Viewer' },
  { email: 'analyst@company.com', role: 'User' },
  { email: 'ceo@company.com', role: 'Viewer' }
];

// 2. Send invitations one at a time through the Team page
// 3. Track acceptance in a spreadsheet until all members confirm

For Enterprise accounts, contact Crazy Egg support for bulk provisioning options.

Post-Invitation Setup

After the user accepts their invitation:

  1. Verify access -- Ask them to log in and confirm they see existing snapshots and recordings
  2. Share snapshot naming conventions -- Consistent naming (e.g., homepage-desktop-2026-03, pdp-mobile-2026-03) helps team members find relevant data
  3. Review recording filters -- If recordings are enabled, ensure the user understands which pages are being recorded and any PII exclusion rules
  4. Share A/B test protocols -- If the user will run tests, document your team's process for test creation, sample size requirements, and winner implementation

Best Practices

  1. Use Viewer role for anyone who only needs to review data
  2. Reserve Admin for one or two account owners
  3. Remove access immediately when team members leave or projects end
  4. Review the team member list quarterly and remove stale accounts
  5. Use separate accounts for client work to maintain data isolation