Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Drag & Drop Files, Choose Files to Upload You can upload up to 2 files.

How does the organizational hierarchy work in nRF Cloud

Throughout this course, we will frequently use terms like device, fleet, project, organization, cohorts, and device sets. These refer to different levels in the organizational hierarchy in nRF Cloud.

Organization, Project, and Cohorts are used to organize devices

Organization

The highest level of the hierarchy is the organization. It manages all projects and users in a given company. Generally, one company maps to one organization. API access to manage devices is done at the organization level using Organization Auth Tokens (OATs), which can be restricted to certain users and actions.

Project and Fleet

All devices in a project make up a device fleet. A single product line, with potentially varying hardware versions (such as EVT, DVT, and PVT) but the same underlying firmware, typically maps to a single project.

Definition

  • EVT (Engineering Validation Test): early prototype builds used to confirm that the core hardware design works and meets basic functional requirements.

  • DVT (Design Verification Test): builds close to the final design, tested to confirm the product meets its full specifications, including environmental, reliability, and certification testing.

  • PVT (Production Validation Test): the first builds made on the real production line, used to confirm that manufacturing can produce the product at volume with consistent quality.

Note

Do two product variations share the same firmware repository?

If so, these are likely best suited for one project. When data is grouped in the same project, issues are deduplicated, and trends are easier to identify.

Cohorts

Cohorts are mutually exclusive subsets of the Project device fleet and are used to manage OTA deployments. When first seen by nRF Cloud, devices are put in the default cohort. Cohort assignments can be updated in several ways, including via API, CSV upload, or manually through a device search.

Typical cohort groupings are Test or QA for an internal test group such as devices in the lab, Beta for a group of beta units that operate under more real-world conditions, and Prod for your production units. These groupings reflect expected targets for OTA rollouts.

Device Sets and Saved Device Searches

When grouping devices on different search criteria, you create a device set. These are temporary in nature and can be seen as a saved search result. Unlike cohorts, device sets can overlap. We will look closely at how to group devices in the next topic.

Cohorts vs. Device sets/saved search

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.