Connect and manage tools
UniPortal also works on a single JSM instance, where it serves as a custom landing page and upgrades the native customer view with an advanced request table. To add more JSM instances, Salesforce, or Azure DevOps, use the Connections screen.
Steps
In Jira, select the cog icon, then go to Marketplace apps > UniPortal > Connections.
Select Connect new tool.
Choose the tool you want to connect:
- Jira Service Management (JSM): UniPortal asks you to allow access to Atlassian, then redirects you to the native Atlassian authorization page to grant permissions. See Jira Service Management for the full walkthrough and video.
- Salesforce: enter the Client ID, Client Secret, and instance URL of your Salesforce External App. See Salesforce for the full walkthrough and video.
- Azure DevOps: enter your Azure DevOps organization name and a Personal Access Token. See Azure DevOps for the full walkthrough and video.
Danger
Use the same Atlassian account for every JSM instance you connect. If a different account authorizes a later instance, UniPortal replaces the whole connections list with the sites that account can access. For example, User A connects instance_one and instance_two. Then User B, who can’t see either site, authorizes instance_three. Both instance_one and instance_two disappear from the connections list. See the FAQ for more.
When you connect several instances, authorize the local instance to itself first. For example, on https://instance_one.atlassian.net, select Connect new tool, select Jira Service Management, and authorize https://instance_one.atlassian.net before you connect anything else.
This account also becomes the identity behind every request that connected instances exchange afterward. Use a dedicated technical account with only the access it needs, not a personal admin login.
Result
The new connection appears in the Connections table with the status CONNECTED. The first JSM instance you authorize carries the MASTER badge. Every instance you authorize afterward becomes a secondary instance, and you don’t set up that relationship manually.
Tip
The name in the Connected tool column defaults to the instance’s URL. Customers see it as the name of the instance tab until you enter an Instance tab name in Configure tabs, for example “IT Help Desk” or “Dev Tasks”. The first request tab uses the same name until you enter a Tab title for it. You can’t rename a connection on this screen. See Request Tabs.
The Connections screen
Before you connect anything, the screen shows “You don’t have any connections yet” and the Connect new tool button.
At the top, UniPortal shows the number of licensed users and the Instance counted towards license size. See Licensing. If a connected instance’s REST API is disabled, a banner appears and the Connections and Edit layout screens become read-only. They return to normal as soon as UniPortal reaches that instance again.
Below that, the table lists each connection:
| Column | What it shows |
|---|---|
| Connected tool | Platform icon, connection name, and the MASTER badge on the master instance. |
| Instance URL | A clickable link to the platform’s base address. |
| Connected by | Who authorized the connection. |
| Status | A CONNECTED or DISCONNECTED badge. |
| Actions | The actions listed below. |
Actions
The actions depend on the type of connection.
For a secondary JSM instance, the … menu offers Set current instance as a master and Disconnect. The master has only Disconnect.
For Salesforce and Azure DevOps, the … menu offers View details, Test connection, and Disconnect.
| Action | What it does |
|---|---|
| Edit layout | Opens the layout editor with that instance already selected. |
| Set current instance as a master (via ”…”) | JSM only. Makes that instance the master for all connected instances. Every JSM row except the current master has this action. |
| View details (via ”…”) | Salesforce and Azure DevOps only. Opens the connection window with the saved organization and a hidden token. |
| Test connection (via ”…”) | Salesforce and Azure DevOps only. Checks that UniPortal can still reach the connected tool and shows Connection test successful or a failure message. |
| Disconnect (via ”…”) | Removes that connection from UniPortal. |
| Refresh (via ”…” at the top of the page) | Reloads the connections list, so changes made in another browser tab or by another admin become visible, and checks the license. Available on the master instance only. |
Disconnecting
Disconnecting a Salesforce or Azure DevOps connection also deletes its tabs in the default dialog and in every dialog variant.
Master after a reinstall
If you uninstall and reinstall the master instance, UniPortal doesn’t restore its master status. Use Set current instance as a master on any instance to choose a new master.
Permissions and access approvals
After an update that needs new permissions, the admin screens show only a message that UniPortal is unavailable, with the list of missing permissions and a Go to Manage apps button. A site admin approves the new permissions there. Customers can still open the dialog.
UniPortal also needs access approval for each connected tool. Until it is given, that tool’s area says UniPortal isn’t allowed to connect, lists the addresses, and shows an Allow access button:
- Jira:
api.atlassian.comandauth.atlassian.com. - Salesforce: the address of your connected org.
- Azure DevOps:
dev.azure.comand your organization’svisualstudio.comaddress.
Select Allow access. In the dialog that lists the addresses, select Approve.
Customers can’t approve access, so they never see Allow access or the message for admins. Instead, a customer sees a neutral message that the content is temporarily unavailable and to contact the Jira administrator. An admin who opens the dialog on the portal still sees the banner with Allow access.
To check the approved addresses:
In Jira, select the cog icon, then go to Marketplace apps > Manage apps and select Take me there.
In Atlassian Administration, open Connected apps and select UniPortal.
Open the Data management tab.
Next to Data sharing with external domains, select View. The Configured tab lists the approved addresses.
