Skip to main content

​
Where to Find It

  • Click your name in the lower-left corner of Reevo.
  • Select Settings.
  • Navigate to Users, roles and teams.

​
Overview

Access Control in Reevo lets organization admins manage who can view and edit CRM records and activities through a combination of Teams, Roles, and record-level permissions. This ensures that sensitive customer data is only visible and editable by the right people in your organization. Reevo organizes access control around three concepts:
  • Teams — Groups of users that share record visibility.
  • Roles — Permission templates that define what a user can view or edit.
  • Record Ownership — Determines who “owns” a record and therefore has edit rights.
These three work together to create a flexible, layered permission system.
Only Org Admins can manage teams, roles, and user assignments. The first user in an organization is automatically assigned the Org Admin role.

​
Understanding Roles

Reevo provides three built-in system roles plus support for custom roles:
  • Org Admin — Full View and Edit access to all records across the entire organization. Can manage teams, roles, and user assignments.
  • Team Admin — Can view all org records. Can edit records owned by their team members and their own records.
  • Standard User — Can view all org records. Can only edit records they personally own.
  • Custom Roles — Org Admins can create custom roles with configurable View and Edit permissions per object type (up to 10 custom roles per organization).
System roles (Org Admin, Team Admin, Standard User) are read-only and cannot be modified. If you need a different combination of permissions, create a Custom Role with the desired configuration.
Important notes:
  • Each user can only be assigned one role at a time, defaulting to Standard User.
  • Edit permission always builds on top of View permission — a user must have View access to a record to also have Edit access.

​
Managing Teams

​
Creating a Team

  1. Navigate to Settings > Users, roles and teams > Teams.
  2. Click Create Team.
  3. Enter a name for the team.
  4. Save the team.

​
Adding a User to a Team

  1. Navigate to Settings > Users, roles and teams > Users.
  2. Select a user.
  3. Assign the user to a team.
Each user can only belong to one team at a time. To move a user to a different team, you must transfer them.

​
Transferring a User Between Teams

  1. Navigate to Settings > Users, roles and teams > Users and select the user.
  2. Change their team assignment from the current team to the new team.
  3. Choose how to handle the user’s owned records:
    • Stay with user — Records follow the user to their new team.
    • Stay with team — Records remain with the original team and ownership transfers to a selected user (defaults to the team admin).

​
Deleting a Team

  1. Remove or transfer all users currently assigned to the team first.
  2. Navigate to Settings > Users, roles and teams > Teams.
  3. Delete the team.
A team cannot be deleted while users are still assigned to it. You can bulk-transfer records during the user removal flow, or handle transfers separately via bulk edits.

​
Managing Roles

Only Org Admins can manage roles.

​
Creating a Custom Role

  1. Navigate to Settings > Users, roles and teams > Roles.
  2. Click Create Role.
  3. Name the role and configure View and Edit permissions for each object type:
    • Account, Contact, Opportunity — Set View and Edit at “All Org” or “Your Team’s” levels.
    • Meeting, Task — Set View and Edit at “All Org” or “Your Team’s” levels (applies to public meetings/tasks).
  4. Save the role.

​
Assigning a Role to a User

  1. Navigate to Settings > Users, roles and teams > Users and select a user.
  2. Assign or change the user’s role.

​
Deleting a Custom Role

  1. Unassign all users from the custom role first.
  2. Navigate to Settings > Users, roles and teams > Roles.
  3. Delete the role.
A custom role cannot be deleted while users are still assigned to it. Organizations can have up to 10 custom roles.

​
Permission Details

​
Supported Objects

Access Control applies to the following record types:
  • Accounts
  • Contacts
  • Opportunities
  • Meetings (public and private)
  • Tasks (public and private)

​
Permission Matrix — System Roles

RoleViewEdit
Org AdminAll records across the orgAll records across the org
Team AdminAll records across the orgYour team’s records + your own records
Standard UserAll records across the orgOnly records you own
Custom RolesConfigurable per objectConfigurable per object

​
Public vs. Private Records (Meetings & Tasks)

Meetings and Tasks have an additional layer of visibility control:
  • Public meetings/tasks — Visible to all users who have View access based on their role. Edit access follows the role’s configuration.
  • Private meetings/tasks — Visible only to the owner and participants, regardless of role. This is not configurable via custom roles.

​
Troubleshooting / FAQs

View and Edit are separate permissions. Your role may grant you View access to all org records but restrict Edit access to only your own records or your team’s records. Check your role configuration in Settings > Users, roles and teams > Users.
The meeting or task may be marked as private. Private meetings and tasks are only visible to the owner and invited participants, regardless of your role.
Navigate to Settings > Users, roles and teams > Users and find your name. Your assigned role will be displayed in your user profile.
When transferring a user between teams, you choose one of two options: records can follow the user to the new team, or records can stay with the original team (with ownership transferring to another team member).
Not currently. Each user has a 1-to-1 team association. Multiple team support is planned for a future release.
No. Org Admin, Team Admin, and Standard User are read-only system roles. To customize permissions, create a Custom Role with the desired configuration.