Assign Views and Workspaces to different groups of users

Customize the application for different users by creating different views and workspaces. You can assign these to individual users or groups of users.


For this example we will use the following scenario:

  • Company A has two different divisions in Sweden, each with two vehicles: Stockholm (2 vehicles) and Uppsala (2 vehicles)
  • This company has five users: four operators (2 Stockholm, 2 Uppsala) and one administrator.
  • The operators in Uppsala are not interested in seeing the vehicles and information of Stockholm (and vice versa).
  • For each division, one of the operators is interested in seeing the map and the Vehicles panel only, without any other additional data (vehicle info, tracks, track points, events, etc).
  • None of the operators will have privileges to modify anything in the interface. They will only be able to log in to the platform and see their own division's information.
  • Any modification to the application will only be performed by the admin user.

This is the graphical summary of the schema proposed:

View, Workspace, and Role definitions

Before starting with the steps to configure this schema, we will explain the differences between View, Workspace, and Role:

A View is a filter for users to be able to see (or not see) certain elements of the application. This is regularly used when you want to hide/display vehicles or users to a certain group.

A Workspace is similar to the concept of a view, but applies to the number of available windows and tabs displayed in the screen. This is regularly used when you want to simplify the number of elements of visible objects to facilitate the reading of a map in the screen.

A Role is the set of privileges configured for a user or a group of users.

Configuration of the schema proposed

  1. Creating and assigning vehicles to tags
  2. Creating and assigning operators to tags
  3. Creating the views
  4. Creating the new workspace
  5. Creating a new role

1 - Creating and assigning vehicles to tags

The following steps should be performed as an Admin of the application (or as a Site Admin).

We will create vehicle1 and vehicle2 (both Device types), and will assign them to the tag Stockholm Vehicles.

When you create Devices, we recommend assigning them to tags because they will usually belong to a group. Tagging will simplify the management later on.

You can create the tag before creating a vehicle/device (in Admin->Tags) or during the vehicle/device creation process.

Create vehicle1, assign it to a tag Stockholm Vehicles, and then do the same with vehicle2.

Now is the turn for Uppsala vehicles. Create them in the same way with their corresponding tags and vehicle names for this division.

In our example, we created vehicle3 and vehicle4 and assigned both to a new tag called Uppsala Vehicles.

2 - Creating and assigning operators to tags

Now is the time to create operator tags.

We will create operatorA and operatorB and assign both to the tag Stockholm Operators.

Do the same with Uppsala Operators. Create operatorC and operatorD with a new tag called Uppsala Operators.

As we are logged with the Admin privilege, we will be able to see all the objects created:

Notice that we have added a name with more information about the area of this user (ex. vehicle1 - Stockholm). You can edit the name of the user by editing the user. NOTE: the loginID will be kept and cannot be modified once created.

3 - Creating the views

The next step will be to create the views. Go to Admin -> Views and select Add New View.

Now we will start creating a view for Stockholm Vehicles. As we want the operators to only see vehicles and not other operators, we only select Stockholm Vehicles.

Do the same creating an Uppsala view. Assign this new view to Uppsala Vehicles view. This is how your view list should now look:

4 - Creating the new workspace

At the beginning of this guide, we specified that one of the operators (from each division) wanted to see only the map view and the vehicles panel without any other additional windows.

To configure this we must create a new workspace. Go to Workspace -> View and uncheck everything except Map and Vehicles.

Save the workspace by selecting Workspace -> Save as

5 - Creating a new role

Now we must create a role for each of our requirements.

We are going to need four different types of roles (with default view and with Map Only view) per site (Stockholm and Uppsala)

First, we will go to Admin -> Roles and select Create copy of the role _Operator.

Fill in the information requested: Name, Description, etc. We will call this role 'Stockholm division.'

The next step for setting up the roles is to select which users to which this role applies. Select operatorA only.

Finally, we have to edit the Privileges part in the role settings. Remove any privilege you don’t want this operator to have:

- Admin : we removed any admin role for the operators.

- _EditUsers: roles (we do not want operators to modify any user data).

- _ReadData: we removed everything except _Me, Stockholm Operators and Stockholm Vehicles privileges.

- Views: we removed View Uppsala (we do not want Stockholm to see Uppsala data).

- Workspaces: we removed everything except the choice of _UseSharedWorkspace -> Map Only Workspace (operatorA will have the choice to select both workspaces).

If we want this new role to work properly, we need to disable the default _Operator role (otherwise it will override the settings for our new role). We will simply set that this _Operator role won’t apply to anyone by deselecting all the users.

Now we need to create a copy of the Stockholm division role, with the only difference being that we want to have the Map Only Workspace for operatorB.

Apply the new role to OperatorB

We have to remove the _EditSharedWorkspace for this user (he won’t be able to choose the default view).

The next step is to copy the same role we’ve used for Stockholm division and Stockholm division (map only). This time, we'll use it for the Uppsala operators.

- We create a copy of Stockholm division and we rename it Uppsala division. Change the _ReadData and Views privileges to the Uppsala ones.


- We modify the user from operatorA to operatorD

- We create a copy of Stockholm division (map only) and we rename it Uppsala division (map only). Do the same as before. Change _ReadData and View to Uppsala options.

- We modify the user from operatorB to operatorC


We have four roles for the different divisions, each with their corresponding workspaces and privileges.

To compare the different results, we will display what each type of user sees.

Administrator :

Stockholm operators (default view) logged in with operatorA:

Uppsala operators (map view only) logged in with operatorC. Notice that he is only able to see the vehicle3 and vehicle4 with the map and the Vehicles panel: