Skip to main content

Roles and Permissions in Whippy

Use Roles to review default access levels and create custom permission sets for users.

Written by Maria Cairns

Why it matters

Clear roles reduce accidental access, make onboarding faster, and give admins a repeatable way to match permissions to each person's responsibilities.

Key Concepts

Default roles: Whippy includes Admin and User as default roles. Admin has full workspace access except billing, while User has limited workspace access and cannot change organization-level settings.

Custom roles: Custom roles let admins define a tailored permission set with a role name, optional description, and selected permissions.

Permission groups: Permissions are grouped in expandable sections and can be searched so admins can find the access they need.

Step-by-Step: Create or update a custom role

  1. Open Settings > Users and teams.

  2. Select the Roles tab.

  3. Review Default roles before creating a new custom role.

  4. Click Add role in the Custom roles section.

  5. Enter a Role name and optional Description.

  6. Use Search permissions to find relevant permissions, or expand each permission group.

  7. Select individual permissions, or use Select all permissions when the role should include every permission.

  8. Click Add role or Save changes.

Tips and Best Practices

  • Keep custom role names outcome-based, such as Support lead or Campaign manager.

  • Give users the least access they need to do their work.

  • Review custom roles after major product or process changes.

  • Do not use teams as a substitute for permissions. Use teams for grouping and roles for access.

Troubleshooting

Issue

Possible Cause

Fix

A role cannot be edited

The role may be a default role or your account may not have role management permission.

Create a custom role for a tailored access set, or ask an admin to update your access.

A permission is hard to find

The permission may be inside a collapsed group.

Use Search permissions, then expand the matching permission group.

A user still cannot access a feature after a role change

The feature may also depend on channel-specific access or another organization setting.

Review the user's role, then check any channel or workflow-specific access requirements.

Did this answer your question?