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 Controls let organization admins decide who can view and edit CRM records. Three things combine to produce a user’s access:
  • Record ownership: who owns a record.
  • Teams: which group of users someone belongs to.
  • Roles: the permission template assigned to a user.
Only Org Admins can manage teams, roles, and user assignments. The first user in an organization is automatically assigned the Org Admin role.

Before You Configure Access

Set these up first, or role scoping will not behave the way you expect:
  1. Confirm record ownership is correct. Every scope other than Organization depends on the owner field. Use Reassign ownership to correct owners in bulk.
  2. Create your teams and assign users. Team scope has no effect until users belong to a team. See Users, roles and teams.
  3. Decide per record type. View and Edit are configured separately for each record type, not once for the whole role.

Permission Scopes

Every View and Edit permission is granted at one of four scopes. Scopes are additive: a user gets access if any scope they hold applies to the record. Owner access is a floor, not a setting. Record owners always have View and Edit access to their own records. There is no configuration that removes a user’s access to a record they own. Participant access is set per role. Accounts, contacts, and opportunities each have a Participants field listing users. In the Participant section of a role, you choose View and Edit separately for each of these record types. A user listed in a record’s Participants field gets the access their role allows there, even when Team and Organization are both unchecked for that record type. Meetings and tasks are different: participants always have access to them, subject to the Public and Private rules below.
When the Participant section first appears for your organization, review your existing custom roles. Participant starts unchecked on them, so users with those roles can no longer see accounts, contacts, and opportunities they’re only a participant on until you check View in the Participant section.
The Participants field is managed manually. Someone has to add a user to it on the record, or set it when the record is created. It is not populated automatically from meeting attendance or email activity, and it cannot be set through CSV import. Meetings are the exception: their participants come from the calendar invite.
To restrict a user to only the records they own, create a custom role and leave Organization, Team, and Participant unchecked for that record type. See Restrict users to only their own records.

System Roles

Reevo ships with system roles that cannot be edited. To get a different combination of permissions, create a custom role.
  • Organization Admin: View and Edit all records across the organization. Can manage teams, roles, and user assignments.
  • Team Admin: View all organization records. Edit records owned by their team members, records they’re a participant on, plus their own.
  • Standard User: View all organization records. Edit records they own or are a participant on. This is the default for new users.
Standard User, the default role, can view every record in the organization. If that is not what you want, assign a custom role instead.

Custom Roles

Only Org Admins can manage roles.

Creating a Custom Role

  1. Navigate to Settings > Users, roles and teams > Roles.
  2. Click Create role and enter a name and optional description.
  3. In the Organization section, check View or Edit for each record type that should be visible or editable org-wide.
  4. In the Team section, do the same for records owned by the user’s teammates.
  5. In the Participant section, check View or Edit for each record type the user should be able to see or change when they are listed in that record’s Participants field. This section covers accounts, contacts, and opportunities.
  6. Review the Role summary panel, which describes the resulting access in plain language.
  7. Save the role.
Two rules apply automatically as you configure:
  • Granting Organization access also grants Team access, so the Team checkbox locks on.
  • Granting Edit also grants View, so the View checkbox locks on. Edit always builds on View.

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.
Each user holds exactly one role at a time.

Deleting a Custom Role

  1. Unassign or move all users off the 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.

Managing Teams

Creating a Team

  1. Navigate to Settings > Users, roles and teams > Teams.
  2. Click Create Team.
  3. Enter a name and save.

Adding a User to a Team

  1. Navigate to Settings > Users, roles and teams > Users.
  2. Select a user and assign them to a team.
Each user belongs to one team at a time. To move a user, 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.
  3. Choose how to handle the records they own:
    • Stay with user: records follow the user to the new team.
    • Stay with team: records remain with the original team and ownership transfers to a selected user, defaulting to the team admin.

Deleting a Team

  1. Remove or transfer all users assigned to the team.
  2. Navigate to Settings > Users, roles and teams > Teams.
  3. Delete the team.
A team cannot be deleted while users are assigned to it. Bulk team operations run in the background; track them on Team transfer status.

Permission Reference

Supported Record Types

Access Controls apply to Accounts, Contacts, Opportunities, Meetings, and Tasks.

System Role Matrix

Private Meetings and Tasks

Meetings and Tasks carry an extra visibility flag:
  • Public: visible according to the viewer’s role.
  • Private: visible only to the owner and participants, regardless of role. Roles cannot override this.

What Access Controls Do Not Cover

  • Lists: contact and account lists are visible to everyone in the organization. There is no per-list visibility setting. The records shown inside a list still respect each viewer’s permissions, so two users can open the same list and see different numbers of rows.
  • Saved views: views have their own Private and Organization Shared setting, which is separate from roles. See List views and filters.
  • Deleting records: roles configure View and Edit only.
What roles do control: record visibility and editing in CRM list views, record pages, search results, and exports. A user’s export contains only the records their role allows, and bulk exports require admin access.

Troubleshooting / FAQs

Two reasons. Either the user owns the record, or they are listed in the record’s Participants field and their role allows participant access. Open the record and check its Owner and Participants fields. To stop participant access for everyone with that role, uncheck View in the role’s Participant section for that record type. To stop it for one record, remove the user from that record’s Participants field. Owners always keep access.
View and Edit are separate permissions. Your role may grant View across the organization while limiting Edit to records you own, are a participant on, or your team owns. Check your role in Settings > Users, roles and teams > Users.
It is likely marked private. Private meetings and tasks are visible only to the owner and participants, regardless of role.
Organization access already includes the team’s records, so the Team checkbox locks on when Organization is enabled. Uncheck Organization to configure Team separately.
Edit is enabled for that record type and scope. Edit requires View, so View locks on. Uncheck Edit to release it.
Not currently. Contact and account lists are visible organization-wide. The records inside a list are still filtered by each viewer’s permissions.
No. Exports apply the same record-level permissions as the CRM, so a user’s export contains only the records they can already see. Bulk exports also require admin access.
Navigate to Settings > Users, roles and teams > Users and find your name. Your role is shown in your user profile.
You choose during the transfer: records follow the user to the new team, or stay with the original team with ownership transferring to another member.
No. Each user has one team and one role at a time.
No. System roles are read-only. Create a custom role instead.