Skip to Content

Tags

Tags are firm-wide labels you stick on clients, engagements, and tasks for filtering and grouping. Reach for them when return type, pipeline stage, and assigned user aren’t enough.

Examples:

  • VIP — top-tier clients.
  • K-1 dependency — engagements waiting on partnership K-1s.
  • Audit risk — clients flagged for extra review.
  • Bookkeeping client — distinguishes service tier.
  • Q4 urgent — seasonal flag.

To open them, go to Settings → Tags in the sidebar. You’ll see a flat alphabetical list with inline edit. Every tag is firm-wide — the same set shows up for every team member.

What a tag holds

FieldNotes
NameRequired. 1–50 characters. Examples: “VIP”, “Bookkeeping client”

That’s it. Tags are deliberately lightweight today — no colors, no descriptions, no parent and child hierarchy.

Creating a tag

The page has an inline form at the top:

[Type a new tag name… ] [ Add ]

Type and click Add (or press Enter). The tag lands at the bottom of the list.

Tags preserve case but are case-insensitive for uniqueness — “VIP” and “vip” would conflict. Extra spaces are trimmed.

Renaming a tag

Click the pencil on any row. The name becomes editable inline. Press Enter to save, Esc to cancel.

Renaming updates every record that uses the tag immediately. There’s no rename history.

Deleting a tag

Click the trash icon. You’ll see a confirmation with live counts:

Delete “VIP”? This removes the tag from 47 clients, 12 engagements, and 8 tasks.

Confirming removes the tag from every record and deletes it from the catalog. The records themselves stay — only the label is gone.

Where tags show up

SurfaceWhat happens
Client listA Tags column on each row; filter by tag (multi-select)
Client detailTag chips at the top of the profile; add or remove from the chip toolbar
Engagement detailSame — chips with add and remove
Workflow boardOptional “group by tag”
Tasks workspaceA filter — tasks tagged X
SearchTags match in command palette results

Tags don’t appear on documents or invoices today — those have their own categorization.

Attaching tags to records

RecordHow to tag
ClientClient detail → Tags chip toolbar → type or pick
EngagementEngagement detail → Tags chip toolbar
TaskTask detail panel → Tags row
BulkMulti-select rows in a list view → Add tag

The tag picker is a multi-select with type-ahead. If you have permission to manage tags, you can create one inline — typing a tag that doesn’t exist offers “Create tag X” at the bottom of the dropdown.

Bulk tag operations

In the Clients list:

  1. Check off the rows you want.
  2. A bulk action bar appears at the bottom.
  3. Click Add tag → pick a tag → it applies to every selected client.
  4. Or click Remove tag → pick a tag → it comes off every selected client.

Bulk operations work record-by-record. If one client fails (say, a permission issue), the rest still apply. A summary toast shows “Tagged 99, failed 1.”

[Screenshot: Bulk tag action bar]

How many tags should you have?

Less is more. A firm with 200 tags is unmanageable. Aim for 10–30 tags total.

Healthy patterns:

  • Service tier — “Premium”, “Standard”, “DIY”
  • Risk flag — “Audit risk”, “High-touch”, “Compliance review”
  • Specialty — “Crypto”, “Real estate”, “Multi-state”
  • Operational — “K-1 dependency”, “Awaiting client docs”, “Q4 urgent”

Unhealthy patterns:

  • Per-client tags (“Patel Family”, “Chen Family”) — clients already have names.
  • Year tags (“2026”) — the engagement already carries the year.
  • Pipeline-stage tags (“In review”) — pipelines already model this.

Tips

  • Start with five tags — VIP, At-risk, Bookkeeping, K-1 dependency, Q4 urgent. Add more only when you need them.
  • Audit quarterly — delete tags attached to fewer than three records. Sprawl creeps in fast.
  • Use sentence case — “Audit risk” reads better than “audit-risk” or “AUDIT_RISK”.
  • Don’t tag what’s already structured — return type, pipeline stage, and assignee already filter the same things.

Empty state

┌─────────────────────────────────────────────┐ │ │ │ No tags yet │ │ │ │ Tags are firm-wide labels you can attach │ │ to clients, engagements, and tasks. │ │ │ │ [Type a new tag name… ] [ Add ] │ └─────────────────────────────────────────────┘

The same input doubles as the empty-state call to action.

What’s not here yet

Tag colorsRoadmap — chips are monochrome today
Tag descriptionsRoadmap — hover tooltip
Tag hierarchies (parent and child)Roadmap — flat list today
Tag-driven automationsRoadmap — would land in Settings → Pipelines & Automations
Suggested tagsRoadmap — AI-driven tag suggestions

Permissions

ActionRequired
See tags in lists and detailWhoever can view the record can see its tags
Create new tagsManage tags
Edit or delete tagsManage tags
Attach or detach tags on a recordWhoever can edit the record (for example, Edit clients to tag a client)

Manage tags is owner and admin by default. Opening it up to everyone tends to lead to sprawl — start restrictive and loosen later.

Next

Last updated on