Feature Request: Segregated Permissions for Account Settings
Y
Yousef Ahmad-OW
Objective:
To implement a more granular permissions system for account settings in Go High Level, allowing admins to individually control access to specific settings (e.g., calendar settings) rather than a single toggle that enables or disables all account settings.
Feature Description:
Create distinct permission toggles within the user roles and permissions settings that allow admins to enable or disable access to individual components of account settings. For instance, calendar settings should be separate from other account settings, providing more control over user permissions.
Implementation Details:
Granular Permission Toggles:
Introduce separate permission options under the “Account Settings” category, such as:
Calendar Settings Access: Control over calendar visibility and updates.
Notification Settings Access: Control over notification preferences.
Profile Management Access: Control over personal profile details.
Integrations Access: Control over third-party integrations.
User Interface Adjustments:
Update the permissions management interface to include checkboxes or toggles for each specific setting under account settings, allowing admins to customize user access based on their roles.
Dependency Management:
Ensure that if an individual setting is disabled (e.g., Calendar Settings Access), the user cannot view or modify their calendar settings. This should be clearly indicated in the user interface.
Feedback Mechanism:
Provide a notification or message to users when they attempt to access a setting they do not have permission for, explaining that the restriction is based on their role permissions.
Benefits:
Increases security by ensuring users only have access to the settings relevant to their roles.
Enhances flexibility for organizations by allowing tailored permissions based on user responsibilities.
Reduces the risk of unintentional changes to important settings, leading to better account management.
Log In