...
Difficulty: expert
Content
Table of Contents | ||||
---|---|---|---|---|
|
Learning Objectives
After reading this article, you’ll be able to:
Understand Roles/Profiles set-up in Workplace
Select relevant roles per Workplace user
Create environment specific roles as per your needs
Roles and Profiles can be
...
used to differentiate users, their rights and options in
...
Workplace. If a user has multiple roles assigned to him/her, the overall
...
scope of the user will be the sum total/union of all individual roles.
Follow this link to learn more about Cobundu User Management.
How to access:
Go to Workplace back-end https://studio.cobundu.com/
Login with your credentials
Select
...
Roles & Profiles
...
...
Standard Roles
“No roles found, unprivileged user”: user can access End-user
...
Workplace touch points (GO + Workplace App)
...
. As a default, in Studio, every user is created without a role (through excel upload, a role can immediately be assigned to a user).
“Admin” role is needed to access Studio (will only give access to current
...
environment)
...
and DeviceControl (for KioskApp and Workplace App)
Note |
---|
! With great power comes great responsibility: make sure the Admin-user is aware of the Studio basics. Having access to Studio |
...
means being able to configure general Settings, Sensor Devices, User Management, Floor plan configuration etc => a basic training in Studio is needed before access can be given. |
"Developer" role is typically assigned
...
to users who have the rights to view/consume/integrate
...
Workplace APIs
...
.
...
These users
...
might be external developers who work on integrating
...
Workplace with their systems,
...
and should not have access to
...
Workplace touchpoints.
On Workplace Web (GO), users with only developer role are automatically redirected to the API documentation upon login and cannot use any other front-end features.
On Workplace App, an alert will be shown and the user will not be allowed to continue.
...
Environment Specific Roles
Depending on the needs
...
in your environment, other roles can be added to the
...
environment (select "Add New")
...
- “Cleaning/WorkAssistant” role is needed to give access to specific overviews with workorders, see configuration instructions on Work Assistant
- Access to dashboards on GO can be restricted per role (under tenant > Tenant Setup > Dashboards)
...
, for example access to dashboards on Workplace Web (GO) can be restricted for a specific role.
Role based reservation scope definition
Create a Workplace Role which restricts the user to see only a limited scope of locations, and to be able to make reservations only in those locations.
Step 1: Role definition
...
Add new role
...
of Type "Reservation Restriction", and describe the reservation scope of a user
...
by using any of the following 3 parameters:
...
location type
location scope
zone scope
Location Type - Each role can be defined for either only rooms, only workplaces, or both. | ||
Location tree with check boxes | Locations scope (buildings) - The locations in which the user is allowed to book a room or desk. |
...
...
Departments scope - Rooms and workplaces can be linked to departments in Cobundu under the Location Grouping settings. When a set of departments are enabled in a role, the user can only book rooms/workplaces linked to that department. An option called "User's / my department" exists, which points to the user's own department for dynamic restrictions per user.
Zones scope - Rooms and workplaces can be linked to zones in |
...
Workplace under the Location Grouping settings. When a set of zones are enabled in a role, the user can only book rooms/workplaces linked to that zone. |
Step 2: Role assignment
...
As a default, Workplace users don’t have any roles assigned. No restrictions are applicable to
...
the users.
An administrator can assign one or more roles of type reservation restrictions to a user. If a user has multiple roles assigned to him/her, the overall reservation scope of the user will be the sum total/union of all individual roles.
...
See Users & Groups for more information on user creation.
When a Reservation Restricted Role is assigned, the user can only book rooms/workplaces described within the role on Workplace touch points. Reservation requests for other locations will be blocked by
...
Workplace.
...
Info |
---|
The restrictions only apply for bookings made via |
...
Workplace, and not for requests originating in the underlying IWMS from other sources ( |
...
from Outlook through Exchange or IWMS web portal). Also the other way around: IWMS restrictions will always be respected as it’s the underlying IWMS which owns the reservation data. |
Settings in IWMS | Settings in |
---|
...
Workplace | Result in IWMS | Result in |
---|
...
Workplace | ||||
---|---|---|---|---|
No restriction / Allowed to book room X | No restriction / Allowed to book room X | -> | Allowed to book room X | Allowed to book room X |
No restriction / Allowed to book room X | Restriction set on room X | -> | Allowed to book room X | Not allowed to book room X |
Restriction set on room X | No restriction / Allowed to book room X | -> | Not allowed to book room X | Not allowed to book room X |
If a user is trying to book a resource that is outside of his/her reservation scope, an error message is shown
Step 3: Booking assistance
This part is still a WIP and will be available in a future release.
In the Cobundu touchpoints (like the Workplace app), the search functionality for rooms and workplaces will take the reservation restrictions into account and exclude the resources which are not available for the user.
...
Search
Live Search |
---|