Admin & Settings

Roles, permissions & exports

What admins, managers, and reps can do; CRM export and legislation sync rules.

Last updated 2026-04-12 2 min read

RepDesk uses roles and sometimes extra permission flags on a user record to decide who can configure the org, who can export CRM data, and who can run expensive sync jobs (such as Legislation Intelligence). Higher roles generally include what lower roles can do for day-to-day CRM work—but always confirm your company’s policy.

Role ladder (typical)#

Role

What they usually do

Super admin

Platform operator only—not your company’s tenant admin for day-to-day CRM.

Org admin / Admin

Users, integrations, CRM objects/fields, commissions settings (where applicable), and other org-wide configuration. Often have CRM export without extra toggles.

Manager

Team views, pipeline structure, and often CRM export; exact mix varies by org.

User

Works accounts, contacts, deals, tasks, etc., within visibility rules. Some features (commissions visibility, Deal Builder, export) may be flagged per user in Admin → Users.

Invite colleagues: Invite team members.

(Screenshot — add later: Admin → Users with role column or permission toggles.)

CRM export#

Export (CSV from CRM lists) is sensitive—many orgs limit it to managers and admins, or grant export via a permission flag on specific users. If you do not see Export, ask an admin rather than sharing your password with someone who has export.

Legislation Intelligence: view vs sync#

When Legislation Intelligence is enabled:

  • Browsing maps, trackers, and insights is usually available to everyone who can use the feature (subject to your org’s rules).

  • Running syncs (Sync All, bill syncs, etc.) is restricted to admins or users explicitly given the Legislation Sync permission—this protects API cost and data quality.

Rule of thumb: If a button says Sync and you are not sure you should press it, ask an admin first.


Info callout (optional in CMS):
Who can sync? Only admins or users with Legislation Sync. Everyone else can still use read-only tabs on Regulation when the feature is on.


Permission flags (per user)#

Beyond role, your admin may set flags on a user for things like:

  • Commissions visibility

  • Deal Builder access

  • CRM export

  • Legislation Sync

Those live under Admin → Users when your deployment exposes them—labels vary.

Was this helpful?