Learn about datasources

Overview

Datasources are the entities that securely connect your instance with the tools where your data is. For example, the default datasource is the instance where the app is installed, which needs no configuration.

This data is collected thanks to the integrations provided by the app. See Product and data integrations for more information.

Datasources and gadgets

Each gadget uses a datasource, and several gadgets can share the same datasource. Initially, when you configure your first gadget in a dashboard, you can opt for having all the compatible gadgets automatically configured with that datasource. Imagine that in your dashboard, there are four gadgets that use Bitbucket as the datasource. When you configure the first one, the rest can be automatically configured with the same datasource.

See Add and manage datasources to learn how to configure a datasource.

Permissions in datasources

Datasources fetch and display information from external products, which sometimes require extended permissions to access restricted or confidential data, or information that you want to keep private. In this case, you can configure permissions and indicate who can use and/or edit your datasources. You’ll find the following options to set up access restrictions:

• Anyone can use and edit

• Anyone can use, some can edit

• Only specific people can use or edit

You can configure permissions when you create a datasource or by editing the datasource in the Manage Datasources page.

See Manage permissions on datasources to learn more.

Datasource viewing modes

Datasource viewing modes give you greater flexibility in how gadgets display data. This feature lets you control whether data is displayed based on the permissions associated with the configured credentials, such as API tokens or OAuth tokens, rather than the viewer’s permissions.

Credentials

The gadget always uses the credentials configured by the user who created this datasource to load and display data. These credentials are independent of the viewer or owner permissions.

Datasources configured with specific authentication credentials will always use those credentials to display data, regardless of who is viewing the dashboard.

Open

Viewer

The gadget displays data according to the user's permissions. Users without access to certain fields/projects will not see restricted data.

Open

Owner

The gadget uses the dashboard owner’s permissions to load data, ensuring a consistent view for all users viewing the dashboard.

Open

Datasource	How the data can be displayed

Datasource	How the data can be displayed
My Jira instance (local Cloud or Data Center instance) or My Confluence instance (local Cloud or Data Center instance)	Viewer OR Owner
Connector app (remote Cloud instance) Open	Viewer OR Owner
API Token (Cloud instance) Open	Credentials
User name and password (Data Center instance) Open	Credentials
Personal Access API Token (Data Center instance) Open	Credentials

Type of datasources

Dashboard Hub uses three different types of datasources:

Default datasource

The default datasource is called This Jira/Confluence/Bitbucket/monday.com instance, which is the instance where Dashboard Hub is installed, and it requires no configuration. You can select it right after installing the app.

It is crucial to understand that This Jira/Confluence instance datasource utilizes the permissions of the dashboard owner to access and display data. This means that the data visible in gadgets using this datasource will be limited to what the dashboard owner has access to in the connected platform.

• It is enabled by default, requiring no further configuration. It can be selected immediately in compatible gadgets.

• It has access to the Jira/Confluence instance where the app is installed.

• Data access and permissions are determined by the dashboard owner's permissions within the connected platform. Although, you can choose between the Owner or the Viewer Viewing Mode.

For external platforms like http://monday.com or Bitbucket, the datasource needs to be linked to a specific http://monday.com account or Bitbucket account respectively. The authentication and the scope of accessible data depend on the dashboard owner's permissions within those external platforms.

Open

Connector app

The Dashboard Hub Connector app is a special app that you install on external Atlassian Cloud products like Jira (Core, Software, Service Management) and Confluence.

Data accessed through a Connector datasource relies on the permissions of the Atlassian account connected to the Connector app instance on that specific external instance. This is the user who authorized the connection in that external instance, not necessarily the dashboard owner in the Dashboard Hub instance.

This app acts as a bridge to bring data from other Atlassian Cloud products, maintaining user and security privileges configured on every instance. This ensures that users can only access data from other Atlassian Cloud products if their Atlassian accounts have the necessary privileges.

• It just requires an admin to install the app on the external Atlassian Cloud instance and you are ready to go!

• It requires a paid Dashboard Hub app to be installed in the main instance, but the Dashboard Hub Connector apps are free!

API Token

This type of datasource is required when:

• A connector app cannot be installed.

• When you specifically want to use the data accessible to the user who owns the API token, regardless of the dashboard owner’s permissions. This ensures data consistency, as the data displayed will always be within the scope of the token owner's access, regardless of who is viewing the dashboard or where it is embedded (e.g., on different dashboards or Confluence pages).

• It provides data access to several third-party products and services like the http://marketplace.atlassian.com/ , Migrate from Opsgenie | Atlassian , https://www.atlassian.com/software/statuspage , and http://monday.com(all available today), and others available soon (see Product and data connectionsPreview).

• It requires an API Token to be generated from the external service and configured in the Dashboard Hub datasource settings. The access is limited by the permissions granted to that specific API Token.

Open