Branches, teams, and access

A branch groups data and operational context for one location. Your organization determines which branches you can access.

Keep each location organized

Administrators create branches and manage branch membership. A branch has its own database schema and API key. Members work within the branches assigned to them; administrators manage the organization's branch set.

Connect a device to the right branch

In api.yaml, enter the branch ID, its API key, and the backend base URL. Ingest authenticates using the branch key; never use a user sign-in token as an edge API key.

api.yaml · identity excerpt, not the complete file

api:
  branch_id: YOUR_BRANCH_ID
  key: YOUR_BRANCH_API_KEY
  url: https://YOUR_BACKEND/api/v1
  # Keep ingest, buffer, and request sections from the sample.

Prepare the tables you write to

Camera routing names detection tables. Rules can name a notifications table, and monitor rows target nodes. The backend ingest endpoint expects the destination table to exist in the branch schema with compatible columns; generation does not create backend tables.