People and support object types record the teams, roles, and support channels attached to a data contract. See Data contracts for the concepts. This group has four object types: Team, Team member, Role, and Support channel.
Team
A team groups the people responsible for a data contract. It works as a container that holds the contract’s team members.
Teams come from the Open Data Contract Standard (ODCS), the contract model behind the Data Product Standard application. In the app, a team sits in the People and support group. A data contract can define one or more teams.
Add a team to record who maintains a contract and to keep its members in one place. A team describes the people and contacts on the contract, not who is accountable for the product. Accountability stays with the product’s ownership roles (owner, steward, custodian).
For example, the data contract for a “Customer 360” product defines a team that groups its data engineers and analysts.
Team attributes
| Attribute | Description |
|---|---|
| Team Name | Name of the team. |
| Description | Rich-text description of the team. |
| Tags | Free-text tags for the team. |
Team member
A team member is one person on a data contract’s team. It records the person’s account, their job role on that team, and their dates in and out.
Team members come from the Open Data Contract Standard (ODCS), the contract model behind the Data Product Standard application. A team holds its members as separate team member entries in the People and support group.
Add a team member for each person who works on the contract. The Date In and Date Out fields track when someone joins or leaves. Replaced By Username records who took over.
For example, the “Customer 360” contract’s team includes a member with the username jsmith, a role of data engineer, and a join date.
Team member attributes
| Attribute | Description |
|---|---|
| Username | Account username of the member. |
| Full Name | Full name of the member. |
| Role | Job role on the team. |
| Date In | Date the member joined. |
| Date Out | Date the member left. |
| Replaced By Username | Username of the replacing member. |
Role
A role is an access-control role defined on a data contract. It sets what access the role grants and who approves requests for it.
Roles come from the Open Data Contract Standard (ODCS), the contract model behind the Data Product Standard application. In the app, a role sits in the People and support group.
Use a role to document how consumers request and gain access to a contract’s data. A request can pass through First Level Approvers and then Second Level Approvers for two-step review. This role controls access, so it differs from the product’s ownership roles (owner, steward, custodian), which describe accountability.
For example, the data contract for a “Customer 360” product defines a Data consumers role that the data steward approves.
Role attributes
| Attribute | Description |
|---|---|
| Role Name | Name of the access role. |
| Access Level | Level of access the role grants. |
| First Level Approvers | Approvers for the first approval step. |
| Second Level Approvers | Approvers for the second approval step. |
Support channel
A support channel is where consumers get help for a data contract. It records the channel type, the tool it runs on, the scope of support, and a link to join.
Support channels come from the Open Data Contract Standard (ODCS), the contract model behind the Data Product Standard application. In the app, a support channel sits in the People and support group.
Add a support channel so consumers know where to reach the team behind a contract. Channels commonly run on tools such as Slack, email, or Jira.
For example, the data contract for a “Customer 360” product lists a Slack channel, #customer-360-support, with an Invitation URL to join.
Support channel attributes
| Attribute | Description |
|---|---|
| Channel Type | Type of support channel. |
| Channel URL | Link to view the existing channel. |
| Tool | Tool the channel runs on. |
| Scope | Scope of support the channel covers. |
| Invitation URL | Link to join the channel as a new member. |
For the concepts behind these object types, see Data contracts. For how they connect to other object types, see Data product object types and attributes.