Employee Newsletter: Improved experience with ABAC visibility

• Overview
• What's changed
• Behavior for ABAC vs non‑ABAC tenants
• How it works in regards to recipient experience
• How it works for creators
• Impact and benefits

Overview

This update improves how restricted content is displayed and handled in Employee Newsletter content blocks. The goal is to make access restrictions clearer and less disruptive for readers, while still preventing users without access from viewing protected content.

These changes apply to:

• Employee Newsletter – Content blocks

• Both ABAC and non‑ABAC tenants (where applicable)

The site-level experience is handled separately and is not covered in this article.

Learn more about ABAC here.

What’s changed?

1. Greying‑out behavior replaced with a clearer visual treatment

Previously, when a newsletter contained content that some users could not access (due to ABAC or standard access controls), those content blocks were greyed out.

Now, the old “greyed‑out” restricted look is replaced with an updated visual treatment (blurred/visually obscured).

2. Restricted indicators hidden in end‑user and preview views

For content blocks where the viewer does not have access:

• End‑user view (what recipients see in the email)

  • The previous “restricted component” that explicitly called out that content was restricted is no longer shown in the email body.

  • Instead, the user sees the new visual treatment of that content block (e.g., blurred/obscured).

• Preview view (what senders/creators see in the newsletter preview)

  • The “restricted” component (pill + message) is removed from the preview as well, and replaced with the updated visual style.

This keeps the layout cleaner while still signaling that content is not available.

3. Updated “Restricted” pill and message (author/editor context)

Within the Employee Newsletter authoring/management experience (not the recipient email itself):

• The “Restricted” pill and message have been updated according to the design to:

  • More clearly indicate which blocks are restricted based on ABAC or standard permissions.

  • Align labels, icons, and text with everyday language used across the product.

These cues help editors quickly identify restricted segments in the newsletter content block configuration.

4. Lock icon replaced with “eye” icon

Across the Employee Newsletter content block interface where restricted content is surfaced:

• The older lock icon has been replaced by an eye icon (typically representing “visibility” or “view access”).

• This aligns restrictions with a more intuitive visual metaphor: users can see that something exists, but they may not be allowed to view its details.

Behavior for ABAC vs non‑ABAC tenants

From the epic comments:

• The blurred/updated interface also appears for non‑ABAC tenants.

• Previously, for non‑ABAC tenants, a greyed‑out restricted component was shown when users lacked access.

• With this change:

  • Non‑ABAC tenants now get the same blurred/updated treatment instead of the old greyed‑out restricted component.

  • The send behavior is unchanged:

    • Users without access still see restricted content represented in the email (via the blurred/obscured block).

    • When they click on that content, they are redirected to the Request membership page (or equivalent access-request flow).

Result: The visual treatment is now consistent across ABAC and non‑ABAC tenants, while the underlying access control remains unchanged.

How it works in regards to recipient experience

When a newsletter contains content (e.g., site content, page, or post) that a recipient does not have permission to view:

1. The restricted content block appears in the email with the new blurred/obscured treatment.

2. The user cannot see the actual content within the email.

3. If they click on that block/link:

   • They are taken to the Request membership (or equivalent access-request) page.

   • From there, they can follow the normal process to request access.

No change to:

• Who can technically access the underlying content.

• How access is granted/denied once they request membership.

How it works for creators

When building or previewing a newsletter:

1. Content blocks that reference restricted content are:

   • Visually called out using the updated “Restricted” pill and messaging in the configuration/authoring experience.

   • Shown with the new visual treatment in preview (rather than the previous “restricted component”).

2. The eye icon is used in place of the lock icon anywhere the user interface indicates visibility/access limitation for these blocks.

3. Editors can still:

   • Include restricted content in newsletters (subject to your governance), and

   • See which parts will be restricted for some recipients.

Impact and benefits

• Cleaner, more modern user interface

  • The new blurred/obscured styling and eye icon are more visually consistent and intuitive.

• Consistent behavior across ABAC and non‑ABAC

  • Both tenant types now use the same restricted-content visual pattern, reducing confusion.

• Reduced friction for readers

  • Recipients still understand that content exists but requires access, and they are guided to the request membership page on click.

• No change to access control

  • Who can or cannot see the underlying content is governed by your existing ABAC or permission settings; this epic changes only the experience and visuals, not the rules.