specs/models/M_USER_STATUS
User Status
A user can have one of three statuses:
- Invited - The user record has been made in the system, but this user has not accepted their account via the email invitation. The user cannot log in until they have used the welcome email to set up their account
- Active - The user currently has the access rights granted by their assigned role.
- Inactive - The user record is still in the system, but that user has no access to the system. This occurs when the user has been “deactivated”.
Fields
| Name | Description |
| Status | The name of the status |
| Time Since Active | The amount of time the user has been logged in (if they have an active session), or the amount of time since the last time they logged in. |
Tests
| ID | Name |
|---|---|
| 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-T123 | Group-Restricted LDAP : 05 - Deactivated users should still be able to log in |
| QA-T174 | SAML : 03 - Admins should be able to log into Player |
| QA-T176 | SAML : 06 - Deactivated users can still log into SAML with certain configuration |
| QA-T263 | User Roles : 04 - Account Owners should be able to deactivate/reactivate users |
| QA-T333 | LDAP Tulip Managed : 03 - Deactivated Users can't Log In |
| QA-T387 | User Management : 11 - User Deactivation |
| QA-T660 | User Management : 03 / Password Creation for New Admin with wrong input |
Requirements
| ID | Requirement |
|---|---|
| 842 | Support specific number of concurrent users as defined by customer license agreements and SLAs |