> For the complete documentation index, see [llms.txt](https://bdi.gitbook.io/bdi-public-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bdi.gitbook.io/bdi-public-documentation/readme/representation-kit/certified-roles.md).

# BDI Association Roles

## 1. Introduction

BDI defines Common Roles as the standardized roles for activities in a specific sector or type of supply chain. They form the basis for standardized role-based authorizations, lowering the effort for maintaining authorization rules.

This type of roles is sector specific, as opposed to BDI Roles that are part of the building blocks (see Policy Agreements).

## 2. **Sector specific Common Roles**

Common roles define operational responsibilities within supply chains, helping to create standardized policies, particularly Data Access Policies. Each specific sector (type of cargo, modality) has common roles that are well-understood and recognized. The same applies to data elements that a role needs to have access to, in order to be able to perform a task. Defining these common roles (such as truck driver, customs agents, inspection agent, forwarder or terminal planner) reduces the cost of interactions between entities. An undefined role needs custom definitions for the combination role-data access policy. Defining these policies is a labor-intensive action. Managing access rights is simplified by standardization.

Members of different Associations that have different policies per common role, or different roles, will need to align these policies and roles to become interoperable. It is expected that a natural convergence on common roles in a sector will appear over time: Associations will agree upon shared common roles and policies if this benefits their business objectives.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bdi.gitbook.io/bdi-public-documentation/readme/representation-kit/certified-roles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.