What are queues in salesforce?
=> Queues are used to assign to records that doesn't have any user as an owner.
=> Users who have access to the queue are called as queue members.
=> Queue members can examine records in the queue and claim ownership of one's they want.
=> Only supported for cases, leads, service contracts and all the custom objects in salesforce.
=> Records can be assigned to a queue by manually changing the owner field of record or with the help of assignment rule.
How records will be accessed if its owner is a queue?
=> Queue members and users above them in the role hierarchy will always have access to record in
that queue.
=> OWD also defines the access to the objects records in queue :
________________________________________________________________________________
If we set public read/write/transfer | Any user can view and take ownership(only for leads, cases).
________________________________________________________________________________
If we set public read/write or public | Any user can view but can take ownership only from queues of
read only | which they are member.
_________________________________________________________________________________
If we set as private | only members can view and take ownership of records.
_________________________________________________________________________________
Important points to remember:
--> A single queue can have records of multiple objects which we call us supported objects.
--> Regardless of the sharing model users must have the edit permission to take the ownership of records in queues of which they are already a member.
--> Admin, users with "modify all" object level permission for the respective object and users with "modify all data" permission can view and take ownership of records from any queues regardless of the sharing model or their membership in queue.
--> Queue members can be changed by 1. Admin 2. Person with " Manage[object name]" privilages.
--> Before deleting a queue re-assign its records to another owner and remove it from any assignment rule.
=> Queues are used to assign to records that doesn't have any user as an owner.
=> Users who have access to the queue are called as queue members.
=> Queue members can examine records in the queue and claim ownership of one's they want.
=> Only supported for cases, leads, service contracts and all the custom objects in salesforce.
=> Records can be assigned to a queue by manually changing the owner field of record or with the help of assignment rule.
How records will be accessed if its owner is a queue?
=> Queue members and users above them in the role hierarchy will always have access to record in
that queue.
=> OWD also defines the access to the objects records in queue :
________________________________________________________________________________
If we set public read/write/transfer | Any user can view and take ownership(only for leads, cases).
________________________________________________________________________________
If we set public read/write or public | Any user can view but can take ownership only from queues of
read only | which they are member.
_________________________________________________________________________________
If we set as private | only members can view and take ownership of records.
_________________________________________________________________________________
Important points to remember:
--> A single queue can have records of multiple objects which we call us supported objects.
--> Regardless of the sharing model users must have the edit permission to take the ownership of records in queues of which they are already a member.
--> Admin, users with "modify all" object level permission for the respective object and users with "modify all data" permission can view and take ownership of records from any queues regardless of the sharing model or their membership in queue.
--> Queue members can be changed by 1. Admin 2. Person with " Manage[object name]" privilages.
--> Before deleting a queue re-assign its records to another owner and remove it from any assignment rule.
No comments:
Post a Comment