Skip to main content

How to Restrict Field Edit Permissions to Specific Users/Roles in Dazos CRM

Learn how to restrict field editing permissions in Dazos CRM so that only specific users or roles can modify certain fields while others have read-only access.

Before You Begin

  • You must have administrative access to create and manage roles in Dazos

  • Understand that field editability is managed at the Role level, not for individual users

  • Consider your organization's hierarchy structure before making changes

Understanding Role-Based Field Permissions

In Dazos CRM, field editability is controlled at the Role level rather than for individual users. This means:

  • You cannot give edit permissions to just one person within a shared role

  • All users assigned to a role will have the same field permissions

  • Fields can be set to "Read Only" or "Hidden" for entire roles

Implementation Options

You have two main approaches to restrict field editing:

Option 1: Create a Unique Role

Create a specific role for users who need full edit access while restricting other roles to read-only access.

Option 2: Role-Wide Restriction

Lock the field for everyone in specific roles if they no longer need to make changes to that field.

Steps to Create and Configure an Admin Role

  1. Create a New Role: Navigate to your role management settings and create a new role (e.g., "Full Admin")

  2. Assign the Role: Assign this new role to the user account that needs full edit access

  3. Position the Role Correctly: The admin role should be positioned at the top of your organizational hierarchy or at the same level as your highest existing roles (like Senior Executives) to ensure proper system authority

  4. Contact Support: Once your role is created and positioned correctly, contact Dazos support to manually configure the field restrictions for all other roles

Important Hierarchy Considerations

Role positioning in your organizational hierarchy affects system permissions:

  • Higher-level roles typically have more authority in system logic

  • If you cannot move your admin role above existing top-level roles, position it at the same hierarchical level

  • Roles at the same level are treated with equal authority by the system

Expected Result

After completing these steps:

  • Users with the admin role will have full edit access to the restricted field

  • Users in other roles will have read-only access to the field

  • The field restriction will apply across all relevant modules (such as Leads and Intake Opportunities)

Troubleshooting

Cannot move role to top of hierarchy: If you're unable to position your admin role above existing roles, place it at the same level as your highest existing roles (such as Senior Executives). Contact support for assistance with final positioning if needed.

Need multiple users with edit access: Assign multiple users to the same admin role, or create additional admin-level roles as needed.

Related Resources

  • Role Management Documentation

  • User Permissions Overview

  • Organizational Hierarchy Setup Guide

Did this answer your question?