🔐 Role-Based Access Control (RBAC) Overview

Role-Based Access Control helps manage what users can see, create, or update in the app depending on their role. This ensures users only access the parts of the app they are allowed to.

1. ✅ Role Configuration

Each user role (like RH, ASM, etc.) has permissions assigned to it. (Livspace Mobile Controller RBAC).

Key Points:

• Enable: Turns on access for the role.

• Role: The name of the user group.

• View / Create / Update Modules: Lists what parts of the app this role can see or work with.

Example:

• Role RH has access to create records in all modules like Partner, Property, Journey Plan, and Dealer Journey.

• Role BDhas access to create records in modules like Partner, Journey Plan, and Dealer Journey but not Property.

2. 📋 Menu Items

This section sets up what menu options appear for a specific module. (LIXIL Mobile Controller RBAC).

Key Points:

• module_name: The main module.

• menu_items: The submenu visible to the user.

3. 🔍 Default Filters

Filters help show only relevant data to users automatically. (LIXIL Mobile Controller RBAC).

Key Points:

• Example: Show records where Name starts with a certain text and Dealer_Email equals a specific value.

This helps the user avoid manual searching.

4. 👤 User Information

This links user identity with what data they should see. (LIXIL Mobile Controller RBAC).

Key Points:

• Tells the system which user field to use for filtering data.

• Example for AMC and Contacts modules:

5. ⚙️ User Accessibilities

Extra settings that turn features ON or OFF for a user. (LIXIL Mobile Controller RBAC).

• Globally Both features are turned ON for whole application.

• But for specific role like Dealer, Both features are turned OFF (0).