Multi-tenancy & org scoping

AcuSight is multi-tenant: each organization is a self-contained tenant, and everything in it — projects, devices, datasets, models, recordings, metrics — belongs to that org and is invisible to any other. This page explains how that isolation works. To administer your org, see Orgs, users & multi-tenancy.

​

The organization is the boundary

Every object in AcuSight carries the organization it belongs to. That org tag is the boundary: two customers can each have a project called “Line 1” and a device called “press-3”, and neither will ever see the other’s.

​

Scoping is enforced on every request

Isolation isn’t left to the UI to remember — it’s enforced at the data layer. When you sign in, your identity resolves to exactly one organization, and every read and write the platform performs is automatically filtered to it:

• The dashboard only ever loads your org’s data.
• The API derives the org from your token — there’s no org ID to pass, and no way to ask for another org’s data.
• Devices are provisioned into a single org and report only into it.
• The Co-Pilot answers only from your org’s data.

Because scoping happens server-side from your credentials, there’s no cross-org query to accidentally get wrong.

​

How users land in an org

Which org you join is decided by your email domain when you sign up — a company domain groups colleagues into one shared org; a personal address gets its own workspace. The mechanics (owner vs. member, first-user-claims-the-domain) are covered in Signing in and the Orgs guide.

​

No cross-org sharing

Because the org is a hard boundary, there’s no supported way to share a project, dataset, or device between organizations, or to move data across. Isolation is the point — it’s what lets teams and customers share one platform without sharing anything else.

​

Next steps