Content
General info
The users list page in the CRM allows administrators to perform CRUD (Create, Read, Update, Delete) operations on CRM users. Administrators can add new users, edit existing user details, or delete users from the list. The page provides intuitive action buttons for each user and a page with form to add new users.
User story
As a [CRM user],
I want to perform CRUD operations on CRM users from the users list page,
So that I can effectively manage user access and information within the CRM.
Visual design:
https://www.figma.com/design/I5CXH7H3ICD0vfA1kPbcVf/ROCKEN-jobs-%2F-talent?node-id=49880-106393&t=RKnLV3nan7jlQ1QD-4
|
#
|
Acceptance Criteria
|
|
|
01
|
Scenario: Adding a New User
GIVEN I am on the users list page,
WHEN I click the "+" button to add user,
THEN I should be presented with a page with form to enter the new user’s details,
AND upon submission, the new user should be added to the list.
|
|
|
02
|
Scenario: Editing a User
GIVEN I am on the users list page,
WHEN I click the "Edit" button next to a user’s entry,
THEN I should be able to modify the user’s details and save the changes.
|
|
|
03
|
Scenario: Deleting a User
GIVEN I am on the users list page,
WHEN I click the "Delete" button next to a user’s entry,
THEN I should be asked to confirm the deletion,
AND upon confirmation, the user should be removed from the list.
|
|
|
04
|
Scenario: Confirmation for Deletion
GIVEN I am deleting a user,
WHEN I click the "Delete" button,
THEN a confirmation dialog should appear,
AND only after confirming, the user should be deleted from the list.
|
|
|
05
|
Scenario: Viewing Updated User List
GIVEN I have added, edited, or deleted a user,
WHEN I view the users list table,
THEN the table should reflect the most recent updates,
AND show the correct number of users after any CRUD operations.
|
|
|
06
|
Scenario: Validation for Adding/Editing Users
GIVEN I am adding or editing a user,
WHEN I submit the form,
THEN the system should validate the inputs,
AND ensure all required fields are filled before saving the new or updated user information.
|
|
|
07
|
Scenario: Handling Errors in CRUD Operations
GIVEN I am performing a CRUD operation,
WHEN there is an error (e.g., missing required fields, duplicate email),
THEN I should see an error message indicating the problem,
AND the operation should not proceed.
|
|
