Notion Content Agency Template: Manage Multiple Client Accounts

Running a content or marketing agency means juggling several client accounts at once, each with its own editorial pipeline, deadlines, and invoices. The temptation is to spin up a separate workspace or a duplicate set of databases for every client, but that quickly becomes a maintenance nightmare: eight copies of the same task board, no shared reporting, and constant context switching. The free Notable Dashboard takes a different approach. Because everything in it is one set of databases surfaced through multiple filtered and rolled-up views, you can run many clients through a single workspace without cloning anything. This article walks through how to adapt its real fields to an agency operation.

Why one workspace beats duplicated databases

The core design principle of the Notable Dashboard is that a single database powers many views. The Quick Stats row at the top of the dashboard, for example, does not contain numbers anyone typed in. Each stat, Tasks Due Today, Active Goals, Monthly Revenue, and Upcoming Events, is a filtered or rolled-up view of an underlying linked database. That same pattern is exactly what a multi-client agency needs. When your Tasks & Projects database and Financial Tracker hold every client’s records together, a top-level rollup can total revenue or count open tasks across your whole book of business in real time. Duplicate databases cannot do that; they fragment your data so no single view can ever summarize the portfolio.

The practical payoff is that you maintain one schema. Add a field once and every client view inherits it. Fix a formula once and every rollup updates. You get per-client focus through filters and agency-wide reporting through rollups, from the same source of truth.

Separating client accounts with the Project field

The Tasks & Projects database ships with these fields: Name, Status (Not started, In progress, Done), Due Date, Priority (Low, Medium, High), Progress (%), Project (Marketing, Sales, Management, Finance), Tags, and Assigned To. The field that does the heavy lifting for an agency is Project. Out of the box its options describe internal departments, but a select field is just a set of labels you control. Rename or replace those options with your client account names, for example Acme Corp, Bluebird Coffee, and Northwind Media, and the Project field becomes your client separator.

Every task, from “Draft Q3 blog post” to “Schedule client review call,” gets tagged to the client it belongs to. You keep Status, Due Date, Priority, and Progress doing their normal jobs, and Assigned To routes work to the right writer, editor, or strategist on your team. Tags stays free for cross-cutting labels like content type (blog, social, email) or campaign name, which is useful because those cut across clients.

Building filtered views per client

Once tasks carry a Project value, create one filtered view of the Tasks & Projects database per client: filter where Project is Acme Corp, another where Project is Bluebird Coffee, and so on. Each view shows only that account’s work, so a strategist opening the Acme view sees a clean board with no cross-client noise. You can group these views by Status to get a kanban board, or sort by Due Date for a deadline-driven list. Because they are all views of the same database, a task edited in one place is instantly correct everywhere, and the unfiltered master view still shows the entire agency workload for capacity planning.

Per-client editorial scheduling in the Content Calendar

The Notable Dashboard includes a Content Calendar linked from its Navigation hub, and this is the natural home for editorial planning. Treat each entry as a content piece with its owning client, its publish date, and its production status. If you apply the same client-name convention here, tagging each item to its account, you can create a calendar view filtered to a single client to review that account’s editorial schedule in isolation, then switch to the full calendar to see every client’s publish dates side by side and spot bottlenecks where two big pieces land the same week.

Pairing the Content Calendar with Tasks & Projects gives you two useful layers: the calendar answers “what is publishing and when,” while the task board answers “who is doing which step and is it on track.” Keeping them as separate but coordinated databases avoids overloading a single record with both scheduling and granular production sub-tasks.

Tracking client payments in the Financial Tracker

The Financial Tracker database has these fields: Name, Amount ($), Date, Category (Groceries, Bills, Client Payment, Client, Salary, Office, Stocks, Freelance, Software), Type (Income, Expense, Investment), Status (Completed, Pending), and Notes. For agency billing, this maps cleanly. Log each invoice or retainer as a record with the Amount, set Category to Client Payment, and set Type to Income. Use Status to distinguish invoices that are Completed (paid) from those still Pending, and use the Notes field to record which client and invoice number the payment corresponds to, or add the client name into the record Name itself for quick scanning.

This matters because the Monthly Revenue Quick Stat is defined as the sum of Amount where Type is Income for the current month. When your client payments are entered as Income, they automatically flow into that agency-wide revenue figure. You can also build filtered financial views, for instance one showing only Pending client payments, to run a fast accounts-receivable check on who still owes you.

Rolling up across accounts

The strength of the shared-database model shows up in reporting. Because all clients live in the same Tasks & Projects and Financial Tracker databases, the Quick Stats row rolls up across every account at once. Tasks Due Today counts deadlines across all clients, and Monthly Revenue totals every client payment for the month. You get a genuine portfolio view without assembling anything by hand, and you can still drill into any single client through its filtered view.

Permissions and sharing when you invite clients

If you want to give a client visibility into their own account, be careful with Notion’s sharing model. Notion permissions are set at the page level and are inherited by sub-pages, but a linked database view still reads from the original shared database. That means sharing a page that contains an unfiltered linked view can expose other clients’ records. To share safely, give a client access only to a dedicated page containing views filtered to their Project, and confirm those views cannot be edited to remove the filter. When in doubt, review Notion’s guidance on sharing and permission levels before inviting an external guest, and consider exporting a report rather than granting live access.

You can duplicate the free Notable Dashboard to start from a working structure and adapt these fields to your client roster; grab it from the free Notable Dashboard template and rename the Project options to your accounts as your first step.

Sources & further reading

• Notion Help: Sharing and permissions
• Notion Help: Relations and rollups