We've implemented Audience Based Access Control (ABAC) for all types of content (Page, Event, Album) within Simpplr. This new feature empowers content creators to control content visibility by assigning relevant audiences.
A "restricted content" section has been added to the content creation flow and editing screens, as illustrated in the screenshot below.
Restrict content to an audience:
Here, the Browse audience modal will allow the content creator to choose the applicable audience who should see this content.
Public site: Audience categories and their audience hierarchy, and site’s system audience will be visible in the audience picker.
Private site: Only the site’s system audience (e.g. site members and followers) will be displayed.
Permissions: Any user who can create content will be able to restrict the access of the content.
Standard users, site managers, site owners, site content managers, feature owner/admin/manager of Manage site ACG:
Can add any existing audience or sub audiences displayed in the audience picker modal based on the target audience and site type of the site.
Can also create sub audiences within this audience picker modal.
Content will continue to reside within sites. However, content can now be restricted to a specific audience, making it visible only to that audience, with certain exceptions as follows:
Restricted content is always visible to the author in Manage content screens and search results even if author is not part of the target audience of the content.
Restricted content is everywhere visible to the users having manage site permission i.e. Site managers, Site owners, Site content managers or Feature owner/Admin/Manager of Manage site ACG.
Based on these rules, content will be visible everywhere in the system.
Content that has restricted access will now be marked with a lock icon within the Manage content screens (accessible via Manage > Content or Manage site > Content). This update helps managers easily identify restricted content.
We are also allowing managers to filter the content using Restricted content in these screens.
Content designated as "must read" is restricted to the specific audience for whom it is visible. It cannot be extended to a more granular sub-audience level.
Notifications can be sent to the audience of the restricted content. They cannot, however, be extended to more granular sub-audience level.
Site owners/managers will see a new tab within Manage site to show the audience within a site. This is visible to users having manage site permission by ACG - Feature owner, admin, manager and also to site managers/site owners.
We have made file management smarter and more consistent with content access rules. With this update, files automatically align to the restriction status of the content they’re attached to, while still giving you flexibility to override in certain cases. Clear banners, toggles, and warnings ensure you always know the impact before making changes.
Files attached to unrestricted content remain accessible to all site members
Files attached to restricted content now inherit the same restrictions by default
You can override file restrictions in certain cases, but we’ll guide you with clear banners and toggles so you understand the impact
New files
When added to unrestricted content → files are open to all site members
When added to restricted content → files default to restricted. You will have the option to make them unrestricted if needed
Existing files
If a file is already used in unrestricted places, you cannot make it restricted
If a file is already used in restricted places, we’ll warn you before making it unrestricted, since this will affect those other contents
If a restricted file is added to unrestricted content or shared in the feed, we’ll notify you that it will become unrestricted.
Content edits
When you change content from unrestricted → restricted, attached files are automatically evaluated and updated according to the rules above
Similarly, when you change restricted → unrestricted, files are reassessed to match the new access
Clear in-app guidance
Info banners and toggles guide you through the impact of each action, so you always know who will gain or lose access
The file browser modal now highlights restrictions when selecting files, helping you make the right choice before attaching.
These enhancements ensure that files always stay aligned with content access which helps in keeping sensitive files secure and avoiding accidental exposure, while still giving you flexibility where needed.
Scenario (S) | Preconditions | Steps | Expected result |
S1 – Attach new file to unrestricted content | Content = Unrestricted | Create/edit content → Attach a new file | File is unrestricted → Everyone with site access can see/use it |
S2 – Attach new file to restricted content | Content = Restricted | Create/edit content → Attach a new file | File defaults to restricted → User can mark as unrestricted → If kept restricted: only target audience sees it → If unrestricted: site-wide users see it |
S3 – Attach existing file (unused anywhere) to restricted content | File exists in site only, not attached elsewhere | Create/edit restricted content → Attach file | Show toggle option → User can mark file as restricted |
S4 – Attach existing file used in unrestricted places | File already attached to unrestricted content/sites/feed | Create/edit restricted content → Attach file | Show info banner: "File cannot be restricted since it’s used in unrestricted places" |
S5 – Attach restricted file already associated with other restricted content | File is restricted & attached to another restricted content | Create/edit restricted content → Attach file | Toggle = ON (restricted) by default → If toggled OFF (unrestricted): Show warning banner: "Unrestricting will impact other restricted content" |
S6 – Attach restricted file to unrestricted content | File already marked restricted | Create/edit unrestricted content → Attach file | Show info banner: "This will make file unrestricted" → Only option: Remove file if user wants to keep it restricted |
S8 – Content changed from unrestricted → restricted | Content initially unrestricted with files | Edit content → Mark as restricted | Evaluate file restrictions per S2–S5 → Render accordingly |
S9 – Content changed from restricted → unrestricted | Content initially restricted with files | Edit content → Mark as restricted | Steps
|