👉 Read Only User - Before Rule Applied

Before enabling Read Only User, the user has full access to the system and can create, edit, duplicate, and delete records .

👉 Read Only User - Form View (Before Rule Applied)

By default, users have full access to form views and can create, edit, duplicate, and delete records.

👉 Enable Read Only Rule

Open the configured access rule, assign the user, enable the Read-only option, set the desired priority level, and click Activate Rule to apply read-only restrictions.

Once the rule is activated, the selected user will no longer be able to create, edit, duplicate, or delete records and will only have permission to view data.

👉 Read Only User - After Rule Applied (List View)

After activating the Read-only rule, the user can only view existing records. Create, edit, duplicate, and delete operations are automatically restricted.

👉 Read Only User - After Rule Applied (Form View)

After activating the Read-only rule, users can view records but cannot create, edit, duplicate, or delete any data.

👉 Disable Login - Before Rule Applied

Before enabling the Disable Login rule, users can log in normally and access all applications and menus assigned to them.

👉 Configure Disable Login Rule

Create an access rule, assign the target user, enable the Disable Login option, and activate the rule to prevent the selected user from logging.

👉 Disable Login - After Rule Applied

After activating the Disable Login rule, the selected user is prevented logging.A clear restriction message is displayed, informing the user that their account has been temporarily disabled by the system administrator.

👉 Disable Developer Mode - Before Rule Applied

Before enabling the Disable Developer Mode rule, users can access Developer Mode and use all available technical features.

👉 Configure Disable Developer Mode Rule

Create a new access rule, assign the required users, enable the Disable Developer Mode option, and activate the rule to prevent selected users from accessing Developer Mode.

👉 Disable Developer Mode - After Rule Applied

After activating the Disable Developer Mode rule, the selected user can no longer access Developer Mode.

👉 Hide Menu - Before Rule Applied

Before applying the Hide Menu rule, users can view and access all assigned menus and sub-menus available in the navigation panel.

👉 Configure Hide Menu Rule

Open the access rule, navigate to the Hide Menu tab, select the menus or sub-menus you want to restrict, and activate the rule to apply the changes.

👉 Hide Menu - After Rule Applied

After activating the Hide Menu rule, the configured menus and sub-menus are automatically hidden. Users can only access the menus that are allowed by the applied access rule.

👉 Model Access Restriction

The Model Access (Restrict) tab provides a centralized set of options to control access to the selected model. Administrators can restrict reports, actions, views, create, edit, delete, archive, unarchive, duplicate, import, export, and edit properties for the assigned users based on business requirements.

👉 Before Rule Applied – Reports & Actions

Before applying the Model Access rule, users can access all reports and actions of the selected model.

👉 Before Rule Applied – Views

Before the rule is applied, all views of the selected model are accessible.

👉 Configure Model Access Restrictions

Create a Model Access rule, assign the required users, select the target model, and configure report, action, and view restrictions. After completing the configuration, click Activate Rule to apply the selected restrictions.

👉 After Rule Applied – Reports & Actions

After applying the Model Access rule, the configured reports and actions are hidden from the selected users and can no longer be accessed.

👉 After Rule Applied – View Restriction

After applying the Model Access rule, the restricted view is no longer accessible. Users attempting to open the restricted view will receive an Access Denied message.

👉 Before Rule Applied – Record Permissions

Before applying the Model Access rule, users have full permission to create, edit, delete, archive, unarchive, duplicate, import, export, and edit properties.

👉 Configure Record Operation Restrictions

Create a new access rule, assign the required users, open the Model Access (Restrict) tab, select the target model, and enable the record operations that should be restricted. Once the rule is activated, the selected users will no longer be able to perform those operations on the configured model.

👉 After Rule Applied - Record Operation Restrictions

After activating the rule, the selected record operations are restricted.

👉 Field Access Options

The Field Access tab provides a centralized set of options to control access to individual fields of the selected model. Administrators can configure fields as Invisible, Read-Only, or Required, and can also remove the Create, Edit, and External Link options for the assigned users based on business requirements.

👉 Before Rule Applied

Before applying the Field Access rule, users can create related records using the Create and Create and Edit options. All configured fields remain fully accessible without any restrictions.

👉 Configure Field Access Rule

Create a new access rule, assign the required users, open the Field Access tab, select the target model and fields, then configure the required field restrictions. Finally, click Activate Rule to apply the changes.

👉 After Rule Applied

After activating the Field Access rule, the configured field restrictions are applied to the selected users. Restricted fields and options are hidden or disabled according to the configured permissions.

