Licenses, User Types & Access Management
Introduction of User Types
Valsight is licensed based on the number of named users. A named user is any natural person authorized by the customer to use the software under the terms stated in the overarching Valsight Agreements.
The maximum number of users is defined by the license. The licensed users are differentiated by user types, whereas each type allows users to use different parts of the application. The current usage and capacity can be viewed on the license page by system admins.
Supported user types:
Analyst/Basic User: Can access simulation workspaces and build charts, but not change any data (no Scenario Manager access). Can view and create presentations.
Simulation User: Same as the Analyst/Basic User + can access simulation workspaces, change data in the Scenario Manager, can upload/update/edit data sources and use Workflows.
Model User: Same as Simulation User + can create and edit projects, models, dimensions, and data sources and use and edit Workflows.
Unrestricted User: Same as Model User + can be a global admin which lifts all restrictions and enables full access, e.g. to settings and configuration.
Note: User types only impose restrictions on top of access rights, users still need to be given specific rights for each project/model/workspace/presentation/workflow that they want to access. Additionally, this also means that users with a restricted user type (e.g. being a basic user) will not be able to open a project although they have been given access to it.
Valsight Access Management
While there are 4 types of licenses, Valsight offers additional options on how to further define access rights for advanced customization among users.
Places to edit the Valsight Access Management | ||
Licenses | The initial access rights for each user are defined by the license type. Being able to choose between 4 different types of users, enables individually composed license packages. | |
Valsight settings | Access rights | The access rights settings can be reached via the Valsight settings. Here, permissions can be granted in an overview of projects, Models, Workspaces and presentations. Learn more. |
User management | The user management can be reached via the Valsight settings. Here, you can edit the permissions of each individual user. Learn more. | |
Group management | The group management can be reached via the Valsight settings. Here, access rights can be provided by assigning users to groups. Learn more. | |
Data permission classes | The data permission classes can be reached via the Valsight settings under 'Projects > Security'. Data permissions define which data a user can access. They can be configured for a project and will be enforced for Charts in Simulation Workspaces. Learn more. | |
Overview of User Type Access Limitations
Information
The premise for users to have the access rights mentioned in the table below is that the according access rights have been granted.
The table shows the maximum possible access for a specific license type. To reach that maximum, proper access rights have to be given.
The unrestricted user has the same abilities as a Model User except for the ability to be a global admin.
The access to projects, models and workspaces can further be split into 2 levels each. This enables the split between users actively working in a space and users viewing the space for information purposes.
By creating a new project (as any eligible user type) you automatically become the project admin for the respective project.
Project | Model | Workspace | |||||
|---|---|---|---|---|---|---|---|
Can Use | (Project/Global) Admin | Read-Only/Can View | Can Edit | (Project/Global) Admin | Limited Access | Full Access | (Project/Global) Admin |
In the table below, we only focused on those limitations that have a direct influence on the user type.
Analyst/Basic User | Simulation User | Model User | Unrestricted User | ||||
|---|---|---|---|---|---|---|---|
Project (Creating a project automatically makes you that project’s admin) | Can Use | Can Use | Can Use | Project Admin | Global Admin | ||
No change in rights if selected as project admin (In the access control, it's shown as “Can Use” although I have set it to project admin) |
|
|
A Modeler that is project admin, can only have “Can Edit” rights on a model! A Modeler that is project admin, can only have “Full Access” on a workspace! |
| |||
Model Creating a model automatically gives you “Can Edit” rights for that model | Read-Only/Can View | Read-Only/Can View | Read-Only/Can View with Can Use rights for project Read-Only/Can View not possible when Modeler is project admin. | Can Edit with Can Use rights for the project | Can Edit with Project Admin rights for the project A Modeler that is project admin, can only have “Can Edit” rights on a model. | Global Admin | |
|
Can be selected to have “Can edit” rights, but does nothing
|
|
|
|
| ||
Workspace Creating a workspace automatically gives you Full Access on that workspace | Limited Access Cannot have Full Access. | Limited Access | Full Access | Limited Access and Can Use on project Limited Access not possible when the user is project admin. | Full Access and Can Use on project If you create a workspace (even with Limited Access) you have full access automatically. | Project Admin A modeler that is project admin, can only have “Full Access” on a workspace. | Global Admin |
|
|
|
|
|
|
| |
Data Source | Can Use/No Access on project level | Can Use/No Access on project level | Project Admin on project level | Can Use on project level | Project Admin | Global Admin | |
|
|
|
|
|
| ||
Export Manager |
|
|
|
|
|
| |
Data Permission Class | Can Use/No Access on project level | Can Use/No Access on project level | Project Admin on project level | Can Use on project level | Project Admin | Global Admin | |
|
|
|
|
|
| ||
Dimension |
|
|
| Project Admin | Global Admin | ||
|
| ||||||
Can Use on project level | Project Admin | ||||||
Workflow |
|
|
|
|
| ||
Presentations |
|
|
| Global Admin | |||
| |||||||
Can be Global Admin | No | No | No | Yes | |||
Advanced Configuration
User types are chosen when creating an account and can also be changed later. Disabled users do not count towards the limit. If you have reached the capacity for a certain type and create a new user, that user will be created as disabled. Enabling a user is allowed as long as you don't exceed the capacity of that user's type. When logging in via SSO and auto-creating users, the default type of a new account is unrestricted but can be changed by modifying the 'autoCreatedUserType' option from the config.yml (see Common SSO Options).