Customer Management

DataKubo supports a three-level hierarchy: Organization (you) → Community (your customer) → Resident (their end user). This guide covers how to manage each level.

Communities

Communities represent your customers — buildings, facilities, HOAs, co-ops, or any site you manage.

Creating a community

In the admin dashboard, navigate to Customers → Add Customer and provide:

• Name — the community or site name
• Admin email — the community administrator's email
• Tenant name — a unique identifier (used for webhook routing)

Communities can also be created via the API:

POST /api/v1/customers
Content-Type: application/json
X-API-Key: your_api_key

{
  "name": "Riverside HOA",
  "admin_email": "admin@riverside-hoa.com",
  "tenant_name": "riverside-hoa"
}

Customer Mode

When you have at least one community, the admin dashboard automatically enables Customer Mode — adding community-level filtering, navigation, and management features.

Residents

Residents are the end users within a community — tenants, occupants, or operators who view their own device data.

Adding residents

In the admin dashboard, navigate to Users → Add User and assign them to a community. Each resident gets:

• A personal login (magic link or Google OAuth)
• Access to their assigned devices only
• A read-only dashboard showing their consumption data

Device assignment

Devices can be assigned to residents in two ways:

1. Admin dashboard — drag and drop or use the assignment dialog
2. API — PUT /api/v1/devices/{dev_eui}/assign with the resident's ID

Unregistered devices

When devices send data before being formally registered, they appear in the Unregistered Devices section. From there you can:

• Assign them to a community and resident
• Bulk-register multiple devices at once

Data isolation

Every query in DataKubo is scoped to your organization. Within your organization:

• You (admin) see all communities, residents, and devices
• Community admins see only their community's data
• Residents see only their assigned devices

This isolation is enforced at the database level via Row Level Security — it's not just UI filtering.

Next steps

• White-Label Setup — brand the platform for your customers
• API Reference — manage customers programmatically