1) How does one determine for those who are allowed to use an Org Wide email address (determined by selected profiles tied to the Org Wide email itself), what list views they have access to based on the Org Wide email address? For example, case list views does not allow for profile access, only public groups, roles, and roles and subordintates. Is there no direct tie from the Org Wide email to that of list views, correct?
2) Assuming, based on #1 being a no, that the Email-to-Case email(s) does not directly grant any particular set of users access to various list views? Being that Email-to-Case deals with the case object, depending on the automatic case creation setup in a particular instance of Salesforce, access to list views would depend on users' access to the record type it's created under?
2 respuestas
@Miglena Thanks for the resources! I think a better question for me to start with here would have been what should one consider when adding a new inbound support email address while ensuring all current users who have access to an existing inbound support email address? Below is a list of items we can think of.
- Org Wide Email Address
- Email-to-Case
- List views
- Any workflow/Apex/flow ties
