Skip to main content

Role-Based Access in TargetBoard

How TargetBoard's user roles, board roles and access roles combine to control what each person can do and which data they can see.

8 min read

Every person in TargetBoard gets access through two separate layers. The first decides what they can do. The second decides what data they can see.

Two layers of access

The layers work together, and each answers a different question.

Layer

Question it answers

Example

User role

What actions can this person take?

Manage users, edit a board, delete a metric

Access roles

Which data can this person see?

Only Sales metrics, or only Engineering data for the Backend team

A person might be allowed to edit a board but still only see the data their access roles permit. The goal is simple: everyone sees what they need for their job, and sensitive data such as HR or Finance stays with the right people.

The roles

User roles, board roles and access roles each control a different part of access.

User roles: what people can do

Each person has one user role on each account they belong to. New people start as Member.

Role

Who it's for

What they can do

Admin

Account owners and managers

Everything a Member can, plus: add and manage users, create and assign access roles, edit any board, delete metrics, create API tokens, and create saved filters shared across the account. Admins see all data, regardless of access roles.

Member

Everyone else

View boards shared with them, edit boards where they're an Editor, and create their own personal saved filters and alerts. They see only the data their access roles allow.

Board roles: who can view or change a board

Boards have their own sharing settings, separate from the user role. Admins can edit any board on their account.

Setting

What it means

Public board

Anyone on the account can view it.

Invite-only board (the default)

Only people added to the board can view it.

Viewer on a board

Can open and read the board.

Editor on a board

Can change the board's layout, cards and settings.

Access roles: what data people can see

Access roles are named bundles of data permissions, such as "Sales team" or "Backend engineers". A person can hold several access roles at once. Every account starts with a few ready-made ones.

Built-in access role

What it grants

Full access

Every data area, with no limits.

[Area] (Full Access), e.g. "Sales (Full Access)"

Everything within that one data area.

Admins can rename these built-in roles and edit their descriptions, but cannot change what they grant or delete them. Admins can also create their own custom access roles.

One set of permissions, everywhere in TargetBoard

A person's access roles apply to every way they reach data in the platform. Each of these works from the same permissions:

Where

How permissions apply

Dashboards

Boards, metrics and cards show only permitted data.

AI Assistant

Answers, summaries and insights draw only on permitted data.

Digital Analysts (Agents)

Agents work within the permissions of the person using them.

MCP

Tools connected through MCP get only the data the person can see.

A user will never be able to see data they shouldn't through the platform.

What decides what someone can see and do

A handful of factors combine to decide each person's access.

  • Their user role. Admins can do everything and see all data. Members are limited by the factors below.
  • Data areas (permission groups). Every metric belongs to one data area, such as Engineering, Sales, Marketing, Finance, HR, Product, DevOps, Customer Support or Security. An access role unlocks one or more areas, or all of them.
  • Data limits within an area. An access role can unlock an area fully, or only part of it. For example, "Engineering, but only the Backend team" or "Sales, but only the EMEA region".
  • Access roles add up. When someone holds several access roles, they see everything any of those roles allows. Roles never take access away from each other.
  • No access role means no data. A Member with no access roles assigned sees no metric data until an Admin assigns one.
  • Board sharing. Even with data access, a person needs to be allowed onto an invite-only board to open it.

What people see when access is limited

  • Locked metric. The metric belongs to a data area the person's roles don't unlock. They'll see a message that they don't have access.
  • Empty metric (zero or no data). The person has access to the area, but their limits don't match anything in this metric. For example, a "Backend team only" role applied to a metric that isn't broken down by team.
  • Partial numbers. The person sees totals that only include the data they're allowed to see. Their numbers can differ from an Admin's numbers on the same board, and that's expected.
  • AI summaries and insights follow the same rules, so a summary never reveals data the reader isn't allowed to see.

Other access paths

API tokens are used to connect other tools to TargetBoard. They are created by Admins and limited to the data areas chosen when the token is created.

Common use cases

Typical ways accounts set up access roles. Limits work on the dimensions your metrics are broken down by, such as team, region or product.

Separate business units

Each business unit should see its own numbers, not the others'.

  • Set up: One access role per unit, each limited to that unit, e.g. "EMEA Sales" and "NA Sales", each unlocking Sales limited to its region.
  • Result: Each unit sees only its own pipeline and results on the same shared boards. Leadership with Full access sees the combined picture.

Separate teams

Engineering teams should see their own delivery and quality metrics.

  • Set up: A role per team, e.g. "Backend engineers" and "Platform team leads", each unlocking Engineering limited to that team. A saved filter such as "Backend teams" can define the limit once.
  • Result: Everyone uses the same boards, and each person sees their own team's data.

Protect sensitive data

HR and Finance metrics should stay with HR and Finance.

  • Set up: Give "HR (Full Access)" or "Finance (Full Access)" only to those teams. Other roles don't unlock these areas.
  • Result: Everyone else sees a locked metric, and the AI Assistant and agents never use this data in their answers.

Cross-functional leaders

A revenue leader needs Sales and Marketing data together.

  • Set up: Assign both "Sales (Full Access)" and "Marketing (Full Access)". No new role is needed.
  • Result: Access roles add up, so the leader sees both areas in one place.

What each account can customize

Each account's Admins control their own setup. Nothing here affects other accounts.

Area

What Admins can configure

User roles

Choose who is an Admin and who is a Member.

Custom access roles

Create roles with their own name and description, e.g. "EMEA Sales" or "Platform team leads". Role names must be unique within the account.

Data areas per role

Pick which data areas a role unlocks: one, several, or all.

Data limits per area

For each area, either give full access or limit it, e.g. to certain teams, regions, products or people. A role can limit one area and leave another fully open.

Saved filters in roles

Reuse an account-wide saved filter (such as "Backend teams") inside a role. Only filters that Admins control can be used, so Members can't widen their own access by editing a filter.

Role assignments

Give each person any mix of access roles. Changes take effect right away.

Built-in roles

Rename them or change their description. What they grant stays fixed.

Board sharing

Make each board public to the account or invite-only, and choose who is a Viewer or Editor.

API tokens

Create tokens and choose which data areas each one can reach.

The list of data areas comes from the metrics an account uses, so accounts only see areas that are relevant to them.

Common questions

A new teammate logs in and sees nothing. Why?

New Members start with no access roles. An Admin needs to assign at least one, such as "Sales (Full Access)".

Two people look at the same board and see different numbers. Is something broken?

Usually not. Each person's numbers only include the data their access roles allow. An Admin sees everything, so their totals are often higher.

A metric shows zero for someone, but it has data for others. Why?

Their role unlocks the metric's data area, but its limits don't match this metric. For example, a "Backend team only" role on a metric that isn't broken down by team. An Admin can adjust the role or add another one.

How do I give someone access to just one team's data?

An Admin creates an access role that unlocks the relevant area and limits it to that team, then assigns it to the person.

Someone needs both Sales and Marketing data. Do we need a new role?

No. Assign both the Sales role and the Marketing role. Access roles add up.

Can a Member see a board they weren't invited to?

Only if the board is set to public. Invite-only boards require the person to be added as a Viewer or Editor.

Can we delete or change the built-in "Full access" roles?

You can rename them and edit their descriptions. What they grant can't be changed, and they can't be deleted.

Who can make these changes?

Only Admins on the account.

How did we do?

Next Self Hosting Setup