Current Limitation:

In HighLevel, users can create Smart Lists but cannot rename or delete them unless they have access to Account Settings. This creates unnecessary friction and administrative overhead, particularly in environments where access to Account Settings is restricted for security, compliance, or operational reasons.

Issue Overview:

Smart Lists are designed as user-centric features, typically used as personal filters or saved views within the Contacts module. It is therefore reasonable and expected that individual users should have full control over the Smart Lists they create.

Feature Request:

Introduce a dedicated permissions section for Smart List management that decouples basic user functionality from full Account Settings access.

Specifically:

✅ Allow users to rename and delete their own Smart Lists

🔒 Restrict the ability to rename or delete shared or global Smart Lists to users with Account Settings permissions

Why This Matters:

Aligns with the expected behaviour of other user-level features (e.g. saved views, filters)

Avoids exposing sensitive account-wide settings to non-admin users

Reduces administrative workload by removing bottlenecks for basic tasks

Enhances day-to-day usability for teams working extensively in Contacts

Encourages cleaner organisation and improved user adoption

Suggested Permission Structure:

Can Manage Own Smart Lists – default: enabled for all users

Can Manage All Smart Lists – default: restricted to users with Account Settings access

Impact:

This small but meaningful change would significantly improve the user experience for operational users while preserving administrative control and system integrity.