Rights UI improvements

Last modified by Thiago Krieck on 2026/11/13 19:22

 XWiki
 Feature
 Idea
 
 
No

Description

 

Summary

Redesign of the rights administration for wikis, sub-wikis and pages:

  • Wiki administration › Rights opens on the Rights Hub, which sums up who can do what and flags problems.
  • One editor serves the wiki and each page. It lists only what is set, with two views: by user or group, and by right.
  • Changes are made in a dialog that explains the effective result, and are saved together after a review.

Current UI

Every rights screen (wiki, Page & Children, Page, Extension Rights, Wikis Creation Rights) is the same table:

  • one row per user or group, one column per right
  • each cell cycles between allowed, denied and not set, and each click is saved immediately

1794569171403-173.png

XWiki 18.9.0, Page & Children rights of a space with 22 groups. Four groups have rights set, but only one of them (Contractors) is on the first page.

Problems

Problem 1. Entries with rights set are lost in the list

Every user and group is listed, whether or not it has rights set.

"When I have set a few custom rights for pages, the groups/users with permissions easily get lost in the long list sorted alphabetically." (forum 18246)

"The UI is impossible to use if there are thousands of users and groups and just a few of them have rights set." (forum 16128)

See also XWIKI-20956.

Problem 2. Users are hard to find, and rights of deleted users are invisible

Users are hard to pick by name. Rights set for deleted users or groups are not displayed, but they still apply.

"When you want to change the access rights for a page […] all you see are user IDs" (XWIKI-19710)

"The page access rights of a deleted user are not displayed and, hence, cannot be removed, but continue to influence the access rights of other users." (XWIKI-21863)

"This situation can (and does) easily happen with Confluence imports […] The UI needs to display all rights that are taken into account, regardless if the user or group exists or not." (forum 17161)

See also XWIKI-9681.

Problem 3. Each click is saved immediately

Multi-step changes pass through intermediate states, and an administrator can lose Admin halfway through.

"Changes are effective the instant he clicks the radio buttons. This also limits exploration from the user because it is an unforgiving UI" (XWIKI-12782, 2015)

See also XWIKI-21064.

Problem 4. Inherited and effective rights are not visible

Nothing shows the rights coming from parent pages or the wiki, or explains why someone has or lacks a right. This is why the Page Rights Viewer and Admin Tools extensions exist.

"When configuring rights to a page and subpages, I don't see what rights are currently inherited from the pages above" (forum 17161)

"It is difficult to understand what are the rights that already apply on page D, and where do they come from." (XWIKI-13403)

"The UI gives you no feedback which rights a user or group has (before or after setting a right)." (forum 16128)

See also XWIKI-2636 (2008) and XWIKI-22897 ("at a glance a user cannot see what rights are assigned to a user or group").

Problem 5. One column per right does not scale

Extension rights and Wikis Creation Rights have their own screens, and every new right adds a column.

"The issue for me is the number of rights that doesn't lend itself to be displayed as columns." (forum 17161)

Problem 6. No overview of rights across the wiki

There is no single place that shows which pages set their own rights, what visitors can do, or what is misconfigured.

"Display groups' rights for each page, which will allow displaying all groups and the type of right on it. […] The same info can be added but for the groups' management page, which will allow knowing the pages administered by this group." (XWIKI-20540)

See also XWIKI-6297, XWIKI-14544 and XWIKI-23744.

Problem 7. Sub-wiki rights are ambiguous

It is unclear whether main-wiki rights and users apply in a sub-wiki, and main-wiki-only rights are still offered.

"Have you checked how to handle displaying rights in case of subwiki when we display local and/or global users? […] It's adding a new layer of complexity" (forum 17161)

"The rights are not visible in the UI of WebPreferences if the group doesn't exist in the subwiki." (XWIKI-23596)

See also XWIKI-11585 and XWIKI-20957.

Problem 8. Hard to use on small screens

