User roles and user criteria permissions for mobile apps
Summarize
Summary of User Roles and User Criteria Permissions for Mobile Apps
User roles and user criteria permissions are essential access control mechanisms in mobile apps that allow you to define user access and visibility of app components. They enable you to tailor the user experience based on roles or specific user criteria, enhancing the app's functionality for different groups within your organization.
Show less
Key Features
- User Roles Permissions: Control access to features and components for defined audiences. The admin role has access to all features, and role inheritance simplifies management by allowing additional roles to be assigned based on user status changes.
- User Criteria Permissions: Grant access to app components based on specific user attributes such as department or location. This allows for dynamic visibility changes, like updating access to content when users relocate.
- Component Association: Different components may be associated with either user roles or user criteria, but not both simultaneously in Mobile App Builder. In the web-based UI, both can be defined, with visibility determined by the Access Control Mechanism field.
- Offline Support: Both user roles and user criteria are supported in offline mode, ensuring consistent access control regardless of connectivity.
Key Outcomes
By effectively implementing user roles and user criteria permissions, organizations can manage visibility and access efficiently, ensuring that users receive relevant content tailored to their roles or criteria. This capability is vital for maintaining operational efficiency and enhancing user experience within mobile applications.
User roles and user criteria permissions are access control mechanisms that enable you to define roles or segment users into groups within the mobile platform. With these permissions, you can show or hide different components of your mobile app to either individuals or groups.
User roles permissions
User roles control access to features and components within mobile apps for defined target audiences. The admin role provides access to all features and capabilities.
After access has been granted to a role, all the groups or users assigned to the role are granted the access. Use role inheritance to group related permissions, making it easier to manage and assign roles. For example, if an employee has been promoted to a sales manager position, you can allocate additional roles to the employee to reflect their new position.
User role records are stored in the Roles [sys_user_role] table. For more information, see Managing roles.
For a list of all the components where you can define user roles and user criteria, see Mobile components where user roles and user criteria permissions apply. Some components apply to both user roles and user criteria, whereas others are mutually exclusive.
User criteria permissions
User criteria permissions are an access control mechanism that enables you to grant users access to mobile app components, based on categories such as departments, locations, or company. User criteria records define conditions that are evaluated against user records. When a user criteria is defined, records are only visible to users who pass the defined conditions.
With user criteria permissions, you can change information within a single area of a group to update all users' details associated within that group. For example, a company relocates, and the management requires that users in the new location have access to different mobile content. Admins can update the user criteria permissions, so that this new content is displayed to all users in this group.
User criteria records are stored in the User Criteria [user_criteria] table.
For a list of all the components where you can define user roles and user criteria, see Mobile components where user roles and user criteria permissions apply. Some components apply to both user roles and user criteria, whereas others are mutually exclusive.
General guidelines for user roles and user criteria in mobile apps
- When defining user roles and user criteria, careful planning is required to ensure that components are associated with the correct access control mechanism.
- Some components can be associated with either user roles and user components, whereas other components are associated with one access control mechanism. For a list of how the components are associated, see Mobile components where user roles and user criteria permissions apply. For example, you can apply user roles to screens and functions. Alternatively, you can apply navigation tabs and icon section destinations to user criteria.
- You can’t select both user roles and user criteria as access control mechanisms for a component in Mobile App Builder. However, in the web-based UI both user roles and user criteria can be defined for a component. In this situation, the operational mechanism is the value defined in the Access Control Mechanism field of the record.
- Both user roles and user criteria are supported in offline.