Bernard Engine · Doc

User management

A user (User) is a person who logs in to Bernard. A user has an e-mail address, a role, one or more departments, an administrator status, and an account that is either authorised or not. Users are stored at the root of the studio, in the Users folder.

Adding users

Reserved for administrators and for roles that have the Can Create permission on the Resource type.

  1. Go to the root: Navigate › Go To Root.
  2. In the Tree View, right-click the Users folder › Create › the user template.
  3. The Create New … window opens. Fill in: - Email: the person's address; it is their login; - Admin account: tick it to make the user an administrator.
  4. Click Create.

Bernard refuses an address that is already used ("This Email is already used") or invalid.

Authorising the account. A newly created account is not yet allowed to log in. Tick its Authorized property in the Property panel. The first time it is authorised, the person receives a welcome e-mail with a temporary password and their login information.

Completing the record in the Property panel: Role, Departments, and add the person to the users of the projects they work on (Project Users). Automatic assignment relies on these lists: see Assignment.

What can get in the way

First login and passwords

First login. With a temporary password, Bernard opens the Password Edition window: choose Save new password to set your own, or Keep auto generated password to keep the password you received.

A password has at least 12 characters, with lowercase letters, uppercase letters and digits.

Forgotten password. In the login window, fill in the company, the database and your login, then click Forgot Password ?. Confirm: a new temporary password is sent to you by e-mail.

Resetting a user's password (administrators): right-click the user › Reset Password, then confirm. The entry is only active for an authorised account.

Roles and permissions

Each user has one role. Roles are a studio category, managed in the settings (Root Settings). Creating a role creates its Role Setting: the set of its permissions.

Permissions are set in Bernard › Settings › Roles Setting (administrators), in three panels:

Panel What it sets Examples
Content edition rights what the role can create, delete and modify Can Create, Can Delete per object type; Can manually abort tasks; Can modify the state of tasks assigned to others (override assignees); Can modify active Workflow structures (Add/Remove tasks); permissions on template and reference files; entering and correcting time
Content display rights what the role can see and filter Can override View Presets (tab parameters) with custom filters; Can change the spreadsheet's query scope; Can view other users' working time (Access HR Data); Can access the Global Root Settings; Has access to projects settings
Role-based behaviours behaviours specific to the role Can create and modify global View Presets (tab parameters); Compute working time based on Timelogs (vs Attendance); Include extra weekday hours as Overtime

The full list is in Roles Setting.

Permissions per property. Each property has its own Read Access and Write Access lists (users and roles). For writing: nobody can write a read-only property; an administrator can always write; if Write Access is empty, everyone can write; otherwise only the listed users and roles can. In the spreadsheet, a column you cannot modify carries a padlock.

Reserved for administrators, whatever the role: Global Settings, Roles Setting, Administration Tools, Navigate › Login as, the Tech tab, changing a user's role.

Departments

A department has a name, a colour and a background colour. A user belongs to one or more departments; a task and a compound have a department. Departments are stored in the Departments folder of the settings.

Workstations

Reserved for administrators.

Each workstation is a Computer object, stored in the Computers folder. Bernard recognises it by its MAC addresses (MAC Addresses). An unknown workstation is created the first time Bernard starts, under the machine's name.

Property Effect
Authorized the workstation can open Bernard; an administrator authorises it, never from that workstation itself
Ip List Allow the IP addresses allowed for this workstation; if empty, any address is accepted
IP Address the workstation's current IP address, read-only
Always Open no automatic locking or closing (render workstation, screening room)

On a user, Authorize Any Computer immediately authorises the new workstations they use. It is ticked for an account created as administrator.

A refused workstation shows "Unauthorized Computer" and Bernard closes. Each user has a current workstation (Current Computer); Bernard › Check Current Computer checks it and offers to change it.

See also Security.

Logging in as another user

Reserved for administrators.

Navigate › Login as lists the authorised users. Choose one and confirm: Bernard restarts with that person's permissions and preferences, so you can test what they see. A banner shows it, and your administrator password is requested at restart.