In a profile, I have the Account object rights set for
- Read
- Create
- Edit
In the org-wide sharing settings, I have the account object for Default Internal Access set to Public Read Only
What I thought this meant is that by default, all users will have view access to all account records.
And then, if a user of my aforementioned profile is the owner of an Account record OR if the account record is shared with them (via manual sharing or a Sharing Rule that is in place), that user would then have Read, Write, Edit access.
That doesn't appear to be the case though. It seems any user belonging to my profile has read and edit rights to all account records, even those they don't own or are shared with them.
What am I missing? Or where have I gone wrong?
In short, I'm trying to make it so all users can view account records by default, but only owners of the account record or those users with whom the account record is shared (given edit/write privelages through a share) are allowed to edit it.
5 respostas
Mystery solved. I feel stupid for this but I understand how it happened. Long story short, I thought the account object was still editable when in fact it wasn't. I thought it was editable because it showed the pencil mark, even allowed me to type in new values in the fields on the account object. It wasn't until I clicked "save" to commit the change that it said I was blocked from doing so.
I find it a bit odd that if the org-wide setting is for view only AND a profile's object permission is also set to view only, the pencil and ability to type in a different value isn't there at all. But, once edit permission is enabled on the object permission in the profile, ALL account records (even the ones you don't own) will show you the penicl mark on fields and even let you type in different values....only to prevent you from editing when you try to save (if you don't own the record or it isn't shared with you). It gave me the impression I had edit rights on everything.
Lesson learned. I'm hanging my head in shame. Thank you again Dmitry for taking the time to give me some suggestions and help.
