Message-ID: <657611986.16116.1711724805912.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16115_505002762.1711724805912" ------=_Part_16115_505002762.1711724805912 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Restricting User Access to Structure

Restricting User Access to Structure

By default, Structure is accessible to anyone who has Browse= permission on structure-enabled projects. You can further restrict th= is access level to one or more user groups.

To select who can use Structure:

  1. Navigate to Administration | Structure | Configuration.
  2. Click Select Structure Users.
  3. Select whether Structure should be available to Everyone or to = ;Users in selected groups/roles.
  4. In the latter case, change the selected groups/roles list by selecting the second radio button and use the Add = Group/Role section to add one or more required user groups or= project roles. To set up required property, use the drop-down selectors to= choose either Group or Project option, then choose the required group name or project/role comb= ination and press the Add button to add it to the lis= t. If project is set to "Any", this means that t= he user should be in the specified role for any of structure-enabled proje= cts.
  5. You can remove the permission option by clicking the trashcan icon on t= he right of the option. 
  6. Click Apply when done or Cancel to dismiss your changes.

Which projects are enabled for the Structure also affects Who Has Access t= o the Structure.

When Structure is enabled for anyone, even anonymous vi= sitors will have access to Structure. To make Structure accessible to only = logged in users, restrict access to the jira-users group.<= /p>

Structure plugin maintains a cache of users permissions with regards to eac= h structure. In most cases, the cache is recalculated automatically, but in= some cases Structure plugin may miss a change in a user's groups or roles.= The result could be that the changed permissions take effect several minut= es later (but only with regards to=20 Structure Permissio= ns). A user can force the cache to be recalculated by doing=20 hard refresh from the browser. Typically, it's done by hol= ding=20 Ctrl or=20 Shift or both and clicking the=20 Refresh button.
------=_Part_16115_505002762.1711724805912--