Feature

Team Permissions

Give every team member exactly the access they need — admins, managers, reps, and view-only roles.

Overview

Nexora Suite's team permissions system gives every team member a role — admin, manager, rep, or view-only. Roles control who can see which leads, edit settings, assign work, and access billing. Set it once and never worry about who should see what.

Key Benefits

Role-based defaults

Four built-in roles cover 95% of sales teams: Admin (full access), Manager (team oversight), Rep (own leads), and Viewer (read-only). Pick a role when you invite someone and you're done.

Granular overrides

Need a rep to see the whole pipeline but not billing? Or a contractor who should only access a single pipeline? Per-user overrides let you adjust any permission without rewriting role defaults.

Safe onboarding

New hires can be given view-only access during their first week, then promoted to full rep permissions once trained. No risk of accidentally exposing billing data to a trial user.

How It Works

1
Invite a team member
Send an invite from Settings → Team. Pick a role at invitation time.
2
The role sets the defaults
Admins see everything, managers see their team's work, reps see their own leads plus the shared pool, and viewers see read-only data.
3
Override specific permissions
Need to tweak a specific permission for one person? Open their profile in Settings and toggle individual access flags.

Most small teams don't think about permissions until something goes wrong: a contractor sees confidential deals, an intern accidentally deletes a lead, a competitor's ex-rep joins and takes the whole pipeline with them. By the time you're thinking about role-based access, you've already had the incident.

Nexora Suite's permissions system is built for the preventive case. Every team member has a role from the moment they're invited, and roles enforce sensible defaults: reps don't see billing, viewers can't edit, managers see their team but not other teams. You get the security without having to configure anything.

For teams that need more control, per-user overrides let you adjust specific permissions without changing the role. This is useful for edge cases — a trusted contractor who needs access to a specific pipeline, a new hire who should see reports but not edit them, an intern who should have view-only access for their first month.

Common Use Cases

Giving interns view-only access during onboarding
Restricting billing and financial data to admin roles
Letting freelancers work specific leads without seeing the whole pipeline
Separating sales and operations teams with different permission sets

Try Team Permissions in Nexora Suite

If you've ever worried about who can see what in your CRM, or if you've delayed hiring because onboarding permissions is painful, Nexora Suite's role system makes it a non-issue. Invite, pick a role, and you're done.

Get Started Free

Frequently Asked Questions

Can I create custom roles beyond the built-in four?▾

The built-in roles (Admin, Manager, Rep, Viewer) cover most teams. For edge cases, use per-user permission overrides rather than creating new roles — it's simpler to maintain and clearer to reason about.

What happens when I remove a team member?▾

Their access is revoked immediately, but their historical activity stays in the timeline (marked with their name). Their assigned leads can be bulk-reassigned to another team member or returned to the shared pool.

Can I give someone access to only one pipeline or team?▾

Yes. Per-user overrides support scoping a team member to specific pipelines, which is useful for freelancers and contractors who should only see a slice of your operation.

Glossary

Team Organigram in Nexora Suite — Visual Org Chart Built Into Your CRM

Glossary

Lead Management in Nexora Suite — Shared Lead Pool for Sales Teams

Glossary

Sales Dashboard in Nexora Suite — Your Daily Sales Control Center

for

Nexora for Sales Managers

for

Nexora for Remote Teams

question

Can I Share a CRM With My Team?