You can control which kind of user has access to a site. Note that Atlassian permissions still apply to all Atlassian content on your site.Site access permissions let you control who can visit your site. Confluence or Jira Service Management (JSM) permissions that are more restrictive than your Refined permissions still apply. So for example, restricted Confluence pages won’t be visible on a public Refined site.
Interactions with other permissions
You can also set more granular permissions on parts of your site:
Permissions on specific Refined Pages, links and menu folders.
Permissions on specific content on landing pages of Refined pages, Confluence spaces, Jira projects, and JSM projects.
All types of permissions are closely related and may impact each other. For example, a user who doesn’t have site access won’t have access to a Refined Page that’s set to be seen by “anyone”.
Manage a site’s access permissions
...
Access level
...
Anonymous users
...
JSM customers
...
Atlassian users
...
Public
...
x
...
x
...
x
...
Support
...
-
...
x
...
x
...
Private
...
-
...
-
...
x
...
Head to the Refined Administration.
Click Sites in the left-hand menu.
Pick Select the site you want to work with.
Click on the Permissions tab.
...
Public - Anyone can view your site, regardless of whether they are logged in or not. This setting is useful if your site is a knowledge base or public facing support site.
Support (only available if you have added a JSM portal to your site) - Customers who are logged in to JSM can view your site, as well as your organisation’s employees with an Atlassian account. This setting is useful if you have a support site on which only customers with a JSM account can submit a ticket.
Private - Only your organisation’s employees with an Atlassian account can view the site. This setting is useful for intranets, for example.
Choose who can access your site:
Type of site | Description |
|---|---|
Public site |
|
Support site Available when you have Refined Sites for JSM. |
|
Private site |
|