Overview
App Area Availability Rules let administrators customize the Mobaro Mobile App experience by restricting access to specific sections for designated user groups. This feature is ideal for tailoring app functionality based on roles and operational requirements, ensuring users only see the tools relevant to their tasks.
Creating App Area Availability Rules
Follow these steps to set up and configure an App Area Availability Rule:
Step 1: Access the App Area Availability Rules Section
Go to the Configuration Section
In the Mobaro Backend, navigate to 
Configuration from the sidebar.
Open App Settings
From the top navigation bar, select App Settings.
Locate the App Area Availability Rules Panel
In the right-hand panel, find App Area Availability Rules and click the + Add area availability role button.
Step 2: Configure the Rule
Provide a Descriptive Name
Enter a name that reflects the rule’s purpose (e.g., "Trainee Restrictions").
optional Assign User Groups
Add the relevant User Groups to which this rule will apply.
Leave this field empty to apply the rule to all users.
Disable Specific App Areas
Toggle the switches for the areas you want to restrict. Available options include:
Save the Rule
Click Save to finalize your settings. The rule will immediately apply to the selected user groups or all users if no groups were specified.
Reminder: Ensure at least one app area is disabled; otherwise, the rule will not have any effect.
Managing App Area Availability Rules
Once rules are created, you can edit or delete them as needed.
To edit a rule:
Navigate to Configuration > App Settings.
Locate the rule in the App Area Availability Rules list.
Click the Edit icon next to the rule.
Modify the name, user groups, or disabled areas as required.
Save your changes.
To delete a rule:
Find the rule you want to remove in the App Area Availability Rules list.
Click the Trash icon next to the rule.
Confirm the deletion in the pop-up dialog.
Warning: Deleting a rule immediately restores access to all previously restricted areas for affected users.
Best Practices
Descriptive Names: Use clear, descriptive names for rules to simplify management (e.g., "Trainee Restrictions," "Read-Only Access").
Role-Based Access: Assign rules based on user roles and responsibilities to streamline the app experience.
Regular Audits: Review and update rules periodically to ensure they align with operational changes.
Test Before Deployment: Use a test account within the affected user group to preview the impact of a rule.
Frequently Asked Questions
Q: Can I apply a rule to individual users?
A: No, rules can only be assigned to user groups or applied universally if no groups are selected.
Q: How are conflicting rules handled?
A: If multiple rules apply to the same user group, the most restrictive rule takes precedence.
Q: Can I temporarily disable a rule without deleting it?
A: No, rules must be edited or deleted to change their impact.
Q: Are restricted areas hidden permanently?
A: Areas remain hidden until the rule is modified or removed.