Skip to main content
Projects are the unit of work in the platform. They group the apps you’ve registered and the sessions those apps produce. Every project lives inside a tenant inside an organization, a logical grouping for one product or initiative.

Create a project

From the developer portal, open Projects and choose New project. You’ll set:
  • Name and optional description.
  • Region: where this project’s data is stored. New projects default to N. Virginia (us-east-1). Choosing a different region is an Enterprise feature; Enterprise plans can pick from the standard region list (e.g. eu-west-1, ap-southeast-2, ca-central-1). Need a region that isn’t listed? Contact support.
  • Tenant: which tenant workspace inside your org owns the project.
  • Status: active, archived, or setup_incomplete for a project you’re still wiring up.
A project starts empty. Add apps next.

Add apps to a project

Each registered App in a project has a platform app_id assigned by the dashboard. Register one from inside the project; see Register an app. One project can hold multiple apps; a given app_id belongs to exactly one project at a time.

Wearables

For connecting wearable integrations and viewing the data they produce, see Connect wearables & view data, which covers the full setup flow end to end.

Sessions

A session is one usage event captured on-device and ingested into the platform. Sessions surface under the project’s Sessions tab once the apps in the project ingest them and the app is allowlisted for ingestion. See API keys → Ingestion access for how that allowlist works, and Synheart Session for how sessions are produced on-device.

Project settings

Each project exposes a settings page for renaming, archiving, and managing access. Archive projects you’re no longer working in rather than deleting them; archived projects stay readable but step out of the active list.

Patterns that work well

  • One project per environment: keep dev, staging, and prod data isolated.
  • Project per study or cohort: for research, give each cohort its own project so you can scope keys and access cleanly.

Next

API keys

Generate scoped keys for the apps in your project.

Connect wearables & view data

Connect a wearable integration and explore the session data it produces.

Synheart Session

See how sessions are produced on-device before they reach the platform.