specs/models/M_USER
User
A user is a digital object representing a person that has any access right to the Tulip system. There are two types of users:
- Users- Users with some level of access to Tulip
- Operators- Users with access to the Tulip Player for running Tulip apps
The User Model contains the following Models:
When actions are completed in Tulip or Tulip Player, they are always attributed to an individual User.
Tulip Users can authenticate via the following methods:
- LDAP
- SAML
- Email/Password
- Badge ID (Tulip Player only)
See the Authentication Methods page for more details
Once a user is created, it is permanently stored in the Tulip account. It can be “deactivated” so that the user is no longer allowed to log into Tulip or the Tulip Player.
If a user is “deactivated”, then another user can use their badge ID.
Fields
| Name | Description |
|---|---|
| Name | The name defined by the user |
| User ID | The unique identifier of the user. This value is often mapped to an organization's auth system. |
| The email address given by the user. Required for login. | |
| Password | The password given by the user. Required for logging into Tulip. This value is often mapped to an organization's auth system. |
| Badge ID | A unique alphanumeric ID assigned by a Tulip user with user “create” privileges. |
| Role | A specific role from the list of User Roles |
| User Fields | A list of custom fields that are given to every user by a user with access to the “User Fields” page |
| Status | The user’s status around logging into Tulip- either active, deactivated or pending |
| Image | A custom image that will be displayed as a headshot |
| Phone Number | A phone number that can be texted from a Tulip app. A user can only enter their own phone number. |
| Language | By default, Tulip will attempt to use the same language as the browser default. The user can manually set this to another language. |
Tests
| ID | Name |
|---|---|
| QA-T4 | User Management : 01 - Create new administrator account |
| QA-T5 | User Management : 02 - Receive welcome e-mail and registration link |
| QA-T6 | User Management : 03 - Password Creation for New Admin |
| QA-T10 | User Management : 04 - Log in with new admin |
| QA-T11 | User Management : 05 - Cannot Create an Admin with an Email Already In Use |
| QA-T12 | User Management : 06 - Add phone number to admin account |
| QA-T13 | User Management : 07 - Upload image for Admin icon on /account |
| QA-T16 | User Management : 08 - Create new operator account |
| QA-T120 | Group-Restricted LDAP : 02 - Users in the configured admin group can log in |
| QA-T121 | Group-Restricted LDAP : 03 - Users operator group can log in |
| QA-T122 | Group-Restricted LDAP : 04 - Admins should not be able to create Users |
| QA-T123 | Group-Restricted LDAP : 05 - Deactivated users should still be able to log in |
| QA-T171 | SAML : 02 - Admins can log in to Factory using SAML |
| QA-T172 | SAML : 04 - Operators can log into Player using SAML |
| QA-T177 | SAML : 08 - Operators whose role changes to Administrator in SAML should be promoted to Administrator in Tulip |
| QA-T178 | SAML : 07 - Administrators whose role changes to Operator in SAML should be demoted to Operator in Tulip |
| QA-T260 | User Roles : 01 - Account Owners can add other Account Owners |
| QA-T261 | User Roles : 03 - Account Owners can edit other users' profiles |
| QA-T262 | User Roles : 02 - Account Owners can create users |
| QA-T263 | User Roles : 04 - Account Owners should be able to deactivate/reactivate users |
| QA-T264 | User Roles : 05 - Administrators should not be able to manage users |
| QA-T265 | User Roles : 06 - Tulip Table Supervisors should not be able to manage connectors |
| QA-T266 | User Roles : 07 - Tulip Table Supervisors should not be able to manage the shop floor |
| QA-T267 | User Roles : 08 - Viewers should be unable to modify data in Tulip |
| QA-T279 | User Management : 10 - Users can change their password |
| QA-T331 | LDAP Tulip Managed : 01 - Creating Users |
| QA-T332 | LDAP Tulip Managed : 02 - Users can log in via LDAP |
| QA-T333 | LDAP Tulip Managed : 03 - Deactivated Users can't Log In |
| QA-T387 | User Management : 11 - User Deactivation |
Requirements
| ID | Requirement |
|---|---|
| 43 | All user maintenance activities shall be recorded. |
| 50 | Disallow deletion of content that have been used in execution of a work order or material processing. |
| 104 | All tracked information must be accessible and viewable for users in a workflow. |
| 813 | All data shall be Attributable; data must be identified to the person who did the data collection. Records shall include information about how the data was acquired, action/activity performed, where and and when |
| 842 | Support specific number of concurrent users as defined by customer license agreements and SLAs |