...
On private or support sites, users always have to log in.
On public sites, users have to log in to see:
Landing pages of Jira Service Management projects.
Request types in Request Types modules and My Requests modules.
Issues in Issue Types modules and Jira Issues modules.
Refined Pages, links and menu folders that are set to be visible to logged-in users only.
Sections and rows on a page that are set to be visible to logged-in users only.
...
Your app(s) | Users log in to all of your sites through |
|---|---|
Confluence | |
Jira | |
Both Refined Sites for Confluence Cloud and Refined Sites for Jira Service Management Cloud | Jira, also if a site doesn’t contain Jira content. In the future it’ll be possible decide per site whether users authenticate with Jira or Confluence. Read about upcoming features in our roadmap. |
...
Hide the login button.
Create or go to the page that will serve as a login page.
Open the Page Builder.
Add the login URL (subdomain).(domain.com)/login to a module: for example a Button module, Image module, or a link in a Text module.
Use view permissions to make the page look different based on whether the user is logged in or not. For example, hide the section or row that contains the module with the login link for users who are already logged in.
...