How to configure

For config this module you need to first debug the developer mode on. After go to the Setting → Users & Companies → Users and select any User in which you want to apply the configuration. Once you open any record then click on the Access Management tab.

Hide Menu, Submenu

This configuration is used for hiding the Menu or Submenu for the particular user. Once we configure it, then that menu will not be visible for the user.

Before configuring the menu current user can see the following menus.

Now we want to hide the Sales menu for this user then we just need to select the menu from the list and save it.

Before the Submenu hide this below screen visible.

If we want to hide the submenu then we need to configure the submenu same way we configure before.

After doing the above configuration and save the record and go to the user login and refresh the page then it will display this below screen.

Reports

If we want to hide the specific report based on the user then we will add the report in the Access Management -> Report Tab and add the record of the report which we want to hide then save the records.

Before the configuration in the user below screen display.

After the above configuration is done. When we checked with that user in the Invoices then it will display the below screen.

Same way we can configure the number of the report which we want to hide for the particular users.

Actions

If we want to hide the specific actions based on the user then we will add the action in the Access Management → Actions Tab and add the record of the action which we want to hide then save the records.

Here we have separated the Action in the Two Section Server Action and Client Action based on the requirement you can configured and that action will be not visible to the particular user.

Server Actions: Server actions allow you to define a sequence of actions to be performed, such as creating records, updating fields, sending emails, and more.

Client Actions: Client actions are used to define actions that occur on the client side, typically related to user interface interactions.

Before the configure the user will see the below screen.

After adding this action just we need to save the record then go to the user login page and refresh the page. Here it will hide the config action for that particular user.

Now we have configured the below action in the user from view.

After add this action just we need to save the record the go to the user login page and refresh the page. Here it will hide the config action for that particular user.

Fields

Using this module we can configure the fields level configuration like readonly fields, required fields, invisible fields, Disable Create and Edit option in Many2one and Many2many, Disable redirect link in Many2one.

Here we have give the details of the each fields:

Model You need to select the model in which you want to perform the operations.

Field After selecting the model you will see the fields of that particular model and you need to select any field from the list.

Invisible If you set invisible is true then that particular field will be invisible for that model and particular Users.

Readonly If you set readonly is true then that particular field will be readonly for that model and particular Users.

Required If you set required is true then that particular field will be required for that model and particular Users.

Remove External Link This functionality is only used for the Many2one fields. If you set true then we can not redirect from that particular field.

Remove Create/Edit Button This functionality is used for hide the option of Create/Edit from Many2one and Many2many fields.

Invisible Fields

Here you can see in the below screen user can see the Payment Reference field.

Now we are configure this field in the User form view like below screen.

In this screen we have configured like user can not see the Payment Reference field. Once the user go to this page then user will be not see this configuration field.

Readonly Fields

If we set the Readonly true in any fields then it will be not editable for that particular user. Currently we can edit the Payment terms.

Now we configure this field as a readonly.

After the above configuration user will be see this below screen and field become readonly for this user.

Required Fields

If we want to make any fields as a required field for any user then we will do using this configuration. In the Customer Invoice Invoice Date field is not required. So now we will configure this field as required for this user.

After the above configuration Invoice Date field will become required for this user. You can see in this below screen

Remove External Link

Currently here we can see that External Link in the Payment Terms.

If we want to hide the redirect link from the Many2one field then you need to configure this Boolean True like below screen.

Now checking the same form with that user and it will remove the redirect link from.

Remove Create/Edit Option This functionality is used to hide the option of Create/Edit from Many2one and Many2many fields.

Here we can see the Create and Edit option available for customer field.

So if we want to remove this option using the configuration then we need to do this following configuration.

After saving the record, if we check with the above user then it will be displayed like below screen.

Views

Hide Views based on configuration for object. We can hide any view like Form, Tree, Kanban etc

Currently we can see the following views for this user. If we want to hide any view like kanban, Calender then we just need to configure the form view for this user.

Here we have configured the Lead/Opportunity model and config the Calendar and Kanban view for the user.

After the above configuration we will see this below screen of the views for that user.

Create, Edit Button Invisible in Tree/Form View

If we want to hide the create button from any object then we will do it using configuration.

For remove the Create access we need to do the following configuration.

After the above configuration we will see the below screen for that user.

Same way we can invisible the edit button.

Delete, Duplicate Action Invisible in Tree/Form View

Currently we can see the this below action for the user.

If we want to invisible the Delete and Duplicate action from the tree and Form view then we will do the following configuration in the user configuration.

In the Above screen we have configure for the Journal Entry (Customer Invoice or Bill). so once we check with the user then it will be invisible the this Duplicate and Delete action.

