Restrict inbound/outbound emails, visible to only specific role users

SRE
Tera Expert

Hi,

 

Restrict inbound/outbound emails(sys_email) and visible to only specific role users and which should not impact on task table in activity

Tried Business Rule run before on Query, able to restrict but emails are not processing. Also tried ACL's not working as expected. 

 

Tried communities, didn't find any proper link. Appreciate your help on this 

 

Thanks,

Sre

6 REPLIES 6

OlaN
Giga Sage
Giga Sage

Hi,

Can you please explain your use case, and what you want to achieve in more detail?

There are already OOB ACLs that, for example, grant read access only to email records that are attached to task you are assigned to.

SRE
Tera Expert

There are some sensitive emails sent or received , which no one should see only security_admin role users should see the emails.

or

if cannot restrict with role, at least only recipient should see their respective emails and received emails should see by only security admin users.

 

Thanks,

Sre

In that case I would suggest to put these emails into records that are assigned to a specific group, and only allow to read records in this group if you are a member of the group.

nayanawadhiya1
Kilo Sage

Hello,

Below is the configuration for show/hide the emails in activities - 

There is a system property named glide.ui.activity.email_roles enables administrators to control which roles can see emails in the activity formatter.

 

To configure this property:

 

  1. Navigate to System Properties > UI Properties.
  2. Locate the following property: List of roles (comma separated) that can view emails in the Activity Formatter when "Sent/Received Emails" are included.
  3. Add roles to the property, separated by commas. These are the only roles that can see emails in the activity formatter. All other roles are blocked from seeing emails. If no roles are listed, all users can see emails.The itil role is on the list by default.
  4. Click Save.

And if this the thing you are looking for then go for it.
Otherwise you can explain your use case in depth.