a root to stand on
Every tool that lets you belong to many organizations gives you a switcher. The handful of real roots exist only where one company owns every context. Paperclip is the first tool I have used where one person owns many organizations natively, and it shipped without a root. So I built one.
Superhuman’s support site has a page titled “Unified Inbox Workaround.” Not “unified inbox.” The workaround. It explains how to use tabs and keyboard shortcuts to approximate seeing your accounts together, because the product does not do it. Shortwave’s equivalent page suggests forwarding everything into one Gmail.
I have been collecting these for a while, because they are confessions. The companies that build the most opinionated software for people with several jobs looked at the problem of showing those jobs side by side and wrote a help article instead.
roots belong to owners
I went through the tools a person with many organizations touches in a day: chat, identity, cloud consoles, browsers, desktops, terminals, password managers, planners. Almost all of them do the same two things. They isolate a context well, and they hand you a menu to pick the next one. Slack’s workspace list. GitHub’s account switcher, added in November 2023 because Enterprise Managed Users made everyone two people. AWS’s access portal, which since January 2025 will let five identities sign in at once, each in its own tab. Chrome profiles. Notion workspaces. Obsidian vaults. VS Code profiles. CrewAI has a command called org switch. Paperclip has a company switcher in the sidebar.
A switcher solves the inside of each context and leaves the between to your memory.
The exceptions are worth listing, because they share one property. 1Password shows every vault from every account in a single view. Discord’s inbox shows unreads and mentions across all your servers. Slack, since its 2023 redesign, can merge channels and unreads across every workspace you’re signed into. Microsoft 365 Lighthouse gives a managed-service provider one portal over every customer tenant they administer, and Microsoft’s own phrase for it is “single pane of glass.”
In every one of those, one party owns the data model for all the contexts. 1Password owns your vaults. Discord owns your servers. Microsoft owns the tenants and the partner relationship that connects them. The moment the contexts have different owners, a personal GitHub and an employer’s managed one, two Gmail accounts, six client tenants where you are a guest, the root disappears and a help article appears in its place.
That is the structural fact under the multi-organization problem. You are a guest in most of your organizations. Nobody who owns a context will build you a view of the ones they don’t own. So the root, if it exists, has to be yours.
the first tool where you own the organizations
Paperclip is an open-source control plane for running agents as a company: roles, reporting lines, budgets, goals, issues, heartbeats. It launched on 4 March 2026. The line in its README that matters here is not about agents. It says a single deployment runs many organizations with complete data isolation between them. Company is a first-class, multi-instance entity. Every object belongs to one.
That makes it the first tool I have used where one person natively owns N organizations, each a complex group of complex agents doing complex things, and can stand outside all of them. My own instance has dozens of companies in it. Some are businesses. One is this blog. Several are experiments that lasted an afternoon.
And the interface drops you inside one. The sidebar switcher is the whole between. On 30 March 2026 somebody opened issue #2212 against the project, titled “No Cross-Company Coordination Mechanism,” and the answer was that isolation is by design. Which is correct for the agents. Company A’s agents should not see company B. But the operator is not an agent. The operator is the one person all those companies have in common, and the product had no place for that person to stand.
The marketing copy says “one control plane for your entire portfolio.” There was no portfolio screen. That is not a criticism of the project; it is the same vacuum I found in terminals. When a tool’s data model finally gets the unit right and its interface still opens inside one instance of it, the missing surface is exactly the one nobody has ever built, because nobody has ever owned enough organizations at once to need it.
what the root had to be
So I built one. It’s called Tickler, after the tickler file: the accordion of dated folders that sat in every office of the last century, whose one job was to bring a thing back in front of you on the day it needed you. Same job here. Tickler is a single pane of glass across every company in the instance. It shows, in summary, roughly everything a company’s own screens show, condensed to the point where you should not have to leave it, with a door into the full company for when you do.
The requirement, in the words I wrote down before starting: a starting-point control surface that gives the user a root to stand on. A foundation. A known location that is the central starting point for the whole experience, and that you can always get back to.
Working from that, five properties, in the order I discovered they mattered.
It belongs to no company. The root cannot be a special company, or the most recent company, or a dashboard inside a company. It is above the company boundary, and the only thing it can show is what every company is willing to tell it.
It shows need, not activity. The failure mode of every “unified” view is the merged feed: all of everyone’s traffic, interleaved, which is just email again. A root shows, per organization, three things: what state is it in, what does it need from me, and how long has it been since I looked. That third one is the interest column. It is the number no tool shows you and the one that should decide where you go next.
It is where you return to. A switcher moves you from A to B. A root moves you from A to the root to B, and the extra hop is the point. It is the moment where you write down what A was, look at every organization’s need, and choose B on purpose rather than because B pinged. It is Ashforth’s rite of passage with a URL. Nippert-Eng’s segmentors kept two key rings. The root is the hook by the door where both rings hang.
It reads and writes the block. Every organization gets a small, fixed-shape record of what you were doing there: who this is for, what’s open, what you tried, what’s next, what you promised. The root shows it on the way in and prompts for it on the way out. In a tool full of agents this is the one place the agents earn their keep in the between: they can write the block for you, because they were there when you left.
It is the scheduler’s input. Once every organization reports state, need and staleness, choosing the next one stops being a matter of who was loudest. Tickler does not decide for you. It makes the decision visible, which turns out to be most of what a scheduler is.
what it is not
A root is not a unified inbox. An inbox merges traffic and calls the merge a view. It is the leakiest possible surface; every organization drains into it and none is legible. A root keeps the organizations separate and shows one line each.
A root is not a dashboard. A dashboard is inside an organization and shows that organization’s metrics. The root has no metrics of its own. It has one row per company and a column for how long you’ve been gone.
And a root is not something a vendor will build for you across the organizations you don’t own, for the structural reason above. It has to sit on your side of every boundary, reading from each organization whatever it is willing to expose, and holding the rest in blocks you and your agents write. Paperclip was the first place I could build one because it was the first place I owned all the organizations. The interesting problem is building the same surface over the ones I don’t.
Every switcher in that list assumes you know where you are going. Most of the time I don’t. I know where I’ve been, badly, and I know who is shouting. What I built is the place to stand while I decide, and the reason it took a tool full of agents to make me build it is that this is the first time I’ve had enough organizations for the standing to hurt.
You can’t switch from nowhere.