AgileApps Support Wiki Pre Release

Difference between revisions of "Record Level Visibility"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 10: Line 10:
==Working with {{PAGENAME}}==
==Working with {{PAGENAME}}==
{{TenantCapability|{{PAGENAME}}|off|off|}}
{{TenantCapability|{{PAGENAME}}|off|off|}}
=== Setting Up Record Level Visibility ===
=== Setting Visibility Criteria on a Record ===


<noinclude>
<noinclude>

Revision as of 20:48, 9 September 2015

WorkInProgress.gif

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

Warn.png

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

Lock-tiny.gif

Setting Up Record Level Visibility

Setting Visibility Criteria on a Record