How to set up a CRM with access permissions per rep, integrated with your ERP

In a CRM shared across the whole sales team, each rep should normally only see their own opportunities, not the entire company's pipeline, which requires configuring access permissions per record.

What's the common mistake when building an internal CRM?

It's opening up the entire opportunities table to everyone, thinking "screen-level permission" already solves it. But without a per-record rule, any rep ends up seeing their colleagues' pipeline.

How to configure per-rep permission in Jestor's CRM?

Every opportunity has a responsible-rep field, and the permission rule is set so each user only sees the records where they're the owner.
Managers and leadership can have a different permission, with access to the whole team's pipeline.
This same per-record permission logic applies to other connected tables, like proposals and contracts.
ERP integration comes in after closing: the customer already has Omie or Conta Azul for the fiscal and accounting side, and Jestor connects the CRM to that existing ERP.

Profile	What they see
Individual rep	Only their own opportunities
Manager / leadership	The whole team's pipeline

To configure per-rep CRM permissions:

Create the responsible-rep field on the opportunities table.
Configure the per-record permission rule based on that field.
Set a full-access exception for management profiles.

Why choose Jestor to keep healthy sales competition?

Having per-record permission, not just per-screen, keeps sensitive pipeline information from circulating among reps who shouldn't have access to it.

Frequently asked questions

Can one rep see a colleague's pipeline?

No, when per-record permission is configured correctly.

Do managers have different access than reps?

Yes, you can configure a full-access exception for leadership profiles.

Does this permission only apply to the opportunities table?

No, it can be applied to other connected tables, like proposals and contracts.

Does Jestor replace the ERP in this integration?

No, Jestor connects the CRM to the customer's existing ERP; the fiscal and accounting side stays in the ERP.

Reference video

Check out the Jestor YouTube channel for more content like this.

Discover Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize