Content Restrictions
Content Restrictions applies relationship-aware access rules so users only reach content they are allowed to see.
Overview
This module is a supporting access-control layer. It is used when WinnerWare needs to limit content visibility based on who owns the content and which users are allowed to act within that owner's access circle.
This module is not designed as a standalone feature that administrators turn on and configure by itself. It is enabled behind the scenes when another WinnerWare feature depends on restricted access behavior.
Key Features
- Restricts access to content item routes when access rules apply.
- Works in both the public content flow and the admin content-item flow.
- Allows access for the content owner and other approved related users.
- Leaves unrestricted content behavior in place when no access providers are active.
How It Works
When a user opens a content item that passes through the protected content routes, WinnerWare checks whether that user should be allowed to access the item.
In the current implementation, access can remain available when:
- the user is an administrator
- the user owns the content item
- the user belongs to the allowed relationship set for that content owner
This makes the module useful for supervision-style or relationship-based experiences where one user can act on behalf of a defined group of people, but not everyone in the system.
Configuration
| Admin display name | Feature ID | Notes |
|---|---|---|
| Content Restrictions | CloudSolutions.ContentRestrictions | Enabled by dependency only. It is intended to support other features rather than manual rollout. |
Usage
Use this module when another WinnerWare feature needs content visibility to follow business relationships instead of being open to all authenticated users.
Developer Notes
- The module adds an authorization policy and request filter around content item access.
- It relies on relationship-aware user providers from the wider solution to determine which additional users can access an owner's content.
- There is no standalone settings page or editor surface in the current implementation.