1

Within the profile settings, under object settings, then object permissions - I do not see the option to set a profiles object permissions for Tasks, Events, Notes, Users to no access. Appears that I am able to set the field level permissions, though it's unclear why there is not the option to set the object permissions to no access, if there's another place to do this, and if not, if removing access via the fields will have the same results. How to set object permissions to no access for: Tasks, Events, Notes, Users?

Update: In retrospect, might be worth stating the problem that resulted in this question. I am creating a barebones user and have removed links to Tasks, Events, Notes, and Users - but these object are still showing up in searchable fields by objects dropdown for the sidebar search. As I've removed object permissions from other objects, they've been removed from the dropdown, so I believe removing permissions for these objects will have the same results.

  • 1
    Can you contact Salesforce to enable "Organization Wide Defaults" private sharing setting for the USER object as a first means of hiding them..? – bigassforce May 24 '14 at 17:05
  • @user320: Are you saying that I need to contact SF and request that they add the user object to "Setup > Security Controls > Sharing Settings" and then set "Default Access" to Private for the user object? Thanks! – blunders May 24 '14 at 19:22
  • 1
    Yes, this will allow you to hide users from each other, if you really wished your 'barebones user' not to see them. Would be great if we can learn more about the spirit of your requirements. – bigassforce May 24 '14 at 20:06
  • +1 @user320: Thanks, that's what I'll do then, since I don't know any reason why users should be able to see which others configs, beyond maybe supervisors being able to view configs of staff that report to them. – blunders May 24 '14 at 20:12
  • 1
    @user320: In this case, the use of account, contact, opportunity happen to be the core objects that "they" want, which isn't really what I'd suggest, but if that's what they want, that's all they're going to see. As for objects, I just thought of everything as being an object, but it's pretty clear to me at this point that there are a lot of assumptions baked into SF that are not obvious; for example, that all contacts require accounts. Any rate, thanks for asking, and glad that I addressed your question! :-) – blunders May 24 '14 at 21:06
3

Tasks, Events and Notes all have a field named Private (data type boolean) that controls the sharing of these objects. Users visibility would be controlled by hierarchy and entity history. I hope that helps.

| improve this answer | |
  • So, basically the answer is that it's only possible control the sharing of these objects, not access to objects themselves, right, or am I misunderstanding your answer? Here's an example that I just found as a result of your reference to "hierarchy" (which I believe means role hierarchy) that appears to define the factors used to determine access to tasks and events. PS - good luck with your goal of becoming a SF-Dev! – blunders May 24 '14 at 19:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.