Release page access setting (Private, Restricted, Public, Off)
Introduction
In our Automated Release Notes app, we offer various access types for release pages to cater to different user needs and privacy preferences. These access types allow you to control who can view the release pages created bases different use cases/for different target audiences, etc. Below are the four access types available -
Private - This access type restricts access to the release page to only those users who have been explicitly logged in to your JSM portal. It ensures maximum privacy and confidentiality for sensitive release information.
Restricted - With the restricted access type, access to the release page is limited to specific email addresses or website domains. It provides a balance between privacy and accessibility, allowing controlled sharing of release information within relevant end users.
Public - The public access type makes the release page accessible to anyone, including users who are not logged in to the application. It is ideal for sharing release information with a wider audience, such as customers, partners, or the general public, without requiring authentication.
Off - When the access type is set to "Off," the release page is not accessible to anyone, effectively disabling its visibility. This option may be useful during development or when the release information is not ready for sharing.
How users can login to the private release page?
Jira service management (JSM) should be installed on the same Jira instance to enable private access to release page.
On the landing page, users will see the login option.
When user clicks on the login button, they will be redirected to your JSM portal login page.
Once user logs into the JSM portal with valid credentials, they will be redirected to the release page.
If the user is already logged into the JSM customer portal on the same browser, they will not be redirected to JSM login page and will get logged into the release page automatically.
How users can login to the restricted release page?
On the landing page, users will see the login option.
Below are some cases based on which you’d see how users are restricted or given access to the release page
Has JSM account (Assumption is user is not logged in to JSM account) | Belongs to given domain | Access |
---|---|---|
Yes | Yes | User is redirected to JSM account to login. Once logged they are given an access to release page once clicked on the release page link. |
Yes | No | User is redirected to login. Once logged in and clicked on release page and below message will be displayed - This release page is not accessible to you. Please contact the release page admin to get relevant access. |
No | Yes | User is redirected to sign up on JSM. Once signed up, they need to click on release page link and they can access the release page |
No | No | User is redirected to sign up on JSM. Once signed up, they need to click on release page link however below message will be displayed - This release page is not accessible to you. Please contact the release page admin to get relevant access. |