Resource/Data Sharing becomes an exceptionally useful feature to divide resources and data between different orgs. It provides a variety of benefits that includes effective and efficient use of shared resources, economics of scale, availability of resources and so on. This section presents you the different ways of managing resources to your end customers.
Managing end customer using Sub Organizations
It is possible to group each end customer things/connections into Sub-Orgs. Managing the end customers using sub organization have the following advantages/disadadvantages:
- Requires devices to publish using different application tokens, to insure the Thing is in the correct sub org. (Increased device configuration complexity)
- Requires Thing Definition updates, Trigger, Device Profiles and so on to be imported to all affected sub orgs if there is an update. (Increased maintenance)
- Isolates data of each end-customer by sub-orgs, providing enhanced security.
- Easy to provide an end customer visibility to things, as authorization is per sub-org.
- The portal’s billing report will provide usage counts by sub-org.
- Easy to stack with security tags and sharing to stack security layers.
- It it possible for you to use triggers and sub-organizations to define their own triggers.
For more information on adding a Sub-Organization, see Adding a Sub-Organization.
Managing end customer using Tags and Security Tags
Managing the end customers using Tags/Security Tags have the following advantages/disadadvantages:
- Simplifies device configurations (All use the same application token)
- Simplifies configuration updates, such as Thing Definition updates, Trigger, Device Profiles and so on. (only one to update)
- Each customer’s things & roles are distinguished via use of tags & security tags. (requires more configuration of things & user roles)
- The portal’s billing report will not separate counts via tags or security tags
- Trigger functionality is not security tag aware, thus from triggers you can access all data
For more information Tags and Security Tags, see Using Tags and Using Security Tags.
Managing end customer by Sharing Things/Connections
Managing the end customers by Sharing things from a parent org to an end customer’s sub org have the following advantages/disadadvantages:
- Requires the sharing of the Thing as a part of the Thing’s configuration process, need to know the sub org to share to.
- Cloud trigger updates are still required per sub org, if there are updates.
- Doubles the Thing counts (and fees). One in the parent org, and one for the shared thing in the end customer’s sub org.
- Easy to provide an end customer visibility to things, as authorization is per sub-org.
- Easy to provide a master view of all things, as all will be in the parent org.
- The portal’s billing report will provide usage counts by sub-org.
- Cloud triggers can be defined in either the parent or the sub-organization depending on the use case
For more information Sharing, see Sharing Things and Connections.