Cards

Cards are the core building blocks in Cicle. They represent tasks, items, or action points within your project management workflow.

What is a Card?

A card is a discrete unit of work that belongs to a list, which belongs to a board. Cards can contain checklists, comments, attachments, labels, and members.

Data Hierarchy

Company
  └── Team
        └── Board
              └── List
                    └── Card
                          ├── Checklists
                          ├── Comments
                          ├── Attachments
                          ├── Labels
                          └── Members

A card is always scoped to a company and team. When using a Company API Key, these are automatically injected from the key's binding.

Key Concepts

Completion Status

Cards can be marked as complete. The complete field tracks the status, type, and timestamp of completion. This is useful for tracking progress and generating reports.

Archiving

Cards can be archived to hide them from default views without permanently deleting them. Archived cards can be restored at any time.

Multi-Team Operations

Cards can be copied, moved, or updated across different teams in a single request using the bulk endpoints. This is useful for integrations that need to synchronize data across teams.

Members and Labels

Cards can be assigned to multiple members and tagged with color-coded labels. These are used for filtering, assignment, and categorization.

Permission Scopes

Card operations use these scopes:

Scope	Purpose
`card:read`	Read cards and their data
`card:write`	Create, update cards; manage checklists, labels, members, comments
`card:delete`	Archive cards; delete checklists, attachments
`card:comment:read`	Read comments and discussions
`card:comment:write`	Create and update comments and discussions
`card:comment:delete`	Delete comments and discussions

Overview

Cards#

What is a Card?#

Data Hierarchy#

Key Concepts#

Completion Status#

Archiving#

Multi-Team Operations#

Members and Labels#

Permission Scopes#