During the onboarding process, you will be asked to provide a list of users and determine what role they should have in the system. Below is a breakdown of all the role options for Noda to help you make the best decision for each of your users.

Noda is organized into four hierarchical levels:

Learn more about the difference in this article.

Each user is associated with a single organization and company. A user who is designated as Org Admin will automatically have access to all companies, portfolios, and buildings within their organization. Otherwise, a user can be granted to a subset of portfolios or buildings within their company, as well as those within other companies in their organization.

Portfolio-level users automatically have access to all buildings within a single portfolio. If/when new buildings are added to that portfolio, all portfolio-level users will have access to that building as soon as it is enabled in Noda.

A company can consist of multiple portfolios. We see this with enterprise customers who want to organize their buildings into groups such as by region or campus. In this case, portfolio-level roles need to be assigned individually for every portfolio in a company.

Portfolio-level roles are:

Building-level users can be added to a single building or a set of multiple buildings. For example, if your Noda portfolio is divided into regions, you may have a set of users who need access to 5 out of the 25 buildings in your portfolio and another set of users who need access to 7 different buildings,.

Building-level roles are:

​