Export, Archive Action Invisible in Tree/Form View

Currently we can see the this below action for the user.

If we want to invisible the Export and Archive action from the tree and Form view then we will do the following configuration in the user configuration.

In the Above screen we have configure for the Lead/Opportunity. so once we check with the user then it will be invisible the this Archive and Export action.

Hide Chatter Messages in Form View

Currently we can see this below Chatter Messages for the user.

If we want to hide the Chatter Messages from the Form view then we will do the following configuration in the user configuration.

In the Above screen we have configured for the Hide Chatter. so once we check with the user then it will hide the Chatter Messages.

Hide Conversation Messages

Currently we can see this below Conversation Messages for the user.

If we want to hide the Conversation Messages from the specific user then we will do the following configuration in the user configuration.

In the Above screen we have configured for the Hide Conversation. So once we check with the user then it will hide the Conversation.

Hide Developer Mode

Here, we can see this below Developer Mode for the user.

If we want to hide the Developer mode from the specific user then we will do the user configuration.

In the below screen we have configured for the Hide Developer Mode. So once we check with the user then it will hide the Debug Mode(Developer Mode).

Hide Search Views(Filters,Group By, Favorites)

Here, we can see the Search Views(Filters,Group By,Favorites) for the user.

Hide Filters

If we want to hide the “Filters” from the specific user then we will do the following user configuration.

In the Above screen we have configured for the Hide Filters. So once we check with the user then it will hide .

Hide Group By

If we want to hide the "Group By" option from a specific user, we can apply a similar configuration as we do for filters.

In the Above screen we have configured for the Hide Group By. So once we check with the user then it will hide .

Hide Favorites

If we want to hide the "Favorites" option from a specific user, we can apply a similar configuration as we do for Filters and Group by.

In the Above screen we have configured for the Hide Favorites. So once we check with the user then it will hide .

Hide Chatter, Conversation, Developer mode based on user and model

Here, we can see in the Sales Model the Chatter, Conversation, Developer mode for the user.

1. Hide Chatter

If we want to hide the “Chatter” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide a chatter, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide Chatter. So once we check with the user and model then it will hide.

2. Hide Conversation

If we want to hide the “Conversation” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide a Conversation, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide Conversation. So once we check with the user and model then it will hide.

3. Hide Developer mode

If we want to hide the “Developer mode” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide a Conversation, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide Developer mode. So once we check with the user and model then it will hide.

Hide Filters, Group By, Favorites based on user and model

Here, we can see the Filters,Group By, Favorites for the user and model.

1. Hide Filters

If we want to hide the “Filters” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide a Filters, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide Filters. So once we check with the user and model then it will hide.

2. Hide Group By

If we want to hide the “Group By” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide the group by, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide group by. So once we check with the user and model then it will hide.

3. Hide Favorites

If we want to hide the “Favorites” from the specific user and specific model then we will do the following user configuration.
First, we need to add a model in which we want to hide the Favorites, then click on the checkbox as shown in the image below.

In the Above screen we have configured for the Hide Favorites. So once we check with the user and model then it will hide.

Hide Buttons/Tabs based on user and model

If we want to hide the Buttons and Tabs from the specific user and specific model then we have to configure the button and tab.
For a configuration go to Settings>> Technical>> Button/Tab
Add a model name and click on “Fetch Button and Tab”.

Once we click on the button(Fetch Button and Tab) it will fetch all the buttons and tabs for the selected model.

1. Hide Buttons

After Configuration go to the users, select the specific user in which we want to hide buttons
Go to Access Management>> Button/tab access

Select here model name (which we have configured)and based on the model selected it will display a button and select which button we want to hide from the user.

Here we have selected the button “SEND BY EMAIL”.
Before configuration we can see this “SEND BY EMAIL” button

After configuration this button will get hide

2. Hide Tabs

After Configuration go to the users, select the specific user in which we want to hide tabs
Go to Access Management>> Button/tab access

Select here model name (which we have configured)and based on the model selected it will display tabs and select which Tab we want to hide from the user.

Here we have selected the Tab “Sales & Purchase”.
Before configuration, we can see this “Sales & Purchase” tab in Contacts Model

After configuration, this tab will be hidden

If we want to hide all tabs from any model at that time, we need the same configuration as shown in below
Here I have selected the model name (which we have configured), and based on the model selected, it will display tabs and select which Tab we want to hide from the user.

Here we have selected the All Tab of “Sales Order”.
Before configuration, we can see all the tabs in “Sales Order” Model

After configuration, this tab gets hidden