Users

A username is needed to login to MIKE OPERATIONS.

The “admin” user is available by Default.

This user has administrator rights in MIKE OPERATIONS. Administrators can create users and workspaces as well as assign users to a workspace.

New users can be created in the System Explorer using the context menu of the Users node.

Parameter	Description
Username	The name of the user, specified when logging in to MIKE OPERATIONS.
Full Name	The full name of the user.
Administrator	A value indicating whether the user is administrators. Administrators can create users create other users, create namespaces and associate users to workspaces.
Trusted Account	A trusted Windows account that has trust relation with the log on user.
User Type	The user type: Native authentication Password is specified on the user in MIKE OPERATIONS. Active Directory authentication The Windows account specified is used for authentication.For Active Directory authentication, no password is stored on the user in MIKE OPERATIONS.
E-mail	Optional e-mail of the user.
Password	The password for the user when using Native authentication. The password should contain at least 8 characters. It is recommended to use a strong password. A strong password: Has 12 Characters, Minimum: You need to choose a password that is long enough. There is no minimum password length everyone agrees on, but you should generally go for passwords that are a minimum of 12 to 14 characters in length. A longer password would be even better. Includes Numbers, Symbols, Capital Letters, and Lower-Case Letters: Use a mix of different types of characters to make the password harder to crack. Isn’t a Dictionary Word or Combination of Dictionary Words: Stay away from obvious dictionary words and combinations of dictionary words. Any word on its own is bad. Any combination of a few words, especially if they are obvious, is also bad. For example, “house” is a terrible password. “Red house” is also very bad. Does Not Rely on Obvious Substitutions: Do not use common substitutions, either — for example, “H0use” isn’t strong just because you have replaced an o with a 0.

My Profile

The user can update user information when selecting “My Profile”.

Workspaces

MIKE OPERATIONS are using workspaces to hold data. In a PostgreSQL database a workspace is equal to a schema.

Every workspace (schema) in the MIKE OPERATIONS contains the same database definitions (tables, columns, functions etc.). This means that workspaces can be used for keeping data separated based on user defined locations, model types, area etc.

By default, the workspace “workspace1” is created. If no other workspace is added, “workspace1” will be contain all data of MIKE OPERATIONS.

The workspace1 schema in the PostgreSQL PgAdmin

The workspace contains tables and functions used by MIKE OPERATIONS.

Create a workspace

Administrators can create new workspaces from the context menu of the “Workspaces” node. In the System Explorer.

Specify the workspace name

When selecting OK, the workspace will be created in both the System Explorer and in the database with a generated name.

The workspace table of the master schema will contain information about the workspace.

Associate users

In order to give a user access to a workspace, the user must be associated to a workspace.

Administrators can associate users, using “User associations…” on the context menu of the workspace node.

Select the user and the role of the user in the workspace.

Role	Description
Workspace_lead	Can add, edit and delete data: GIS manager Set private symbology.
Workspace_member	Can add, edit and delete data: Time Series Manager Create new providers Set time zone GIS manager Create new providers. Set workspace symbology for feature classes and rasters. Scenario Manager Can include all parameters on a scenario.
Workspace_reviewer	The user can view data, but not add, edit or delete data.