Projects

Projects is Bitment's work management app: projects contain sections, sections contain tasks, and tasks are where the actual work gets tracked, from a single deliverable to a whole engagement. Your team uses it to run everything from client onboarding checklists to a firm-wide sales pipeline, with due dates, assignees, dependencies, comments, and attachments all living on the task itself. If your firm already runs its work in Asana, Projects can mirror that workspace instead of replacing it, and migrate you off it when you're ready.

Where to find it

Open Projects from the dock. Opened from inside a client, Projects shows that client's task aggregate instead of a project list: projects themselves are not owned by a client, but individual tasks can be linked to one (Coordination › Projects in a client's sub-navigation).

Key concepts

Project: a container for a body of work. It has a name, a description, an optional avatar color or image, and belongs to a firm or to you personally.
Section: a stage or bucket within a project (the columns in board view), such as "Discovery" or "In review."
Task: the atomic unit of work. A task carries an assignee, dates, a description, custom fields, attachments, subtasks, dependencies, and comments.
Subtask: a full task nested under a parent task, with its own assignee and dates.
Dependency: a link between two tasks that shows blocking work from both ends.
Custom field: a field you define per project (a dropdown, text, number, date, or tags) and set per task, for tracking things like priority or deal stage.

A new workspace ships with a Sales Funnel project already set up, with stages running Lead → Discovery → Proposal Sent → Negotiating → EL Sent → Won → Lost, so there's a working pipeline before you configure anything.

Create a project and its stages

Open Projects from the dock and click New Project.
Give it a name and description, and optionally set an avatar color or image and which firm it belongs to (or keep it personal).
Inside the project, add sections for the stages or buckets you want to track work through. These become the columns in board view.
Add tasks into the sections that belong there.

A section that still contains tasks can't be deleted. Move its tasks out first.

Work with tasks

Create a task in any section, or open an existing one to see its detail view: assignee, dates, description, custom fields, attachments, subtasks, dependencies, and comments.
Drag a task between sections to move it through the workflow.
Add subtasks under a task when the work needs to be broken down further. Subtasks are full tasks, so they can have their own assignees and due dates.
Link two tasks as dependencies so blocking work is visible from both sides.
Set values for any custom fields the project defines.
Link a task to a client from the task detail view to have it show up on that client's task aggregate.

Attach a file (or paste a screenshot)

Use the attach button in the task's Attachments section, or paste directly: copy a screenshot or any image, click into one of the task's fields (the description is the easiest), and press Cmd+V / Ctrl+V. It attaches as a file instead of dropping into the text. The limit is 25 MB per file.

Comments and mentions

Task comments are threaded and live on the task itself, so discussion stays with the work instead of scattering into a chat channel. Type @ to mention a teammate or something else in the workspace; mentioning someone notifies them.

Star, archive, restore, and delete a project

Star a project from the projects list to keep it at hand.
Archive takes a project out of the active list without losing it.
Restore brings an archived project back to the active list.
Delete is only available on an archived project, so nothing active can be removed by accident.

Use the share control on a project to grant a colleague view or edit access, or to share it with a firm's whole team. See Firm & team for how sharing and roles work across Bitment.

Connect Asana

If your firm runs its work in Asana, connect it under Settings › Connections › Asana. Once connected, a second tab appears at the top of the Projects app labeled Bitment | Asana.

The Asana tab mirrors the connected workspace's projects and tasks, and changes flow both ways: you can create, update, move, complete, and comment on Asana tasks from inside Bitment. The mirror covers a subset of what Asana's native surface offers; features like custom fields, dependencies, attachments, client links, and sharing are Bitment-native and stay switched off on the Asana side.

Migrate a project off Asana

If your firm is moving off Asana, open any project in the Asana tab and click Migrate to Bitment in the header.

Choose which firm (or Personal) the new project should belong to. It defaults to the connection's own firm.
Bitment creates a new native project in the Bitment tab with a full copy of everything in the Asana project: sections, tasks, subtasks, comments, and assignees (matched to your teammates by their verified email address).
The original Asana project is left untouched, and the copy does not stay in sync afterward. This is a deliberate one-time migration, not an ongoing mirror.

Migrate each project once, then disconnect Asana under Settings › Connections when you're done moving off it. Clicking Migrate to Bitment again later creates a second, independent copy rather than merging changes into the first one.

Create and edit tasks with the AI

The AI can create, update, complete, and reassign tasks for you when you describe what you need, whether you're talking to it in a chat or from the Assistant panel inside Projects. It can also add or rename a project's sections and reorder a whole stage list in one step. Depending on your permission level, the AI either proposes the change as a card for you to review before anything is created, or carries it out directly. A proposed task shows up as an editable card: adjust the title, due date, section, or assignees right there before approving it. Ask the AI to list or summarize tasks and it can show you a live, expandable card for each one, with quick actions to complete it, set a due date, reassign it, or move it to another section, all without leaving the conversation.

Tips

A brand-new project needs sections before it needs tasks: set up your stages first, then start adding work.
Use dependencies when a task genuinely can't start until another finishes; use subtasks when a task is really several smaller pieces of the same work.
If Asana is only used by part of your team, the migration path lets you bring one project across at a time rather than an all-or-nothing switch.