Summary
This article provides information about the two types of Organizations in Cloud Portal: Partner and Customer.
Partner Organization
A Partner Organization is the entity STEP Partners use to create, oversee, and rapidly switch between multiple Customer Organizations.
A Partner Organization must be set up, managed, and used by STEP Partners, also known as SI (System Integrator). Upon creation, a Partner Admin may create Customer Organizations and invite customer individuals as users. Authorized Partner users switch between Customer Organizations to monitor, maintain, and troubleshoot devices.
The available roles for Partner Organization are Super Admin, Admin, and User.
- The Partner Super Admin can perform all actions and is the only one who can create Partner Admins.
- The Partner Super Admin or a Partner Admin can create Customer Organizations.
When a Partner Admin creates a Customer Organization, they are automatically assigned the technician role and can create user accounts, register devices, configure devices, and manage licenses for that Customer Organization.
Only Partners assigned the Technician role have access to a Customer Organization. Only Partner Super Admin or Admins may create Customer Organizations.
Customer Organization
A Customer Organization is the entity that contains devices, systems, software and licenses. A Customer Organization is managed, and used by customer staff, and authorized partner staff.
When a Customer Organization is created by a customer, it may at any point invite one (and only one) Partner Organization to support them, as well as remove them.
Alternatively a Customer Organization may be created by a partner from a Partner Organization, who may manage multiple Customer Organizations.
The available roles for Customer Organization are Admin, Super Admin, and User.
- A Customer Admin can create other User accounts, register devices, configure devices, and manage licenses.
- A Customer Super Admin can create other Admins as well as perform the same actions as a Customer Admin.
Devices only exist within a Customer Organization, where Partners with Technician roles can to configure them.
A Partner can create a Customer Organization and its Customer Super Admin. To do so, the Partner Admin with Technician role assigned would log in and switch to the Customer Organization and add the first User, who, by default, becomes the Customer Super Admin.
NOTE: Each Customer Organization can only be attached to one Partner
Organization, but can have any number of Partner technicians assigned. A Partner Organization may be attached to multiple Customer Organizations,
which allows a Partner Technician to switch seamlessly between Customers
to support them.
Partner Roles in Connected Customer Organizations
When a Partner Organization connects to a Customer Organization and a Partner Admin assigns (dispatches) members to it, the role each member receives depends on the application:
| Application | Role |
| Portal | Installer |
| OnCloud | Technician |
| OnCAFE | Technician Cardholder or Technician Admin |
| HealthPro | Customer The HealthPro admin claims Installers assigned in Portal and grants them a Customer role. |
| BLAZE | Customer The BLAZE admin claims the Installers in Portal and grants them a Customer role. |
NOTE: For Portal, OnCloud, and OnCAFE, a dedicated Partner role is granted
automatically when members are dispatched. For HealthPro and BLAZE, the app
admin reclaims those members and grants a standard Customer role rather than
a dedicated partner role.
When using apps that behave differently together, a Partner member can be given access in one of two ways:
- Option 1 - Dispatch from a Partner Organization
Create a Partner Organization and dispatch members to the Customer Organization (for example, they receive the Technician Admin role in OnCAFE), then have the HealthPro admin claim them (for example, as Manager).
Use this option if you use OnCAFE and BLAZE together. You do NOT need option 1 if you use BLAZE only.
- Option 2 - Invite into a Customer Organization
Create a Customer Organization and invite members directly (for example, the Cloud Portal admin claims them as Admin), then have the HealthPro admin claim them (for example, as Manager).