System integrator playbook

Use this when you run several client sites from one Autoconnecto tenant. You do not need a separate “Customers” object or a separate cloud instance per client.

Shape the tree with assets

1. Create a SITE asset for each client (or each plant).
2. Under that site, add AREA and ZONE assets when the plant needs them.
3. Attach devices to the asset that owns them when the operator thinks of those devices as one place. Attachment is optional — a device can stay without an asset.

Open a site asset to see its devices. Point a dashboard or a rule at the devices on that asset when the work is site-scoped.

Give each client user the right Access Scope

Open Users. For a client operator (not an owner or admin):

1. Turn Global Asset Access and Global Device Access off.
2. Assign the client’s SITE (and child areas if needed) under Assigned Assets. Devices on those assets are included.
3. Or assign Device types (live) and/or Device profiles (live) when the person should see every device of that type or profile, including new ones added later — without editing the user again.
4. Or assign specific Assigned Devices when the list is small and fixed.
5. Limit Assigned Dashboards the same way when the person should not see every board.

Owner and admin accounts always see the whole tenant. Access Scope is for the people who should not.

Asset grants, device IDs, types, and profiles combine (OR). A device is visible if any of those grants match.

What stays out of this pattern

• Do not spin a new Autoconnecto instance per client unless a contract requires isolation.
• Do not invent a Customers screen. Assets plus Users Access Scope are the product path.
• Quiet hours and Monday energy mail stay off until you turn them on for that tenant.
• Profile alarm rules and a rule-engine alarm node both run. Say so when both exist so the client does not copy the same threshold twice.

Related

• Users
• Manage users
• Assets