How the visibilty of interaction records is controlled in Human Resource Core Application scope

[Vdevmat33]

Hi Team,

Could you please suggest how the visibilty of interaction records is controlled in Human Resource Core Application scope.

For example, only user with HR Admin role can view the records in Human Resources Core application scope. Observed that there no acl or business rule on interaction table which suggests same.

Would like to know how this is implemented and what configurations are used here.

We were planning to implement same for other custom application.

Thanks in advance!

[Ankur Bawiskar]

@Vdevmat33 

visibility of interaction should be based on table.None READ ACL

What's your business requirement?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Kieran Anson]

Hi,

The interaction table is somewhat unique as it has the 'application' field which points to sys_scope. This means that scope security is enforced and scoped ACLs are required to read data, even if a global ACL provides access.

So, OOB, HR interactions are secured and only accessible to those with a sn_hr role. HOWEVER, for this to apply, HR Agent Workspace has to be used to set the 'Application' field correctly. 

[Vdevmat33]

Thanks @Kieran Anson 

We have case where access analyzer shows read access as blocked for an interaction record but there is no read acl displayed in the results. Also there is no acl present in application scope on the interaction record. Application scope is Human Resource: Core. The interaction record is visible for user with hr admin role. 

There is no query business rule on interaction table as well. Could you please suggest which configuration might be responsible for blocking/granting this access to hr admins.

Thanks!

[Kieran Anson · Accepted solution]

What roles does the user have that is unable to view the record? Do they have a hr scoped role?