For which scenario we need to use apex managed sharing?
up vote
2
down vote
favorite
We can control access to data at many different levels (OWD, Sharing Rule, Role Hierarchies) in salesforce. However, in which case we need to use apex managed sharing? Can you please explain with examples.
apex-sharing
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
add a comment |
up vote
2
down vote
favorite
We can control access to data at many different levels (OWD, Sharing Rule, Role Hierarchies) in salesforce. However, in which case we need to use apex managed sharing? Can you please explain with examples.
apex-sharing
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
We can control access to data at many different levels (OWD, Sharing Rule, Role Hierarchies) in salesforce. However, in which case we need to use apex managed sharing? Can you please explain with examples.
apex-sharing
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
We can control access to data at many different levels (OWD, Sharing Rule, Role Hierarchies) in salesforce. However, in which case we need to use apex managed sharing? Can you please explain with examples.
apex-sharing
apex-sharing
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
edited Nov 10 at 7:17
Santanu Boral
30.1k52152
30.1k52152
asked Nov 10 at 6:02
SFDCLearneR
716
asked Nov 10 at 6:02
SFDCLearneR
716
asked Nov 10 at 6:02
SFDCLearneR
716
716
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
A simple use case which comes to my mind could be as follows:
At an organization, HR person conducts the interviews of candidates. HR person wants to share candidate's profile to an Interviewer.
Consider, OWD of Candidate object is Private.
Here, you can think that HR person would always create candidate record and in the candidate object, a Lookup field can be used to store Interviewer.
So, in the beginning no other person can see candidate information. When HR person selects the Interviewer (User) from the Lookup and saves the record then that record will be visible to Interviewer to take interview of the Candidate.
During sharing record creation following needs to be specified:
- objectNameAccessLevel - (Read, Edit or All) and for the above use case it will be
Read
- ParentID - This will be Candidate Record Id
- RowCause - For purpose of interview
- UserOrGroupId - Interviewer Id (user)
For more information, refer Sharing a Record Using Apex
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f238934%2ffor-which-scenario-we-need-to-use-apex-managed-sharing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
A simple use case which comes to my mind could be as follows:
At an organization, HR person conducts the interviews of candidates. HR person wants to share candidate's profile to an Interviewer.
Consider, OWD of Candidate object is Private.
Here, you can think that HR person would always create candidate record and in the candidate object, a Lookup field can be used to store Interviewer.
So, in the beginning no other person can see candidate information. When HR person selects the Interviewer (User) from the Lookup and saves the record then that record will be visible to Interviewer to take interview of the Candidate.
During sharing record creation following needs to be specified:
- objectNameAccessLevel - (Read, Edit or All) and for the above use case it will be
Read
- ParentID - This will be Candidate Record Id
- RowCause - For purpose of interview
- UserOrGroupId - Interviewer Id (user)
For more information, refer Sharing a Record Using Apex
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
add a comment |
up vote
5
down vote
accepted
A simple use case which comes to my mind could be as follows:
At an organization, HR person conducts the interviews of candidates. HR person wants to share candidate's profile to an Interviewer.
Consider, OWD of Candidate object is Private.
Here, you can think that HR person would always create candidate record and in the candidate object, a Lookup field can be used to store Interviewer.
So, in the beginning no other person can see candidate information. When HR person selects the Interviewer (User) from the Lookup and saves the record then that record will be visible to Interviewer to take interview of the Candidate.
During sharing record creation following needs to be specified:
- objectNameAccessLevel - (Read, Edit or All) and for the above use case it will be
Read
- ParentID - This will be Candidate Record Id
- RowCause - For purpose of interview
- UserOrGroupId - Interviewer Id (user)
For more information, refer Sharing a Record Using Apex
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
A simple use case which comes to my mind could be as follows:
At an organization, HR person conducts the interviews of candidates. HR person wants to share candidate's profile to an Interviewer.
Consider, OWD of Candidate object is Private.
Here, you can think that HR person would always create candidate record and in the candidate object, a Lookup field can be used to store Interviewer.
So, in the beginning no other person can see candidate information. When HR person selects the Interviewer (User) from the Lookup and saves the record then that record will be visible to Interviewer to take interview of the Candidate.
During sharing record creation following needs to be specified:
- objectNameAccessLevel - (Read, Edit or All) and for the above use case it will be
Read
- ParentID - This will be Candidate Record Id
- RowCause - For purpose of interview
- UserOrGroupId - Interviewer Id (user)
For more information, refer Sharing a Record Using Apex
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
A simple use case which comes to my mind could be as follows:
At an organization, HR person conducts the interviews of candidates. HR person wants to share candidate's profile to an Interviewer.
Consider, OWD of Candidate object is Private.
Here, you can think that HR person would always create candidate record and in the candidate object, a Lookup field can be used to store Interviewer.
So, in the beginning no other person can see candidate information. When HR person selects the Interviewer (User) from the Lookup and saves the record then that record will be visible to Interviewer to take interview of the Candidate.
During sharing record creation following needs to be specified:
- objectNameAccessLevel - (Read, Edit or All) and for the above use case it will be
Read
- ParentID - This will be Candidate Record Id
- RowCause - For purpose of interview
- UserOrGroupId - Interviewer Id (user)
For more information, refer Sharing a Record Using Apex
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
edited Nov 10 at 12:32
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
answered Nov 10 at 7:14
Santanu Boral
30.1k52152
30.1k52152
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
add a comment |
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
Hi Santanu Boral, Thank you for your explanation. We can able to handle above requirements using queues with workflow rule right?
– SFDCLearneR
Nov 10 at 9:39
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f238934%2ffor-which-scenario-we-need-to-use-apex-managed-sharing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
