Easily configure read-only rules for specific users across all models.

Before Applying Read-Only Rule:

Read-Only Rule Configuration:

After Applying Read-Only Rule:

With this setup, the specified users can no longer edit or delete any record in the affected view or model, ensuring strict adherence to your access policy without disrupting their ability to monitor key data.

Control sensitive data leakage by disabling the ability for selected users to export records from list views or any data grids. This helps secure confidential business information and maintain data privacy.

Before Applying Export Disable Rule:

Export Disable Rule Configuration:

After Applying Export Disable Rule:

Once the rule is applied, users will no longer see the export option in list views, preventing them from downloading sensitive data outside the system.

Prevent users from uploading external data into your system by disabling the import functionality for specific models or user groups. This helps avoid data pollution, duplicates, or unintended changes from bulk imports.

Before Applying Import Disable Rule:

Import Disable Rule Configuration:

After Applying Import Disable Rule:

Once disabled, the "Import" button is hidden from the interface for affected users, helping you control how data is introduced into the system and maintain data accuracy.

Restrict users from archiving or unarchiving records to prevent accidental data hiding or reactivation. Ideal for roles that should view but not modify record visibility statuses.

Before Applying Archive/Unarchive Disable Rule:

Archive/Unarchive Rule Configuration:

After Applying Archive/Unarchive Disable Rule:

Once the rule is active, the archive/unarchive button will be removed from the interface, ensuring only authorized personnel can change record statuses.

Protect important data by disabling the ability to delete records for certain user roles or models. Prevent accidental or unauthorized removal of critical business information.

Before Applying Delete Disable Rule:

Delete Rule Configuration:

After Applying Delete Disable Rule:

Once applied, the delete icon or menu will be hidden or deactivated for the targeted users, ensuring data safety and accountability.

Remove the chatter panel from forms for specific users or roles to streamline the interface and restrict access to messages, notes, and logs.

Before Applying Chatter Hide Rule:

Chatter Rule Configuration:

After Applying Chatter Hide Rule:

Once this rule is enforced, the chatter section will no longer appear on forms for users without permission, keeping the interface cleaner and reducing distraction or data exposure.

Restrict access to Developer/Debug mode for specific users or groups, enhancing security and preventing accidental or unauthorized system changes.

Before Applying Debug Mode Restriction:

Debug Mode Rule Configuration:

After Applying Debug Mode Restriction:

After applying the restriction, affected users will no longer be able to access developer tools or debug features, securing the backend and configuration settings.

Simplify the user interface by hiding menus or submenus from specific users or roles to reduce distractions and prevent unauthorized navigation.

Before Applying Menu Hide Rule:

Menu Hide Rule Configuration:

After Applying Menu Hide Rule:

Once this rule is enforced, the hidden menus will no longer appear in the navigation for targeted users, helping to maintain a clean and role-focused interface.

Control visibility of model-specific reports such as PDFs, print templates, or statistical summaries to restrict sensitive reporting access by user or role.

Before Applying Report Hide Rule:

Report Visibility Rule Configuration:

After Applying Report Hide Rule:

After applying the rule, reports will no longer be accessible from the user interface for the specified users or roles, ensuring secure access to business-critical insights.

Restrict visibility of model-specific server actions, or mass operations for selected users or roles to prevent unintended data processing.

Before Applying Action Hide Rule:

Action Visibility Rule Configuration:

After Applying Action Hide Rule:

Once applied, the selected model actions will be hidden for the designated users, ensuring cleaner UIs and tighter process control.

Configure detailed access control for any model—grant or restrict permissions like create, read, write, delete, run actions, and duplication—based on user or role.

Before Applying Model Access Rule:

Model Access Rule Configuration:

After Applying Model Access Rule:

Once rules are in place, users will only be able to interact with the model in the ways permitted—safeguarding data integrity and minimizing risk of unauthorized actions.

Control visibility, editability, and requirement status of fields on forms and lists. You can also remove the external link from related fields to restrict navigation.

Before Applying Field Access Rule:

Field Access Rule Configuration:

After Applying Field Access Rule:

These settings ensure that only relevant fields are visible or editable for users, improve form integrity, and prevent data leaks through unwanted external links.

Show or hide specific action buttons, tabs within forms, and entire form pages depending on the user's role or access level. This helps streamline the user interface and prevent unauthorized actions.

Before Applying Button/Tab/Page Rule:

Access Rule Configuration:

After Applying Button/Tab/Page Rule:

This level of control reduces UI clutter, enhances security, and tailors the experience based on user responsibilities.

Dynamically limit the records users can access using filter domains. Users will only see data relevant to their department, role, or assigned entities—ensuring data confidentiality and focus.

Before Applying Filter Domain:

Access Rule Configuration:

After Applying Filter Domain:

Use domain filters to ensure data privacy, eliminate confusion, and direct users’ attention only to what’s relevant to them.

Manage chatter visibility and control over notes, messages, and communication logs for specific models. Hide chatter where it's not needed or restrict posting access.

Before Restricting Chatter Access:

Access Rule Configuration:

After Restricting Chatter Access:

Prevent unauthorized users from posting internal communications or viewing sensitive activity logs by disabling chatter per model.