Card members
A person on a card: a member who works on it, or the responsible user. Write one record per card, user and type. A card has at most one responsible user; if the same user is given both types, the user stays responsible. The import adds the users to the card with the given type. The records here are the people on the card now; activities may tell how they came to be there.
A record of this entity needs records of other entities in the package: Cards; Users.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "card_members". An entity can have any number of files. See Bundle format.
[
{
"resource": "card_members",
"path": "resources/card_members.json"
}
]Fields
| Field | Type | Required | Description |
|---|---|---|---|
external_id | string (ExternalId) | Yes | Your own identifier of the record, for example k-mrr, unique within the resource across all of its files and case sensitive. Other records refer to this one by it.Constraints: 1–512 characters. |
card_ref | Ref<cards> refers to Cards | Yes | The card. Give the external_id of a cards record. |
type | enum | Yes | member for a person on the card, responsible for the one responsible person. A card has at most one responsible user.Constraints: one of member, responsible. |
user_ref | Ref<users> refers to Users | Yes | The user who works on the card. Give the external_id of a users record. |
References
Show on the entity map
Example
A record of this entity:
{
"external_id": "cm-k-mrr-u-liam",
"card_ref": "k-mrr",
"user_ref": "u-liam",
"type": "responsible"
}Rules
- The combination of card_ref, user_ref, type must be unique.
- Among the records with the same card_ref, at most 1 can have type = "responsible".
Related entities
Activities, Cards, Users
Check after the import
After the import, the records of this entity can be checked on Card Members › Retrieve list of card members.
JSON Schema
card_members.json
