Reference:BlueSpicePageAssignments: Difference between revisions

Latest revision as of 15:04, 29 June 2026


Overview
Description:	Enables you to assign users or groups to a page
State:	stable	Dependency:	BlueSpice
Developer:	HalloWelt	License:	GPL-3.0-only
Type:	BlueSpice	Category:	Quality Assurance
Edition:	BlueSpice pro, BlueSpice free, BlueSpice farm, BlueSpice cloud	Version:
View user help page

Features

PageAssignments allows to assign pages to single users or user groups. Assigned users are notified about assignment changes via email or internal notifications.

Assign responsible users to a page.
Assign individual users or groups.
The responsible editor(s) for the page can be viewed in the flyout "Page assignments" in the quality management tools.
Users can view their assignments on the page Special:PageAssignments.
Users with admin, maintenanceadmin or reviewer rights can manage all assignments on the page Special:ManagePageAssignments.
Assigned users can be shown directly in the title area of the page if the default setting is changed to:

$GLOBALS['bsgPageAssignmentsPageHeaderLimit'] = 25;

Assign all users (with option to exclude some users)

To activate the option to assign all users to a page, a group everyone can be created. For this, the following code needs to be set in <bluespice-installationpath>/extensions/BlueSpicePageAssignments/extension.json:

"PageAssignmentsActivatedTypes": {
			"value": [
				"user",
				"group",
				"everyone"
			]
},

This allows users to add the group everyone to a page assignment. Individual users can be excluded from the assignment by creating the file MediaWiki:PageAssignments-everyone-blacklist. Users can be added to this blacklist with using line breaks.

Permissions conflict with explicit edit rights in a namespace

If an administrator set explicit edit-permissions in a namespace, the pageassignable permission is then only granted to this explicitly set editor group. This means that the groups with other roles, such as reader, have their pageassignable permission revoked. This is caused by the fact that the permission is by default assigned to multiple roles (see below permissions table).

As a consequence, even if they "look" assigned to a page, they are not, and they will not receive read confirmations either. The group(s) with the exclusive elevated namespace right (e.g. editor role in the namespace) will receive the read confirmations instead.

To avoid this conflict, set in /data/bluespice/pre-init-settings.php:

$bsgPermissionConfig[ 'pageassignable' ] = [
	'roles' => [
		"reader"
	]
];

This conflict has been observed at least up to -v5.2+

Technical Information

Technical details for BlueSpice cloud can differ in some cases.

Requirements

MediaWiki: 1.43.0

BlueSpiceFoundation: 5.0.0
OOJSPlus: 3.0.0

Integrates into

BlueSpiceBookshelf

BlueSpiceExtendedStatistics

BlueSpicePageAssignments

BlueSpicePrivacy

BlueSpiceSMWConnector

BlueSpiceWikiExplorer

NotifyMe

Special pages

ManagePageAssignments
PageAssignments

Permissions

Name	Description	Role
pageassignable	Appear in the list of assignable users	reader, admin, author, editor, maintenanceadmin, reviewer
pageassignments	Edit the assignments of a page	admin, maintenanceadmin, reviewer

Configuration

Name	Value
PageAssignmentsActivatedTypes	array ( 0 => 'user', 1 => 'group', )
PageAssignmentsLockdownGroups	array ( 0 => 'user', )
PageAssignmentsPageHeaderLimit	3
PageAssignmentsSecureEnabledNamespaces	array ( )
PageAssignmentsSecureRemoveRightList	array ( 0 => 'edit', )
PageAssignmentsTarget	'title'
PageAssignmentsUseAdditionalPermissions	false

User options

Name	Value
echo-subscriptions-email-bs-pageassignments-action-cat	true
echo-subscriptions-web-bs-pageassignments-action-cat	true

API Modules

bs-mypageassignment-store
bs-pageassignable-store
bs-pageassignment-store
bs-pageassignment-tasks

Hooks

Composer requirements

all-packages	mwstake/mediawiki-component-datastore mwstake/mediawiki-component-commonwebapis

Notifications

Name	Buckets
bs-pa-assignment-add	personal
bs-pa-assignment-remove	personal

PDF exclude - start

To submit feedback about this documentation, visit our community forum.

PDF exclude - end

@@ Line 38: / Line 38: @@
 </syntaxhighlight>This allows users to add the group everyone to a page assignment. Individual users can be excluded from the assignment by creating the file ''MediaWiki:PageAssignments-everyone-blacklist''. Users can be added to this blacklist with using line breaks.
 <br />
+{{Textbox|boxtype=warning|header=Permissions conflict with explicit edit rights in a namespace|text=If an administrator set explicit edit-permissions in a namespace, the <code>pageassignable</code> permission is then only granted to this explicitly set editor group. This means that the groups with other roles, such as reader, have their <code>pageassignable</code> permission revoked. This is caused by the fact that the permission is by default assigned to multiple roles (see below permissions table).
+As a consequence, even if they "look" assigned to a page, they are not, and they will not receive read confirmations either. The group(s) with the exclusive elevated namespace right (e.g. editor role in the namespace) will receive the read confirmations instead.
+To avoid this conflict, set in <code>/data/bluespice/pre-init-settings.php</code>:
+<syntaxhighlight lang="php">
+$bsgPermissionConfig[ 'pageassignable' ] = [
+	'roles' => [
+		"reader"
+	]
+];
+</syntaxhighlight>
+|icon=no}}
+This conflict has been observed at least up to {{Bsvs|bsvTo=5.2+}}
 |desc=Assigns individual users or whole groups to pages, e.g. as responsible editors.
 |active=Yes