👉 Conditional Field Access Rule

The rule is configured to apply the selected field attribute only when the specified condition is satisfied. This allows field behavior to change dynamically based on record values.

👉 Before Rule Applied

Before applying the Conditional Field Access rule, all configured fields remain visible and behave normally. No conditional restrictions are applied, regardless of the record values.

👉 Define Conditional Field Access Rule

Configure the Conditional Field Access rule by selecting the target model, choosing the field attribute (Required, Read-Only, or Invisible), and defining the condition that determines when the selected field restriction should be applied.

👉 After Rule Applied (Condition Matched)

When the configured condition is satisfied, the selected field restriction is automatically applied. In this example, the configured field becomes invisible because the record matches the defined condition.

👉 After Rule Applied (Condition Not Matched)

If the configured condition is not satisfied, the Conditional Field Access rule is ignored for that record. The configured field remains visible and continues to behave normally.

👉 Configure Domain-Based Access Rule

Create a Domain-Based Access rule by selecting the target model, choosing the operations to restrict (Read, Write, Create, or Delete), and defining the domain condition that determines which records the restriction applies to.

👉 Before Rule Applied

Before the Domain-Based Access rule is activated, all configured operations remain available. In this example, the Delete option is visible for every Sales Order regardless of the customer.

👉 Define Domain-Based Access Rule

Configure the restriction by selecting the target model, enabling the desired operation restriction, and defining a domain condition. The restriction will only affect records that satisfy the configured domain.

👉 After Rule Applied (Condition Matched)

When the configured domain condition is satisfied, the selected restriction is automatically enforced. In this example, the Delete option is hidden because the current record matches the configured customer condition.

👉 After Rule Applied (Condition Not Matched)

If the record does not satisfy the configured domain condition, the restriction is not applied. The Delete option remains available and users can continue to perform the operation on records outside the configured domain.

👉 Configure Button & Tab Access

Open the Button & Tab Access section and select the target model. Configure which form header buttons and notebook tabs should be hidden for specific users. Once the rule is activated, the selected interface elements will no longer be available.

👉 Before Rule Applied

Before the Button & Tab Access rule is activated, all configured buttons, action buttons, and notebook tabs remain visible. Users can perform every available action and access all tabs without any restrictions.

👉 Define Button & Tab Access Rule

Configure the Button & Tab Access rule by selecting the target users, companies, and user groups. Choose the buttons and notebook tabs that should be hidden, then activate the rule to apply the configured interface restrictions.

👉 After Rule Applied

After the Button & Tab Access rule is activated, the selected buttons and notebook tabs are automatically hidden. Users only see the permitted actions and interface elements according to the configured access rule.

👉 Search Panel Access Configuration

Select the target users, companies, and user groups, then activate the Search Panel Access rule. Configure the target model and define which filters, Group By options, Custom Filter, Custom Group By, and Delete Favorite actions should be restricted.

👉 Before Rule Applied

Before the Search Panel Access rule is activated, all search panel options remain available. Users can access all Filters, Group By options, Custom Filter, Custom Group By, and Delete Favorite actions without any restrictions.

👉 Configure Search Panel Access Rule

Configure Search Panel Access by selecting the target model and choosing which search filters, Group By options, Custom Filter, Custom Group By, and Delete Favorite actions should be hidden for the selected users, companies, or user groups.

👉 After Rule Applied

After activating the Search Panel Access rule, the configured search panel options are automatically hidden.

👉 Available Chatter Access Options

Configure individual Chatter components for the selected model. You can independently hide the complete Chatter panel or restrict Send Message, Log Notes, Activities, Search Messages, Attachments, Followers, and Follow/Unfollow options according to your access requirements.

👉 Before Rule Applied

Before the Chatter Access rule is activated, all Chatter components remain fully visible. Users can access Send Message, Log Notes, Activities, Attachments, Followers, Search, and Follow/Unfollow options without any restrictions.

👉 Hide Complete Chatter Panel

Enable the Hide Chatter option for the selected model to completely remove the Chatter panel.

👉 After Rule Applied

After activating the Chatter Access rule with the Hide Chatter option enabled, the complete Chatter panel is automatically removed from the selected model.

👉 Configure Selected Chatter Components

Configure only the required Chatter components for the selected model. Enable restrictions for Send Message, Log Notes, Activities, Search Messages, Attachments, Followers, and Follow/Unfollow options while keeping the Chatter panel visible.

👉 After Rule Applied

Once the Chatter Access rule is activated, the selected Chatter components are automatically hidden from the user interface while the remaining Chatter features continue to work normally.