Granular Object Association Permissions

Status: Not Currently Planned

Status history

Under Permission Settings > CRM Tools there is a toggle for Edit Associations. Currently it is all or nothing; however for our organization this poses some problems.

We want to preserve a user’s ability to associate parent/child companies, or association labels for contacts. But we don’t want them to edit associations with Tickets, Services, Courses, and a few of our Custom Objects, as these are part of sensitive automations and processes.

There can be many permutations of object associations, I’m aware. Ideally we would actually welcome that degree of control, however a compromise could be an object blocklist; this user cannot change any association that involves these objects in any form. This would reduce user interface complexity and ultimately serve our purposes.

+1. Our sales reps need to be able to edit deal/contact associations but they shouldn’t be able to edit, for example, Ticket associations.

IMO Best to remove visibility of the card if you don’t want Users messing with the associations.

Thanks for laying this out clearly. The use case makes sense: the current Edit Associations toggle is binary, and that creates real friction when some associations are tied to sensitive automations you don’t want users touching.

This isn’t something we’re planning to tackle in the near term. The permutation space for object-level association permissions is significant, and we’d want to get the model right before building it.

We’ll keep this thread as a signal as we think about where to take association controls.

+1 to this as well