ThingHub — repositories, scopes, and access¶
ThingHub controls how the selected account organizes things and shares a scoped view with another account. Its three work areas are Repositories, Scopes, and Access.
Repositories¶
A repository is an account-owned placement boundary for visible things. The list shows each repository’s name, path, placement policy, and thing count.
Choose Create repository and provide a name and path.
Open the repository to review its placement policy and current things.
Place or move a thing into the repository when your grants allow it.
Update the placement filter when the repository should admit a different set of things.
Deleting a repository requires typed confirmation. Move anything that must remain available before deleting its placement boundary.
Scopes¶
A scope is an account-owned selection of things that can be used by downstream data and access flows. Create a scope with a clear name and filter, then use it as the resource boundary for telemetry queries, processing, or sharing.
Scopes do not move things between repositories. Deleting a scope removes the selection and can break grants or downstream configurations that reference it.
Cross-account access¶
The Access tab manages grants from a scope owned by the selected account to a different account. A grant names:
the owner account and scope;
the grantee account;
the allowed operations, such as telemetry read, attribute read/write, or command send.
To share a scope, choose Create grant, select an owned scope and grantee account, then grant only the operations required. Revoke the grant when the relationship ends. Revocation requires confirmation and is recorded in audit.
Two narrower shapes exist for marketplace partners, and both are opt-in and revocable like any other grant:
a software publisher can be given the telemetry of one app on your devices rather than the whole device;
a license authority can be given usage counters — how much each robot ran — without any access to the readings themselves.
Attribute writing is different from the rest: a device has one set of settings and therefore one author. You may delegate it to one account per scope, and a second delegation over the same scope is refused until the first is revoked.
See Sharing device data with another account for how to set each of these up and how to take them back.
Important
ThingHub is account-scoped. It does not create users, service users, or human identities. Identity administration belongs to DotID applications.
Note
Platform administrators can revoke an audited cross-account grant from DeckLoad. Tenant users cannot grant access to a scope they do not own.