In the new role-based permissions system for Zendesk Sunshine, the endusercan_read flag has been deprecated. Any customers who had this flag enabled on their objects and relationships will be automatically migrated to the new system. The migration process includes setting the read permission to true for end users on the relevant objects or relationships, ensuring a smooth transition without losing existing access settings.
This change simplifies the management of end user permissions by consolidating them into the new role-based permissions framework.
Zendesk has introduced new role-based permissions for Sunshine custom objects, allowing more granular control over access. Previously, agents had unrestricted access to all records, and end users had limited read access based on a flag. Now, admins…
Role-based permissions in Zendesk Sunshine now allow admins to control agents' access to records more precisely. Previously, agents had full access to all records under all objects and relationships. With the new permissions, admins can define…
End user permissions in Zendesk Sunshine have been expanded to allow more detailed access control. Previously, end users could only read records based on the endusercan_read flag. Now, admins can set any combination of create, read, update, and…
The default policy for role-based permissions in Zendesk Sunshine remains unchanged. Admins have full access to all records, agents have full access to all records, and end users have no access to any records. This default setup ensures that only…
RBAC, or role-based access control, policies in Zendesk Sunshine define the create, read, update, and delete (CRUD) permissions for agents and end users separately. These policies apply to all records under a given object type or relationship type,…