Working across multiple businesses.

Your bsns.cc account is one identity that can have a separate membership in each business you help operate. You can switch between those businesses without sharing their books, customers, employees, contracts, or permissions.

One graph per business

Each business is its own workspace, sometimes called a tenant. It has its own operating center or centers, enabled apps, roles, settings, and connected record graph. For example, one business can run around work projects while another runs around hive orders and inventory. A third can use both.

Connections never become cross-business edges. A Bill invoice owned by Acme cannot be attached to a GNA project or order. A Pact agreement in one business cannot supply signature status to another. Every endpoint of a connected record must belong to the same business.

Contacts are separate too. The same real-world person may be a customer of two businesses, but each business retains its own contact record and relationship history. The system does not create a durable cross-business customer record behind the scenes.

Switch before focused work

The business switcher changes the business you are working as. In a focused view, the orders, projects, invoices, agreements, expenses, people, messages, and customers you see all belong to that business. Anything you create names that business as its owner.

Check the current business before creating, approving, sending, or reconciling a record. A switch changes context; it does not move an existing record from one business to another.

Portfolio is a view, not a merged business

Portfolio view is available where a cross-business summary is useful and supported. It reads a bounded contribution from each business you are authorized to see, then combines those contributions for the page. work is the primary portfolio cockpit for attention, coordination, and approved financial summaries.

Every mixed result should keep its source business visible. That includes a task row, a summary contribution, Wren evidence, and a notice that some context was omitted. The source label is part of the record’s meaning, not decorative metadata.

Specialist surfaces remain focused on one business unless they explicitly offer a portfolio view. This includes bill, pact, tabs, crew, loop, ties, and most hive operations. Choose a focused business before acting in one of those surfaces.

Permissions are checked per business

Roles do not carry across businesses. You might be an owner in Acme, a team member in GNA, and an accountant in a third business. Each app checks that business’s membership, app access, role, and record permissions before returning context.

A connected link never grants access. Seeing a Work project does not automatically let you read its linked invoice or agreement, and portfolio membership does not authorize a write. Every write targets one business and is authorized again by the app that owns the record.

See Roles and permissions for the seat, app-role, and record-level checks applied inside each business.

How to read sources and omissions

Connected and portfolio views preserve provenance: the business, the owning app, the record address, and the time its source was checked. A checked-at time describes the read, not the age of the underlying business event.

A source marked unavailable was not guessed or replaced. An omission can mean a bounded view did not include every match, or that a source was unavailable or outside your permission. It does not prove that no other records exist. Switch into the named business or open the owning app when you need the complete specialist view.

Wren follows the same boundary

Connected reply drafting is scoped to the current business. Wren can use only the records and fields you are authorized to read there, and its evidence identifies the contributing source and checked-at time. A tenant-scoped request never receives another business’s data.

If a Wren experience explicitly offers portfolio scope, each business is authorized and labeled separately. In either scope, read visibility is not action authority: a supported change must be confirmed, target one business, and pass authorization again when it runs.

Where to go next

• How the apps connect— ownership, handoffs, freshness, and Wren context inside one business.
• Getting started— signup, trial pricing, and the setup wizard.
• Settings— team, branding, billing, and MFA.