Manage Permissions of Different Group of Pages

Priority

Low

Components

Affects versions

None

Fix versions

2024 M1 Delivery Milestone

2024.Q2.0

Labels

2024.Q2.02024M1_DEVd_23_10d_23_11d_23_12documentation-24Q2-baseline2documentation-24Q3-baselinedocumentation-24q2-baselinefc_24_01fc_24_02fc_24_03quality-analysis

Description

As a Page Creator

I want to be able to manage Permissions for my whole site and also for different group of pages

So that I am able to manage separately the pages that all my users see from the pages that only the members or a specific group see.

Context

There are several challenges regarding the usage of Private Pages, as their behaviour is not very intuitive so the user is confused by it. We would like to be able to give the users the main functionalities Private Pages offer without the need to use them. The main functionalities identified for Private Pages are:

Specific design for these pages.
Guest users are not able to see them.
The specific navigation menu for these pages.
Specific SEO Configuration
Possibility to have different domains for these pages.

We would like to cover all but the last one.

Requirements

Being able to easily identify the public pages from the restricted ones.
Being able to define and manage the default Permissions (Everyone, Member, Specific Role…) for all the pages of the site
Being able to configure and manage Permissions of a whole subtree of pages:
- What is configured at this level would take precedence over the Site configuration.
Being able to configure and manage Permissions of a specific Page:
- What is configured at this level would take precedence over the subtree configuration, and therefore over the Site configuration.
Being able to identify at first sight if a page/subtree of pages is visible for guests.
- To review: Adding a filter to show pages with guest viewer permissions vs no guest viewer permissions.
Being able to manage Page permissions in bulk.

Use Cases	User	Steps
Identifying Guest Visibility for Content Across Various Locations	Content Creator	The user accesses content management features like the page tree, miller columns, stylebook view, and item selector. The system visually distinguishes between pages with Guest View permissions (public) and those without (restricted). This can be achieved through icons (e.g., padlock) or labels displayed next to each page name. Parent page permissions with Guest View should not inherit a locked icon due to child page restrictions. Hovering over the padlock icon (except in the stylebook view) displays a tooltip with the text "Restricted Page." The user can immediately recognise publicly accessible content across various interfaces, streamlining content management and ensuring transparency regarding page visibility Ensure the visual indicators (icons or labels) have sufficient colour contrast and are distinguishable for users with visual impairments. Also, consider providing alternative text descriptions for the icons to enhance screen reader compatibility.
Update Permissions for Multiple Pages at Once (Bulk permissions)	Admin user/ Content creator	The user accesses the page list view. The system allows selecting multiple pages using checkboxes. The user chooses the "Set Permissions" option from the bulk actions menu. The system displays a modal window with options to configure a common permission level for all selected pages. The user confirms the bulk permission update. The chosen permission level is applied simultaneously to all selected pages.
Filtering Pages by Guest Visibility	Admin user/ Content creator	The user accesses the page list or sitemap view. The system provides a filter option for "Guest Visibility." The user selects "Show Pages Visible to Guests" or "Show Pages Not Visible to Guests." The system displays only the pages matching the chosen filter criteria. The user can efficiently review and manage pages based on guest user visibility.
Configuring Permissions for a Specific Page	Admin user/ Content creator/ Page creator	The user opens the edit view for a particular page. The system displays a dedicated "Permissions" section within the page settings. The user selects the desired access level for the specific page. The system displays a message indicating that these settings will override both the default site permissions and any subtree permissions (if applicable). The user saves the page settings. The chosen permission level applies only to the edited page, overriding any inherited permissions from the site or subtree settings.
Identifying Public vs. Restricted Pages	Admin user/ Content creator/ Page creator	The user accesses the page list or sitemap view. The system visually distinguishes between public pages (accessible to everyone) and restricted pages (with specific access controls). This can be achieved through icons, colours, or labels. The user can hover over a page or click on a tooltip displaying the current permission level. The user can easily identify public and restricted pages at a glance.
Setting Default Permissions for the Entire Site	Admin user/ Content creator/ Page creator	The user navigates to the "Permissions" section in the website settings. The system displays options for default access levels (e.g., Everyone, Member, Specific Role). The user selects the desired default permission level for all new and existing pages on the site. The system saves the configuration. All new pages created inherit the default permission settings. Existing pages retain their current permissions unless explicitly modified.
Configuring Permissions for a Subtree of Pages	Admin user/ Content creator/ Page creator	The user navigates to a specific folder or section within the sitemap. The system provides an option to "Set Permissions for this Subtree." The user selects the desired access level for all pages within the chosen subtree. The system displays a confirmation message highlighting that these settings will override the default site permissions for pages within the subtree. The user confirms the configuration. All pages within the selected subtree inherit the newly configured permissions, taking precedence over the default site settings.