The grid needs horizontal space, its controls are small, and one tap saves a change.

"On small resolutions, the Search filter field from Rights is too small, it would be great if will be larger (now you can write 5-6 characters)." (XWIKI-10227)

Proposed Solution

The changes are listed in implementation order, from the current UI to the final design. The order follows dependencies: each change uses what the changes above it built.

ChangeSolves problemsWhy at this point
List only what is set1, 2Moves the table to Live Data, which every later change builds on. Already planned in XWIKI-24142.
Edit in a dialog3, 8Needs the read-only Live Data table. Already planned in XWIKI-23538.
All rights in one editor5Needs Live Data to show or hide rights as columns, and the dialog to list every right.
Save once, after a review3Needs all edits to go through the dialog, so they can be held as pending instead of saved per click.
Show inherited rights4Reuses the Live Data table as a second, read-only table.
Add a "By right" view5Its edits must go into the same pending changes as the dialog's.
Open on the Rights Hub6Its cards link to the editors and to the list of pages with their own rights, which needs a query over the rights objects of every page.
Explain the effective result4Needs the security module to report why a right is granted or denied, not only whether. This is the main new back-end work.
Flag problems and check access2, 4, 6Use that same explanation, and are shown on the Rights Hub.
Make sub-wikis explicit7Changes the Rights Hub's default access card and the lockout check of the review. Depends on open question 5.

Overview

Rights stops being a single table. It becomes an overview screen, with the details on subsequent UIs:

  • Rights Hub. Answers "who can do what on this wiki, and is anything wrong?" without opening a table: what visitors and registered users get, how many entries are set wiki-wide, how many pages set their own rights, and, only when there is something to fix, a "Needs attention" banner. Each card leads to the place where that part is managed.
  • Editors. The wiki-wide editor and the page editors are the same screen: a list of what is set at that level, viewed by user or group or by right. Page editors also show what comes from the wiki. All edits go through dialogs and are saved together after a review.
  • Pages with their own rights. A list of every page that sets its own rights, each leading to that page's editor.
  • Sub-wikis. Each sub-wiki has the same Rights Hub and editors, scoped to that wiki.

1794572520724-862.png

UI text

The screens keep their text short:

  • Each thing is said once. A deleted user is flagged in the Needs attention banner and on its row, not also on the cards.
  • A label does not restate its control. The effective result is shown only when it differs from the setting, or comes from somewhere else.
  • Rules are not printed on every screen. Intros are one sentence, there is no legend, and IDs, hidden rights and the order of checks are in tooltips or behind "Details".
  • Labels and numbers replace sentences: "7 users and groups", "2 unsaved changes", "Deleted".

Changes

The changes are listed in implementation order, from the current UI to the final design.

List only what is set

Solves problems 1 and 2.

  • The table moves to Live Data (XWIKI-24142), with users and groups in one list.
  • It lists only the users and groups with at least one right set at this level.
  • Each row shows the display name. The ID is in a tooltip, and in the Edit rights dialog.
  • Deleted accounts are tagged "Deleted", so their rights can be removed.
  • Columns can be filtered and sorted, and the table is paginated.

Edit in a dialog

Solves problems 3 and 8.

  • Cells become read-only marks: ✓ allowed, ✕ denied, empty = not set. Each cell has a tooltip, so the table needs no legend.
  • Each row gets Edit and Remove.
  • Edit rights dialog: Not set / Allow / Deny for each right.
  • Add user or group dialog: searches only users and groups that are not listed yet, then opens Edit rights.
  • On small screens, Live Data shows one card per entry, and the dialog opens full screen.

1794572910936-821.png

All rights in one editor

Solves problem 5.

  • The Edit rights dialog groups rights as Standard, Wiki-only and Extension.
  • The Extension Rights and Wikis Creation Rights screens are removed.
  • The table shows the standard rights as columns. Other rights are added through Live Data ⋮ › Properties.
  • A "+N" marker shows rights set in hidden columns, so no setting is hidden. Its tooltip lists them.

