Site access permissions let you control who can access visit your site. If your Confluence and or Jira Service Management (JSM) permissions still apply to all spaces and projects on your siteare more restrictive than your Refined permissions, these 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
...
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 when you have added a JSM project to your site Refined Sites for JSM) - Customers who are logged in to JSM can view your site, as well as your organization's employees with an Atlassian account. This setting is useful for support sites where only customers with a JSM account can submit a ticket.
...
Access level | Anonymous users | JSM customers | Atlassian users |
---|---|---|---|
Public |
|
|
|
Support | - |
|
|
Private | - | - |
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.
...