One organization per client
Self-hosted Enterprise holds unlimited organizations on one deployment, each isolated by Row Level Security, with no per-client fee. Your team switches between clients; nothing leaks across.
Feature detailsAgencies live in other people's data and in the fear of pasting the wrong client's brief into the wrong channel. Tenon gives each client an isolated organization, puts client approval on the board as a column, and replaces the PDF-by-email loop with a share link.
Recommended: Self-hosted Enterprise (one org per client), or Tenon Cloud per client account

The average agency runs on 7.2 tools to deliver client work, and tool sprawl ranks at the top of operational pain points reported by agency leaders year after year.
Source: Best Tools for Agencies 2026, AgiledSelf-hosted Enterprise holds unlimited organizations on one deployment, each isolated by Row Level Security, with no per-client fee. Your team switches between clients; nothing leaks across.
Feature detailsAdd "Client review" and "Revisions" to the board. A card sitting in Client review for four days is flagged as stuck, and the account lead sees it before the client asks.
Feature detailsThe brief, the status report and the launch checklist are pages. Send a public link, revoke it when the engagement ends, and stop attaching files to email.
Feature detailsPortfolio health shows every client project and its stuck count; the resource heatmap shows the designer booked on three launches the same week.
Feature details
Client review as a columnApprovals become a column the whole team can see, with the stuck flag doing the chasing.

Resource heatmapThe designer booked on three launches the same week, visible before it happens.

The brief as a pageShared by link, edited in place, linked from every ticket it spawns.
These are complete configurations, not suggestions. Create the project, add these columns and custom fields, create the pages, and the rituals column tells you which Tenon features carry the week.
Take a campaign from brief to live with client sign-off at each stage.
Client review column watched daily. Weekly status page shared with the client by public link. Decisions from client calls recorded as decision cards.
Run a multi-discipline build (strategy, design, development, content) without the client seeing the internal mess.
Timeline view for the launch month. Hill chart for the CMS migration scope. Standup digest posted to the client-facing channel with internal notes stripped.
Deliver a monthly retainer with visible capacity and no scope creep.
Resource heatmap checked Monday. Anything marked "change request" gets a decision card before work starts. Monthly report generated from analytics and shared as a page.
Illustrative scenario based on how teams in this sector describe their week.
Yes, as members of their own organization if you want them inside, or not at all: share pages by public link for clients who should never need an account.
Each organization's rows are isolated by Row Level Security in Postgres, the same architecture that runs Tenon Cloud. A built-in self-test proves cross-tenant reads are denied on your deployment.
No. Self-hosted Enterprise is priced per deployment by total people served. The hundredth client costs the same as the first.
Start free on Tenon Cloud, or self-host it. Copy one of the project setups above and you have a working board in ten minutes.