specs/routes/R_SUSR

Account Settings- Users

Overview

The Users page allows Users to

  • View, edit and delete Users
  • Access the Custom Fields for a User,
  • Search for Users (by Name, Email or Badge ID),
  • View Filtered Lists of Users and view last connection datetime or online since datetime.

Model/Page Connections

Users

View

  • Users can Search for Users by clicking into the “Search users” field. Upon entering text, the Users are filtered to a list that only displays the Users with a Name, Badge ID or Email that match the entered text. The list is updated in real time without having to click a button.
  • Users can filter the Users by Role by clicking “Filter” and selecting the User Roles from the Radio Options.

Edit

  • Account Owner Users can Edit other Users’ information by clicking “Edit”.
  • This presents the User with a page in which all information fields listed below can be modified:
    • Profile Picture
    • Role
    • Account Creation Date
    • Email
    • Badge ID
    • Phone Number
    • Language
  • Once the changes have been made, the User can click “Save” to save the changes made to the User’s information.

Deactivate

  • Account Owners have the option to Deactivate users by clicking the “•••” button at the top right of the screen.
  • Clicking the button presents the User with a confirmation modal, that upon clicking “Deactivate Users” deactivates the specified Users’ account.

Create

  • Account Owners can Create Users by clicking on “Add user” at the top right of the screen.
  • The button presents the users with an Add User modal, where the Users inputs the following information:
    • Image
    • Name (Required)
    • Role (Required)
    • Email (Required)
    • Badge ID (required if operator)
  • Upon clicking “Add”, the newly created user receives an Email with the invitation to create the User Account and set a Password.

User Status

View

  • A user can view the last time any other user logged in, or their status since they were invited

User Fields

View

  • Each User has 1 Record associated with it.
  • User Table can be sorted by any Column in Ascending or Descending order.
  • User Fields and all values for all users can be exported via the "Export CSV" button in the top right of the User Fields page.

Create

  • Custom fields of the following data types can be created:
    • Text
    • Number
    • Boolean
    • Integer
    • Interval
    • Image
    • User
    • Datetime
    • Color
  • Account Owners can add Custom fields to the Table.
  • Account Owners can modify the data in each of the records for any of the columns.

Delete

  • Account Owners can delete Columns.
  • Account Owners can delete data from records in any of the columns.

Edit

  • Account Owners can modify specific column names.
  • Account Owners can modify column values for any of the User Records.

User Permissions

Any User with Tulip "viewing" permissions can...

  • View the Users page.
  • View the User Fields page.

Any User with "create" permissions for users can...

  • Add, Delete and Rename Columns in User Fields.
  • Modify values of each individual user within User Fields.
  • Create new users

Tests

IDName
QA-T4User Management : 01 - Create new administrator account
QA-T11User Management : 05 - Cannot Create an Admin with an Email Already In Use
QA-T16User Management : 08 - Create new operator account
QA-T122Group-Restricted LDAP : 04 - Admins should not be able to create Users
QA-T235User Table : 01 - User Table
QA-T260User Roles : 01 - Account Owners can add other Account Owners
QA-T262User Roles : 02 - Account Owners can create users
QA-T263User Roles : 04 - Account Owners should be able to deactivate/reactivate users
QA-T331LDAP Tulip Managed : 01 - Creating Users
QA-T333LDAP Tulip Managed : 03 - Deactivated Users can't Log In
QA-T387User Management : 11 - User Deactivation
QA-T520Users Table : 02 - Users Table Export

Requirements

IDRequirement
24Provide a managed way to define and maintain definitions of a user model including creating, editing, and disabling of users.
29Access and use of system and its components shall be limited to authorized users.
31User record has to include valid full name
43All user maintenance activities shall be recorded.
44Ability to revoke user access to the system both permanently and temporarily with appropriate authorization
114The user model includes ability to define access control to all elements of the system including libraries, administration, transactions, functions, apps, integrations, analytics, reporting, etc.c
375The user model includes ability to define access control for execution of model components. Ie. users, roles, groups that are allowed to execute a process step, data collection, completions, etc.
806All records shall be Enduring, ie. store, managed and unalterable for the full retention period.
810Provide managed authorized access to all records and electronic signatures including data, information, configurations, and data files.