Tenants & projects

Almost everything in the Center belongs to a tenant and, usually, to a project inside it. Getting these right early matters, because moving things between them later is harder than placing them correctly now.

Tenants

A tenant is an organisation. Tenants nest: an operator can hold resellers, who hold end customers. A tenant can see itself and everything beneath it, and nothing above or beside it.

Una (operator)
├── Reseller A
│   ├── Water Utility
│   └── Facilities Co
└── Reseller B
    └── Municipality

Reseller A sees Water Utility and Facilities Co. It cannot see Reseller B, and Water Utility cannot see its sibling.

The active tenant

The sidebar shows your active tenant. It is not decoration — it decides where everything you create lands, and what you see in every list.

If you belong to more than one tenant, check it before creating anything. A device created under the wrong tenant is invisible from the right one.

Projects

A project is a deployment: a set of devices, the integrations they talk through, and the routing and rules between them. Devices, integrations, routes and rules all belong to exactly one project.

How to split them

The useful question is "do these devices share a data pipeline?"

• Same project when devices feed the same destinations in the same shape. Twenty apartment blocks reporting to one billing system is one project.
• Different projects when the routing differs. A pilot deployment sending to a staging endpoint and a live rollout sending to production are two projects, even for the same customer.

Splitting more finely than that means repeating the same routes and rules in several places, and keeping them in step by hand.

Provider defaults

A project can hold provider defaults — settings new devices inherit rather than being retyped per device. For Sigfox that is the default device type new devices are created under; for LoRaWAN, the application and device profile.

A device can override what it inherits. The default is a convenience, not a constraint.

Where: Projects → your project → Provider defaults.

What sits where

Profiles and decoders are deliberately tenant-level: a device model does not change because you deployed it somewhere else, so you define it once and use it in every project.

Next