The cost of a second workspace
A separate account per client is invite chaos. People carry three passwords; reports never roll up; admins never close. A new member asks “which URL?” In Ontra the company record splits projects and access while login stays one. Holdings see totals in a separate view. A member does not fall into another client’s folder by accident. That is not security theatre — it is a scoped boundary.
Seats belong to the workspace; they do not multiply per company. “A separate seat for this client” inflates the bill and does not improve security. Reports open with a company filter. “This client’s effort” is answered without switching accounts. A designer only sees the assigned brand. A manager report sees totals, not the file tree.
- Do not open a second workspace
- A company boundary stops folder leaks
- Management totals are a separate view
- A member does not fall into the wrong client
- Seats do not multiply per company
Agency studio: one room, separate shelves
Rival brands can sit in the same studio. Open a company record instead of cloning accounts. A pitch shares with a passworded link, not a workspace invite. Winning work becomes a project. A lost pitch stays in archive and does not leak to another brand. An intern does not open the wrong folder because there is no grant — and no “admin” shortcut.
Holding: totals apart, content apart
Management reads effort, delay, and close speed with a company filter or a rolled-up view. The content tree does not open in that view. That is not curiosity control — it is a contract. One affiliate does not see another’s spec. A shared services team with `tasks.assigned_only` only sees assigned work. A shared admin does not open everything; the resource grant stops at the affiliate boundary.
Growth does not switch the package
A new client wants a new company record, not a new package. Board, docs, sprints, reports, and fine-grained access sit on one plan. What you pay for is the seat. “Reports on Pro, access on Enterprise” splits the team. In Ontra, growth is adding a person. Adding a company does not multiply seats. That is so the price stays explicit, not so a marketing sentence lands.
Same panel for holding and agency, different views
A second workspace produces three passwords, reports that never roll up, admins that never close. A company record splits projects and keeps login one. A member does not fall into the wrong client. Seats belong to the workspace; they do not multiply per company. “A separate seat for this client” inflates the bill and does not improve security. Reports open with a company filter. Management totals are a separate view; the content tree does not open there.
Rival brands can sit in an agency studio. A designer only sees the assigned brand. A pitch shares with a password, not a workspace invite. On a win the project opens. A lost archive does not leak to the other brand. In a holding, one affiliate does not see another’s spec. Shared services with `tasks.assigned_only` only see assigned work. A shared admin does not open everything; the grant stops at the affiliate boundary.
A new client wants a new company record, not a new package. Board, docs, sprints, reports, fine-grained access sit on one plan. Growth is adding a person. Adding a company does not multiply seats. That is so the price stays explicit. “Reports on Pro, access on Enterprise” splits the team. Ontra does not open that maze.
One login, scoped boundary, one bill
A second workspace produces three passwords and reports that never roll up. A company record splits projects and keeps login one. A member does not fall into the wrong client. Seats do not multiply per company. A separate seat inflates the bill. Reports open with a company filter. Management totals are a separate view; the tree does not open there. Rival brands can sit in an agency studio. A designer only sees assigned work. A pitch shares with a password. On a win the project opens. A loss does not leak.
In a holding one affiliate does not see another’s spec. Shared services live on assigned_only. A shared admin does not open everything. A new client is a new company record, not a new package. Board docs sprints reports access sit on one plan. Growth is adding a person. Adding a company does not multiply seats. The reports-on-Pro access-on-Enterprise maze is not opened.
A new member should not ask which URL. One panel, a company picker, a grant. The root of invite chaos is a second account. Close it on day one. As clients arrive, do not multiply workspaces — open a company record.
Each quarter read effort and delay with a company filter. Do not open the content tree in that view. That is not curiosity control; it is a contract. One panel makes this contract possible. A second workspace makes it impossible.
Billing and reports
Seats belong to the workspace; they do not multiply per company. Reports open with a company filter. “This client’s effort” is answered without switching accounts.
More posts
Product
When tasks and docs share one record, work stops scattering
List, board, and roadmap are views of the same record. A decision is made once and every surface shows the same truth. This piece explains how a pile of tools delays delivery and how Ontra binds one record.
Security
Fine-grained access lets the team breathe
Not everyone needs every project. Add project, folder, and list access on top of roles, and privacy becomes the default. In agencies and holdings the leak is rarely malice — it is the oversized shortcut “admins see everything.”
Setup
Finish the workspace in the 7-day demo, not the tool tour
No credit card. When the demo ends the app locks and data stays. Load real work in week one instead of touring screens: a project, roles, the live sprint, the docs tree, and the first report. A showroom tour does not pick a tool; a sitting record does.
