Workspaces
Last updated
Last updated
Inside each organisation there are many workspaces. Workspaces can be seen like folders. Workspaces can again have workspaces, much like a tree structure. This tree can be used to make a hierarchical structure.
See how this works out in the following example. OrganisationA has a workspace named B. Workspace B is assinged to a distributor of OrganisationA. The distributor has full control of Workspace B and creates workspace C inside for one of its customers. This customer has various zones and creates workspaces D and E insde workspace C.
Workspaces can be created at the organisation level by an admin of the organisation. The other way would be to create a workspace in a workspace where you have the rights to do so.
Users that are listed in the workspace have access to the workspace when they login. There are various roles which decide what the user can see or do inside the workspace. If a user is assigned to a workspace that has child workspaces, the user gains access to those.
Existing users from inside the organisation can be attached to a workspace. Otherwise a user can be created in the workspace users list. After creation a role can be assigned to a user. Creation or attaching a user wont send a welcome email or the like, but there is a bulkaction to send welcome emails available in the users list.
Users can be attached to workspaces. In the same manner users can also be detached from a workspace. Detaching is not the same as deleting. Detaching simply removes access of the workspace from the user, but the user still exists.
Viewer
Able to see some pages and edit nothing.
Editor
Able to see and edit everything but for workspaces inside the workspace
Admin
The same as the editor but then able to create and edit workspace inside the workspace. This is to say that only the admin of a workspace has access to all of the underlying workspaces.
See the image below for an example of a user with a viewer role in a workspace
There is a bulk action in the users list that allows editing of the users notifications channels like for exmaple events of type alarm per sms.
In a workspace there is access to all devices and their tags that are attached to the workspace.
Devices that are in a workspace come there via attaching from another workspace or automatic creation via a source.
There are also devices that get created by aggregates, but there is no manual creation of devices.
New devices via sources If you configure a source like for example Sensori Agent over FTP in a workspace, all devices coming into the platform via that source, in this case FTP credentials will be created inside the same workspace as the source. Same goes for other types of sources like a fetch API like OpenWeatherAPI.
If you have a device in another workspace that you want in some other workspace, you can attach this device to the workspace as shown below
All users in a workspace can access all dashboard of a workspace. There is a link in the edit dashboard page with a link to create a direct public access link. In the public link the user must put username and password as shown in the link with placeholders, otherwise the link wont work.
After creation of a dashboard tiles can be added to the workspace.
In the dashboard edit page its possible to select a customer dashboard theme. The themes are added to the platform by managing organisations. If not custom style is selected the default style is loaded. See the image below on how to set or remove a custom style
Dashboards are build up of blocks which are called tiles. These tiles can be charts, tables, images, maps etc.
Use the small arrow in the top right of the tile to go to its configuration page. Here the tile type can be selected.
Time series chart configuration
plotlines and bands
axis groups
stacking
line and bar charts
Gauge chart
State
Progress bars
Wind direction
Map
Image
HTML
This example will show how to create a non stacking multiple axis time series chart like the one shown below. As is easily seen the the image below it is not smart to put the rain and temperature on the same axis since they have quite a different measurement range which makes the bar chart hard to see. Because of this we will put the temperature and rain on separate axis later on in the example.
In the tile editing page select time series and click save.
3. Its now optionally possible to created coloured zones and lines in the chart via plot lines and bands
4. Now its time to add the first Y axis. There can be one or more tags per axis. There are a few settings for every tag in the axis group. See the example below where there are two temperature sensors on the same Y axis.
5. As discussed earlier temperature and rain should have separate axis to scale them properly. So lets create an additional axis and move the rain tag onto that axis and show it on the left side of the chart.
6. In the tile edit page. Remove the rain tag from the first axis group and then click add axis group.
Sometimes it is useful to have the Y-axis set to some static, not changing minimum and maximum value. Lets say 0 to 50. See the image below on how to achieve this. If you don't want the fixed values anymore, just type the word no into both fields.
If you are a bit familiar with HTML you can also opt for the HTML tile, then you are a bit more flexible in terms of alignment and such and the result is more refined. The best result can be achieved with is a company logo with a PNG extension, because then the background is transparent and you can make it a uniform whole with the rest of the dashboard.
Because there can be found an incredible amount about HTML codes and their function on the internet, Sensori facilitates this Tile type only.
For a company logo it is easiest to choose 'Image' and choose the internet address where the relevant logo is located. It can be any address, as long as the address is secured: so the URL must start with https. It doesn't have to be on the web server of the company in question either. Look for something that works best, e.g. with Google images, in terms of space at the edges so it doesn't get too cluttered.
A workspace can have many rules. Rules are used to capture business logic and for example create an alarm event when some value is crossed.
Refer to page on sources to see how to add devices to a workspace
Create a tile in some dashboard and go into editing as shown
See page for more on rules.
