6 réponses
Thank again, Robin. I did some testing in my dev org.
My hypothesis: If OWD is set to Private or Public read for Accounts, then activiting territory management, activating CRED for accounts in territory, will NOT give a user assigned to the territory, Edit or Delete access, to Account records shared in that territory.
Steps to repeat:
-Created a custom profile with Create and Read access to accounts
-Created new user and assigned user the custom profile mentioned above
-Change OWD for Accounts to Public Read
-Created a Territory Type and Territory Model
-For Account Access: Enabled View and Edit for Accounts in territory
-Added two accounts to Terriotry
-Logged in as newly-created user.
Expected result:
-New user would not be able to have edit access to account, as her profile does not give her edit access to the object
Actual result:
--New user would not be able to have edit access to account, as her profile does not give her edit access to the object
