Organizations on Proficloud.io

On Proficloud.io, an organization is a self-contained unit with strict tenant separation. Each organization maintains its own users, devices, and data.

When a user registers for the first time, an organization is automatically created, and the user is assigned the administrator role. Additional organizations can be created later, but devices and data cannot be transferred between them.

This architecture ensures data integrity and clear ownership while supporting flexible multi-user collaboration.

Role and permission management

Proficloud.io offers a granular permission system within each organization. Users can have different roles across organizations while using the same login credentials.

• Admins have full access to all devices and user management.
• Editors and Viewers can only access the devices assigned to them.
• Only admins can invite new users or change permissions.

This structure enables clear separation of responsibilities while supporting collaborative workflows.

Scenario 1: One organization with multiple customers

Click on image to enlarge

In this setup, the system integrator creates a single organization and invites customers to join as Editors or Viewers.

• The integrator books Smart Services and registers all devices.
• Customers receive access to selected devices only.
• Customers cannot invite new users, manage devices, or access user management.

This model is ideal when:

• The integrator wants full control over the environment.
• Customers need access to specific dashboards and data, but not full platform features.
• The integrator offers Proficloud.io services as part of a larger solution.

Example setup:

• Integrator books “Time Series Data 200” with 10 devices, each using 20 metrics.
• Each customer is granted access to one or more devices.
• Customers see only what they’re assigned — no access to other users or devices.

Benefit: Cost-effective, centralized control with the option to resell access or dashboards.

Scenario 2: One Organization per Customer

Click on image to enlarge

In this model, each customer gets their own organization, providing maximum independence.

• The integrator sets up the customer’s organization and invites them as Admin.
• Devices and services can be booked by either party.
• The customer has full access to user and device management.

After setup, the integrator can:

• Remain in the organization to provide support.
• Or exit the organization entirely, handing it over to the customer.

This model is ideal when:

• The customer should manage their own data and users.
• Clear separation of data and billing is required.
• Long-term autonomy is a goal.

Benefit: Customers can fully utilize all platform features while the integrator remains available for support if needed.

Comparison: One Organization vs. One per Customer

Feature / Functionality	Scenario 1: One Organization with Multiple Customers	Scenario 2: One Organization per Customer
Organisation structure	One shared organization managed by integrator	Separate organization for each customer
Smart Service booking	By integrator	By integrator or customer
Device registration	By integrator	By integrator or customer
User roles	Integrator: Admin Customer: Viewer/Editor	Customer: Admin (optional), Viewer, Editor
Access to User Management	Only the integrator	Yes, if customer is set as Admin
Access to Device Management	Only the integrator	Yes, if customer is set as Admin
Visibility of other users/devices	Customers see only assigned devices	Full control over devices and users
Responsibility for operation	Integrator	Customer (after handover)
Billing flexibility	Centralized (per organization)	Individual billing per customer possible
Recommended when…	…the integrator offers a managed service	…the customer needs full control
Reselling services possible	Yes, integrator manages access and pricing	No, each customer controls their own org
Handover to customer possible	No – integrator stays in control	Yes – integrator can leave after setup