Spaces

TABLE OF CONTENTS

Introduction

The platform uses the concept of Spaces. Because it is a very important concept in will be explained explicit. To use the platform in the intended way, the concept of Spaces is introduced in the following:

Spaces

Spaces represent IoT projects (German: IoT Projekte, Vorhaben, PoCs, Trials) in which several users, from potentially different organizations, participate. The administrator determines what a space actually represents. Typically a user that has been invited to a space will be able to select a space after login, in order to enter that space. All views are then scoped to this space (in addition to being scoped to the users permissions). What a user can actually create, read, update, delete etc. within a space depends on the permissions of the user. If the user switches between modules, the scoping to the current space remains effective. The user can exit the space and enter another space. The user can enter a space again at anytime, unless an administrator revokes the underlying invitation (i.e. the permission that was added to that user based on a successful invitation). Devices are also contained by spaces. This logic can be accessed by the device manager, where each device is created within a particular space. Within that space, a Device is also represented by automatically created containers of a container type Device.

How to use spaces for your organisational unit?

Every new customer should be onboarded in their own Space to ensure that only persons of that organisation have access to its assets, dashboards and machine dashboards. For customer A and B you should create separate Spaces A and B.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.