Recent searches


No recent searches

Feature request - roles - configurable custom objects permissions



Posted Oct 11, 2023

It appears that the contributor and light agent roles permit view access to custom objects and are not configurable to be otherwise. On the other hand, these permissions are configurable for other licenses.

I understand that there are serious limitations to access governance with regard to custom objects (ie macro bypass of permissions on other roles), and I assume that is inherent to the architecture. However, since other roles can have their access configured, it seems like this restriction on modifications is arbitrary.

Custom objects could include sensitive data relevant to work done by private groups and should not be accessible to our light agents, contributors, or other members not in the private group. In the same way as ticket access can be customized.

To enforce effective user access governance, the custom object permissions should be configurable for light agent and contributor roles in the same way as ticket access can be customized.

 

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

Custom objects are visible to users that should not have access. While full licenses for agents can have their custom permissions restricted, due to the fixed config of light agents and contributors, admins cannot customize their access to these data assets. 

What problem do you see this solving? (1-2 sentences) 

The lack of customization options for light agent and contributor roles impacts data governance and may expose sensitive data. This limits the usability of the custom objects feature altogether.

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

This is an on-going issue. This impacts the ability for admins to control who access to what data.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

The only workaround presently available is to not use custom objects to store sensitive data.

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

Unlock the light agent and contributor role customization options to allow admins to restrict/customize access to custom object data. At minimum, for the sake of safest data governance, the default should prevent view access.


3

4

4 comments

image avatar

Shawna James

Community Product Feedback Specialist

Hello Matthew, thank you for taking the time to provide us with your feedback. This has been logged for our PM team to review.
 
For future reference, I want to point you in the direction of our product feedback template. This template has been designed by community members and PM's to help users provide the most accurate details for their feature request so that we can better understand your use case and needs. You do not need to update your post now but we would appreciate in the future if you could utilize the template.
 
For others who may be interested in this feature request, please add you support by upvoting this post and/or adding your use case to the the comments below. Thank you again!

0


Shawna James - thanks, I've just updated it

0


image avatar

Shawna James

Community Product Feedback Specialist

Thank you so much Matthew! We really appreciate it. 

0


Still an issue in 2025. Would love to see custom object permissions be configurable for light agent role.

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post