You are here: Reference > Data classes > Access Group data instances > More about Access Group data instances

More about Access Group data instances
 

  1. About 
  2. New 
  3. Layout 
  4. Settings 
  5. Associations 
  6. History 
  7. More... 

When effective

After you save an Access Group form, active requestor sessions on the current node that are associated with that access group are immediately updated. Requestors at other nodes in a cluster are updated when the next system pulse occurs on their node.

Security audits

Using the optional security audit feature, your application can present in the History display which values were added, updated, or removed from the data object, for selected data classes. See How to enable security auditing for rule or data changes.

Facilities provided to unauthenticated (guest) requestors

Guest users—also known as unauthenticated requestors—typically have access to only the rules in the rulesets in the PRPC:Unauthenticated access group, as referenced in the Requestor type instance named pega.BROWSER.

Caution: If you update the pega.BROWSER requestor type to reference a different access group, or update the PRPC:Unauthenticated access group to make additional rulesets available to unauthenticated users, review the Authenticate? check box on the Security tab of each activity in the rulesets. Select this check box for only the activities that guests need to run.

The clipboard for a guest requestor does not include pages for the Operator ID, organization, division, or organization unit.

The default time-out period for an idle guest requestor is one minute.

Notes

Definitions access group, application rule, organization, work pool
Related topics About Operator ID data instances
About Class Group data instances
Org & Security category — Organization landing page
Standard rules Atlas — Initial Access Groups

UpAbout Access Group data instances