Free5 minutesintermediate

Managing Member Permissions

Configure and manage team member permissions - customize access levels and website restrictions.

permissionsaccessmemberssecurity
Last updated: January 15, 2025

Manage what each team member can access and do in Zenovay. Fine-tune permissions beyond basic roles.

Accessing Permission Settings

  1. Go to Settings → Team
  2. Click "Members" tab
  3. View all team members

Member List View

MemberEmailRoleWebsitesLast Active
John Smithjohn@company.comAdminAllToday
Sarah Jonessarah@company.comEditor3 of 5Yesterday
Mike Wilsonmike@company.comViewer2 of 53 days ago

Editing Member Permissions

Change Role

  1. Click member name
  2. Select "Edit Role"
  3. Choose new role
  4. Save changes

Permission Panel

┌─────────────────────────────────────────────────────┐
│ Sarah Jones - Permissions                           │
│ ─────────────────────────────────────────────────── │
│                                                     │
│ Current Role: Editor                                │
│                                                     │
│ Role: [Viewer ▼] [Editor ✓] [Admin]                │
│                                                     │
│ Website Access:                                     │
│ ☑ marketing.company.com                            │
│ ☑ blog.company.com                                 │
│ ☑ shop.company.com                                 │
│ ☐ internal.company.com                             │
│ ☐ dev.company.com                                  │
│                                                     │
│ [Cancel] [Save Changes]                            │
└─────────────────────────────────────────────────────┘

Website-Level Permissions

Scale Plan

Restricting Website Access

Limit members to specific websites:

  1. Edit member permissions
  2. Uncheck websites to hide
  3. Save changes

Access Modes

ModeDescription
All websitesAccess everything (default)
Selected websitesOnly chosen sites visible
No websitesAccount exists but no access

Example Configuration

Marketing Team Member:
✓ marketing.company.com
✓ blog.company.com
✗ internal.company.com
✗ dev.company.com

Developer:
✗ marketing.company.com
✗ blog.company.com
✗ internal.company.com
✓ dev.company.com

Feature-Level Permissions

Enterprise Plan

Granular Controls

Customize specific feature access:

FeatureOptions
Session ReplayView / Disabled
HeatmapsView / Disabled
Revenue DataView / Hidden
User IdentificationView / Masked
ExportEnabled / Disabled

Setting Feature Permissions

  1. Edit member
  2. Click "Advanced Permissions"
  3. Toggle features
  4. Save

Privacy-Focused Settings

Hide sensitive data:

  • Mask PII: Hide personal information
  • Hide Revenue: Remove revenue figures
  • Disable Export: Prevent data downloads

Bulk Permission Management

Edit Multiple Members

Scale Plan
  1. Select multiple members (checkboxes)
  2. Click "Bulk Edit"
  3. Choose action:
    • Change role
    • Update website access
    • Remove all selected

Import/Export Permissions

Export current configuration:

  1. Go to Settings → Team
  2. Click "Export"
  3. Download CSV

Import updated configuration:

  1. Modify exported CSV
  2. Click "Import"
  3. Review changes
  4. Apply

Permission Groups

Enterprise Plan

Creating Groups

Organize members into groups:

  1. Go to SettingsTeam tab
  2. Click "Create Group"
  3. Name the group
  4. Set default permissions
  5. Add members

Example Groups

GroupRoleWebsitesFeatures
MarketingEditorMarketing sitesAll
SalesViewerAllNo export
DevelopmentAdminDev sitesAll
ExecutivesViewerAllNo replay

Managing Groups

  • Add/remove members
  • Update group permissions
  • Delete groups (members keep last permissions)

Temporary Access

Time-Limited Permissions

Enterprise Plan

Grant temporary access:

  1. Edit member
  2. Enable "Temporary Access"
  3. Set expiration date
  4. Access auto-revokes

Use Cases

ScenarioDuration
Contractor projectProject end date
Audit period30 days
Training1 week
Client review7 days

Permission Inheritance

How Inheritance Works

Team Role (Base)
    └── Website Access (Restricts)
          └── Feature Permissions (Further restricts)

Example

Sarah Jones:
├── Role: Editor (can edit)
├── Websites: Marketing only
└── Features: No export

Result: Can edit marketing site but not export data

Viewing Effective Permissions

Permission Summary

See what a member can actually do:

  1. Click member name
  2. View "Effective Permissions"
Sarah Jones - Effective Permissions

Analytics:
✓ View dashboard
✓ View real-time
✓ View sessions
✓ View heatmaps
✗ Export data (disabled)

Configuration:
✓ Create goals
✓ Edit website settings
✗ Delete websites (role limit)
✗ Manage integrations (role limit)

Websites:
✓ marketing.company.com
✓ blog.company.com
✗ internal.company.com
✗ dev.company.com

Common Scenarios

External Consultant

Limited view access:

  • Role: Viewer
  • Websites: Relevant only
  • Features: No export, masked PII

Department Manager

Department oversight:

  • Role: Editor
  • Websites: Department sites
  • Features: All

Executive Dashboard

High-level only:

  • Role: Viewer
  • Websites: All
  • Features: No session replay

Compliance Auditor

Temporary full access:

  • Role: Viewer
  • Websites: All
  • Features: All (time-limited)

Troubleshooting

Permission Not Working

If settings don't apply:

  1. Have member log out/in
  2. Clear browser cache
  3. Check for conflicting rules
  4. Verify save completed

Can't Edit Certain Members

You can only edit members with:

  • Lower role than yours
  • Same or lower access level

Inherited vs Direct

If permission seems wrong:

  • Check role permissions first
  • Then website restrictions
  • Then feature overrides

Audit Changes

View Permission History

See what changed:

  1. Go to SettingsActivity tab
  2. Filter by "Permission Changes"
  3. View timeline

Permission Change Log

DateUserActionTarget
Jan 15YouChanged roleSarah → Editor
Jan 14AdminRestricted sitesMike
Jan 10YouDisabled exportSarah

Best Practices

Start Restrictive

Begin with minimal access:

  1. Assign Viewer role
  2. Grant specific website access
  3. Enable features as needed

Document Decisions

Keep record of:

  • Why permissions granted
  • Who approved
  • Review date

Regular Reviews

Schedule permission audits:

  • Monthly for large teams
  • Quarterly for small teams
  • After any security incident

Next Steps

Was this article helpful?