View as Markdown

Organizations

An Organization is the top-level tenant in ControlCom Connect. All Devices, Variables, Assets, Locations, Dashboards, and users belong to one Organization, and nothing crosses the boundary: data, users, and resources are isolated between Organizations.

Overview

You typically have one Organization per company or per business unit, depending on how separate the operational data needs to be. The Organization holds your subscription, your branding, your security settings, and the resource hierarchy under which everything else lives. The switcher at the top of the sidebar shows which Organization you are working in; users who belong to several can switch between them there.

Signing in lands you on the Organization's Overview page: device health, Locations in alarm, active alarm counts and recent events at a glance, a summary of your alarm group subscriptions, and a shortcuts card where you pin the Dashboards, Diagrams, Locations or Assets you use most.

The Organization Overview page in ControlCom Connect showing device health, alarm and event tiles, recent events and pinned shortcuts
The Organization Overview: health, alarms and events for everything in the tenant, on one page

Resource Hierarchy

Organization
└── Locations
    └── Assets
        └── Devices
            └── Variables

The hierarchy is logical, not mandatory. A Device does not have to belong to an Asset, and an Asset does not have to belong to a Location. But populating the upper levels unlocks site-based filtering, Asset-level dashboards, and multi-site rollups. The Platform Overview shows how the pieces connect, with a worked example from field sensor to asset.

Team and Access

Users belong to the Organization and get their access through roles. Every Organization starts with three built-in roles (Administrator, Editor, and View) and you can define your own, choosing exactly which features each role allows. API keys are bound to roles the same way, so programmatic access follows the same permission model as people.

Inviting users, building custom roles, and the permission model are covered in Team and Roles.

Settings and Billing

Organization-wide configuration lives in Settings: the Organization's name and details, API keys for programmatic access, the subscription plan with billing and usage tracking, and audit logs. Logos and colors are managed separately in Branding, which controls how the platform looks for everyone in the Organization.

Was this page helpful?