Scopes for Operations Hub Users/Groups
This topic provides a list of scopes you can assign to users/groups for accessing Operations Hub.
To access both the designer and runtime features in Operations Hub, a user must possess,
at a minimum, the iqp.developer
and iqp.user
scopes.
Scope | Description |
---|---|
iqp.developer |
This scope is assigned to developer users. When a developer account is created, an associated application user account is automatically generated, sharing the same login credentials. Users with this scope have the ability to access pages for application creation, granting them access to both application design and runtime functionality. |
iqp.user |
This scope is assigned to application users. Users with this scope can only access those applications in Operations Hub to which they have been granted access. These users do not have the ability to access pages for application creation. Their access is solely restricted to the runtime functionality of the applications. |
iqp.clouduser |
This scope is assigned to users who want to use the REST API, mainly the M2M Device RESTful APIs. |
iqp.nodered |
This scope is assigned to users who want to access the Dataflow Editor. |
iqp.studioAdmin |
This scope is assigned to privileged users. Users with this scope can access the Administrator Console to configure global settings for an Operations Hub instance, such as the settings for email servers and the MQTT brokers for MQTT data interoperability. Note: This
scope does NOT grant access to Operations Hub designer or
runtime. |
iqp.tenantAdmin |
This scope is assigned to privileged users. Users with this scope gain
administrative authority at the Tenant or System level (in our case, we have
one tenant). They enjoy full administrative access to the Operations Hub
instance, with the exception of scenarios requiring membership in the
|