Skip to main content
added 26 characters in body
Source Link
Eric
  • 54.6k
  • 11
  • 105
  • 196

I would start by checking access for the Account object for the profile. Perhaps, you cloned an existing profile that did not have access to the Account object to begin with. Also, consider your Organization Wide Defaults. Remember that permission sets can only grant access (to a record) not restrict (access to) it. Keep that in mind when assigning it to a user.

I would start by checking access for the Account object for the profile. Perhaps, you cloned an existing profile that did not have access to the Account object to begin with. Also, consider your Organization Wide Defaults. Remember that permission sets can only grant access not restrict it. Keep that in mind when assigning it to a user.

I would start by checking access for the Account object for the profile. Perhaps, you cloned an existing profile that did not have access to the Account object to begin with. Also, consider your Organization Wide Defaults. Remember that permission sets can only grant access (to a record) not restrict (access to) it. Keep that in mind when assigning it to a user.

Source Link
VanAlfredo
  • 369
  • 3
  • 15

I would start by checking access for the Account object for the profile. Perhaps, you cloned an existing profile that did not have access to the Account object to begin with. Also, consider your Organization Wide Defaults. Remember that permission sets can only grant access not restrict it. Keep that in mind when assigning it to a user.