How the apps connect.

bsns.cc is one operating system, not a collection of apps you have to reconcile by hand. Each app still owns the records it is responsible for, while secure links let the rest of the system show the context and handoffs that belong around your work.

Those links stay inside one business. They do not copy records, merge permissions, or make one app the owner of another app’s facts.

Two operating centers

Most businesses begin from one of two centers. work centers projects and service delivery. hive centers products, inventory, orders, and shop operations. A business can use either center or both; neither has to live inside the other.

The same specialist capabilities can support either center:

• ties owns the customer relationship and its authorized history.
• loop owns external conversations and customer replies.
• bill owns invoices, balances, and payment status.
• pact owns agreements, signatures, and their audit history.
• tabs owns expenses, vendor bills, approvals, and reconciliation.
• crew owns people, time, and operating-capacity context.

What you can do from a Hive order

An authorized Hive order can bring the common next steps to the order page while each specialist app keeps control of its records:

• Start an external message in loop with the order and customer context attached. Linked issues, replies, and unread state can then appear with the order.
• Open an invoice draft in bill with the order customer and line, discount, shipping, and tax snapshots prefilled. Bill rechecks access and owns the invoice and collection lifecycle.
• Create an agreement from a pact template and see the linked document and aggregate signature status from Hive.
• See explicitly attributed tabs costs and approval/reconciliation status, plus permission-filtered crew time and execution context.

A handoff prefills known context; it does not silently send an invoice, collect payment, sign an agreement, or create accounting or staffing records. You finish that action in the app that owns it.

What you can do from a Work project

A Work project uses the same pattern. It can open a Bill invoice draft tied to the exact project and preselect a customer when there is one unambiguous linked customer. Billable lines still belong in Bill and are not inferred from a generic project.

The project can also start a Pact agreement from a template, show linked agreement and signature status, show attributable Tabs and Crew context, and keep linked Loop conversations close to the work. Access is checked again by the app that owns each record.

Ties brings the relationship together

ties gives the customer relationship a durable home. Its timeline can combine the Work and Hive activity you are allowed to see, including relevant Loop issues, without moving those source records into Ties. When several records are shown together, their owning app remains visible.

Freshness, access, and missing context

Connected panels load separately so a slow specialist app does not hide the order, project, or customer you opened. A checked-at time tells you when that panel last read its owning app during the page load. It is not the time the underlying invoice, agreement, expense, or time entry was created.

A specialist panel is normally absent when that app is not enabled for the business. When the app is enabled but your current role cannot read its context, the panel explains that access is required.

• Temporarily unavailable means the owner could not be read just then. The page does not guess or substitute data; try again or open the owning app.
• Access required means your current membership or app role does not allow that context. Ask a business owner or admin if you believe you should have access.
• Omitted means a bounded view did not include every matching record, or some records were unavailable or not visible to you. It does not mean the omitted records do not exist.

What Wren can see

In connected reply drafting in loop, Wren can assemble relevant facts from the same authorized Work or Hive context available to you. Its evidence disclosure identifies the source app, what was checked, when it was checked, and whether a source was unavailable, unauthorized, or omitted from the bounded context.

Wren does not receive blanket database access. Tenant boundaries, app roles, object permissions, field visibility, and sensitive-data exclusions still apply. Seeing a fact also does not authorize Wren to change it: any supported write remains a separate, confirmed action and is authorized again when it runs.

See Roles and permissions for the full app-by-app matrix, including the difference between a Hive Cashier and Technician.