Structure and Permissions

The following figure depicts the ownership of the main components in Octave:

These components are structured as follows:

• Company: when an organization registers for Octave, an organization account representing that company is added to Octave, and all objects created by the users of the account are grouped/partitioned within that account. Multiple organizations can be registered and selected within the Octave dashboard.
• Group(s): developers can organize Modbus slave devices into groups.
• Token: each organization is assigned a Master Token that can be used to invoked Octave’s REST APIs. This token can be found in the bottom left hand corner of the Octave dashboard.
• Device(s): one or more Octave-enabled devices can be registered for the company and administered through the Octave dashboard. Each device can be associated with zero or more tags. This allows you to aggregate events from the same stream on multiple devices.
• Action(s): developers create both Edge Actions and Cloud Actions to execute business logic on the edge device and in the cloud respectively.
• Stream(s): contain events for a device.