Crusource Docs
Teamspace & PermissionsUpdated: 2026-11-06
Overview: Configure role-based access control (RBAC), field-level permissions, and record ownership boundaries.

Roles & Record Visibility Policies

Crusource CRM enforces strict multi-tenant Role-Based Access Control (RBAC) to ensure that sensitive customer information, contract values, and executive notes remain secure and visible only to authorized personnel.

Default Role Hierarchies#

RoleScope & Privileges
AdministratorFull access to all CRM records, billing, team settings, user management, and API integrations.
Sales ManagerFull read/write access to all records owned by members within their assigned team; view team reports.
Sales RepresentativeAccess restricted to records they own or records shared collaboratively with them.
Read-Only AuditorRead-only access across assigned modules; cannot create, edit, or delete records.

Step 1: Navigating to Roles & Permissions#

  1. In the sidebar, navigate to Settings > Teamspace > Roles & Permissions.
  2. Review the list of predefined and custom roles.
Roles and Permissions Table
Click to enlarge screenshot
Roles and Permissions Table

Step 2: Customizing Module-Level Permissions#

  1. Click Edit next to any custom role.
  2. For each CRM module (Leads, Deals, Accounts, Contacts, Tasks, Calls, Meetings):
    • Create: Can this role author new records?
    • Read: Select between None, Owned Only, Team Only, or All Organization Records.
    • Edit: Select between None, Owned Only, Team Only, or All Organization Records.
    • Delete: Restrict permanent deletions to managers or admins only.

Step 3: Setting Field-Level Security#

To restrict sensitive fields (such as commission rates or private deal notes) from general view:

  1. Scroll down to the Field Security section.
  2. Select the target module (e.g., Deals).
  3. Find the sensitive field (e.g., Commission Split % or Internal Margins).
  4. Set permission to Hidden or Read-Only for individual roles.
  5. Click Save Permissions.

[!CAUTION] Changes to role permissions take effect immediately for all active sessions. Affected users will not need to log out.

Need Instant Assistance?

Have a question about Roles & Record Visibility Policies?

Ask Loop AI for step-by-step guidance, permission requirements, or troubleshooting tips directly within the docs.