CRM Team Permissions: Share Work With Clear Boundaries
Set up practical Convertly roles by separating module access from record visibility, then verify that teammates can do their work without unnecessary access.
A connected CRM gives your team more context. It also creates a responsibility to decide who needs to see and change that context. Good access design starts with people’s work, not with a role name that sounds right.
Convertly has an Admin system role and organization-owned custom roles. You can name a role for your own team, but its configured permissions determine what the user can do.
Separate two access decisions
Module access controls whether someone has no access, view access, or manage access to a relevant area. Record visibility determines whether the person works with assigned records or all permitted workspace records.
These settings work together. Someone may need to manage their own leads without managing every lead in the organization. Another person may need a broader view for a review without permission to change the underlying work.
Do not assume that a role called “Manager” includes a predefined set of rights. Treat the label as a description of the responsibility you configured.
Design the role around a real working day
List the tasks the person needs to perform. A salesperson might need to review leads, record calls, work with follow-ups, and respond through an authorized WhatsApp inbox. A reporting colleague may need different modules and a different record scope.
As an Admin, use the user and role controls in Settings to create the role and select the appropriate module permissions and visibility. Give manage access where changes are necessary rather than enabling it everywhere for convenience.
Integrations, billing, organization configuration, and user management remain administrative responsibilities. Reserve Admin access for people who actually maintain the workspace.
Test the experience outside the Admin account
An Admin’s view is not a reliable test of a custom role. Verify with an appropriate non-Admin account that the person can complete the intended work and cannot reach records outside their scope.
Check connected workflows, not only menu visibility. Can the user open the lead related to a follow-up? Can they access the intended inbox? Can they view relevant call information? A visible navigation item does not grant extra rights by itself.
AI follows the user’s data access too. It is not a shortcut around restricted lead visibility.
Plan changes to people and responsibilities
When someone changes roles, review their access and outstanding work together. Reassign leads and follow-ups deliberately so customer commitments are not left without a responsible person.
Permission changes can take effect immediately. Archiving a role may also require a replacement for users or dependent rules. Restoring it does not automatically move people back or re-enable associated automations.
Troubleshoot a missing record methodically
Check the active workspace, module permissions, assigned-versus-all visibility, ownership, and Trash status. For messages or calls, check the relevant inbox or device restrictions as well.
Do not solve every access question by making the user an Admin. Identify the specific permission or assignment needed, then retest the workflow.
Use the roles and access guide when creating your first custom role or reviewing an existing one. The aim is enough access to do the job, with clear responsibility for the rest.