Difference between revisions of "Record Level Visibility"
imported>Aeric |
imported>Aeric |
||
| Line 4: | Line 4: | ||
--criteria selection | --criteria selection | ||
--add performance warning to tenant capability | |||
{{Warn|<br>When you restrict visibility, it is entirely possible to cut yourself out of the loop. In some cases, that is the desired and intended behavior. But if you restrict visibility to a team you don't belong to, restrict it to a list of users that does not include yourself, or restrict it to a role you do not have, then at that point you can no longer see the record, even if you own it. (But an admin can still see it, and re-set visibility.)}} | {{Warn|<br>When you restrict visibility, it is entirely possible to cut yourself out of the loop. In some cases, that is the desired and intended behavior. But if you restrict visibility to a team you don't belong to, restrict it to a list of users that does not include yourself, or restrict it to a role you do not have, then at that point you can no longer see the record, even if you own it. (But an admin can still see it, and re-set visibility.)}} | ||
Revision as of 18:45, 9 September 2015
Work In Progress:
This page is under development.
About Record Level Visibility
In general, anyone whose role gives them access to an object can see any of the records it contains. But with Record Level Visibility you can specify who is allowed to see each record, one by one. With no visibility criteria specified, everyone who can access the object can see the record. But with visibility criteria specified, only users who match the specified criteria can see it. Users who not match the specified criteria do not see the record in list views, search results, or reports. And if they happen to have the URL that goes directly to that record, they get a "record not found" error when they visit that URL.
--criteria selection --add performance warning to tenant capability
Warning:
When you restrict visibility, it is entirely possible to cut yourself out of the loop. In some cases, that is the desired and intended behavior. But if you restrict visibility to a team you don't belong to, restrict it to a list of users that does not include yourself, or restrict it to a role you do not have, then at that point you can no longer see the record, even if you own it. (But an admin can still see it, and re-set visibility.)
Working with Record Level Visibility
- The Record Level Visibility option is enabled by your Service Provider.
- The default single sign-on setting on on-premises installation is off.
- The default single sign-on setting on the cloud is off. (Contact Support to make changes.)
