I would like to suggest adding the ability to restrict Custom Objects based on Roles and Permissions inside HighLevel.

As more businesses use Custom Objects to manage important data, not every user should have access to every object or every record. Different team members may need different levels of access depending on their role.

For example, a sales user may need access to lead-related Custom Objects, while a manager may need access to financial, operational, or reporting-related Custom Objects. In some cases, certain users should only be able to view records, while others should be able to create, edit, delete, or manage them.

The ideal improvement would be:

Admins can control which roles can access each Custom Object

Admins can set view, create, edit, delete, and manage

Permissions can be assigned by role or individual user

Sensitive Custom Objects can be hidden from unauthorized users

Permissions apply consistently across desktop, mobile app, workflows, reporting, and contact records

This would be very useful for agencies, sales teams, real estate teams, medical clinics, service businesses, SaaS companies, and any organization using Custom Objects to manage private or role-specific data.

Adding role-based permissions for Custom Objects would improve data security, reduce accidental changes, protect sensitive business information, and make Custom Objects more practical for larger teams.