Manual:Extension/BlueSpicePageAccess: Difference between revisions

Redaktion (talk | contribs)
No edit summary
Tag: 2017 source edit
Redaktion (talk | contribs)
No edit summary
Tag: 2017 source edit
Line 22: Line 22:
<pre><nowiki>
<pre><nowiki>
<bs:pageaccess groups="sysop, secure1,secure2" />
<bs:pageaccess groups="sysop, secure1,secure2" />
</nowiki></pre>{{Note box|boxtype=Note|icon=|Note text=A user can only restrict access to the groups that user belongs to. This is a security feature that prevents users from locking themselves out of a page. In addition, users in the sysop group always have access to these pages.|bgcolor=}}
</nowiki></pre>{{Textbox|boxtype=note|icon=yes|header=Important!|text=A user can only restrict access to the groups that user belongs to. This is a security feature that prevents users from locking themselves out of a page. In addition, users in the sysop group always have access to these pages.|bgcolor=}}
{{Translation}}
{{Translation}}


[[Category:Editing]]
[[Category:Editing]]

Revision as of 09:53, 19 February 2025


The BlueSpicePageAccess extension allows you to restrict access to a page to specific user groups. The restriction is done by inserting the pageaccess tag. The access restriction per page is done on a group basis. "Access" here means all actions including reading and editing.

Instructions

To add this tag using VisualEditor:

  1. Position the cursor at the top of your page.
  2. Select Add Content Droplet.
  3. Select Page Access Permission in the dialog box.
  4. Click Insert.
  5. Add the desired groups.
  6. Click Insert.
    alternative text=Restrict read access to groups

The page now shows an info header with the groups that have access. Access restriction notice banner

In source view, the tag looks like this:

<bs:pageaccess groups="sysop" />

To add more groups, separate them with commas:

<bs:pageaccess groups="sysop, secure1,secure2" />
Important!A user can only restrict access to the groups that user belongs to. This is a security feature that prevents users from locking themselves out of a page. In addition, users in the sysop group always have access to these pages.




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