1794572931532-116.png

Save once, after a review

Solves problem 3.

  • Changes from the dialog stay pending: rows are tagged New, Modified or Removed, and have Undo.
  • A banner shows "N unsaved changes", with Discard and Review & save.
  • Review changes lists each change, before → after.
  • If the changes remove the current user's Admin right, Review changes warns, names the scope and says which entry the right came from. This covers every cause, not only group membership (XWIKI-21064).

1794572948152-887.png

Show inherited rights

Solves problem 4.

  • Page screens get a collapsed "Inherited from the wiki" section: a read-only table with a link to edit those rights in the wiki administration.
  • The section states the rule in one line: "A right set here replaces the wiki's on this page." The full rule stays in the documentation: when a right is allowed on the page, only the users and groups allowed there get it, and everyone else loses it on that page, even if the wiki allows it. Rights not set on the page come from the wiki.
  • Inherited entries that are also set on the page are marked "Overridden here".

1794572967226-397.png

Add a "By right" view

Solves problem 5.

The editor gets a "By user or group / By right" toggle. "By user or group" stays the default.

  • By right: one row per right, with its category (Standard, Wiki-only, or the extension that adds it), Allowed and Denied counts, and pending changes.
    • Rows show counts only ("1 group, 1 user", or nothing), so the table stays short on large wikis and never scrolls sideways.
    • Filtering Allowed or Denied by a name lists the rights where that user or group is set.
    • On page screens, a "From the wiki" column counts inherited entries.
  • Clicking a right opens the list of who has it. Each entry can be switched between allow and deny, removed, or undone. Clicking a name opens Edit rights.
  • Add opens a popover to allow or deny the right for a user or group.

All changes go into the same pending state as the rest of the editor.

1794572984986-252.png

1794572993255-852.png

1794573001241-125.png

Open on the Rights Hub

Solves problem 6.

Wiki administration › Rights opens on the Rights Hub instead of the table:

  • Default access: what visitors and registered users get, in plain language. Editable in place (XWIKI-14544).
  • Wiki-wide rights: a count and the first names. "Manage" opens the editor.
  • Pages with their own rights: a count and the first names. "Open list" opens a Live Data table with Title, Location, Entries set, View restricted, Last changed, and Open rights. It replaces the audit use of Admin Tools.

1794573016075-941.png

Explain the effective result

Solves problem 4.

  • In Edit rights and the "Add" popover, each right shows Yes or No with the reason, updated as settings change.
  • The line is shown only when it adds something. A right allowed or denied in the dialog itself gets no line.
  • Examples: "Yes · from All registered users". "No · only Website Team is allowed here".

Flag problems and check access

Solves problems 2, 4 and 6.

  • The Rights Hub gets a "Needs attention" banner, shown only when there is something to fix:
    • rights set for deleted users or groups, with Remove rights
    • pages missing a required right (XWIKI-23744), with Mark as reviewed
  • The Rights Hub gets a Check access button: "Can [user] [right] on [page]?" The answer is Yes or No with the deciding setting. The order in which the levels were checked is behind "Details". It reuses the logic of the effective result.

1794573029533-938.png

1794573033268-594.png

Make sub-wikis explicit

Solves problem 7.

  • The top bar and breadcrumb name the wiki being administered.
  • The Rights Hub and the editor state that main-wiki rights do not apply here.
  • Each entry is tagged Local or Global. Add user or group gets an All / Local / Global filter when the wiki accepts both kinds (XWIKI-11585).
  • Default access targets the wiki's members, and sets who can become a member (open, on request, or by invitation).
  • Programming and Create wiki are not offered.
  • The lockout warning knows that main-wiki administrators are not sub-wiki administrators.
  • The main wiki's Rights Hub gets a Sub-wikis card: membership, default access, administrators and items to review for each sub-wiki.

 


 


Get Connected