/
Learn about Datasources

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 Integration for further 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 datasource, when you configure the first one, the rest can be automatically configured with the same datasource.

See Add and Manage Datasources to see how to configure a datasource.

Permissions in datasources

Datasources fetch and display information from external products, which in some occasions require extended permissions to access restricted or confidential data, or maybe just something you want to keep for yourself. 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 editing the datasource in the Manage Datasources screen.

Read everything you need to know here Manage Permissions on Datasources!

Datasource Viewing Modes

Datasource Viewing Modes give users greater flexibility in how gadgets display data. This feature allows you to control whether data is displayed based on the permissions associated with the configured credentials (e.g., API tokens, OAuth tokens) rather than the viewer’s permissions.

Credentials

The gadget always uses the credentials (e.g., password or token) 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 (e.g., password or API token) will always use those credentials to display data, regardless of who is viewing the dashboard.

credentials.png

Viewer

The gadget displays data according to the permissions of the person viewing the dashboard. Users without access to certain fields/projects will not see restricted data.

viewer.png

Datasources created using Connector apps to connect with remote instances (read more about Dashboard Hub Connector Apps) or local instances using the default datasources “My Jira instance” or “My Confluence instance” will have the ability to choose between Viewer mode or Owner mode.

Owner

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

The Owner Mode can be disabled by admins, check the global setting: Restrict Owner View Mode

owner.png

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)

connector.png

Viewer OR Owner

API Token (Cloud instance)

cloud_api_token.png

Credentials

User name and password (Data Center instance)

user_password.png

 

Credentials

Personal Access API Token (Data Center instance)

PAT.png

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/Bitbucket/monday.com 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/Bitbucket/monday.com instance where the app is installed.

  • Data access and permissions are based on the dashboard owner's access 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.

monday.com-dashboardhublogo.png

 

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), Confluence, and Bitbucket (includes Pipelines).

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!

The Dashboard Hub app itself acts as a connector to the local instance. Therefore, if you are adding a gadget displaying data from the [PRODUCT] instance where Dashboard Hub is already installed, use the default datasource and do not install an additional Connector app. Connector apps are only required for connecting to external instances.

Documentation image DBHC2.png

 

API Token

This type of datasource is required when:

Documentation image DBHC3.png

 

See also

Related content

Need support? Create a request with our support team.

Copyright © 2005 - 2025 Appfire | All rights reserved.