Skip to content
Safeer App

icon picker
Profile

Edit profile data

1. Stakeholder: Employee
User Story 1: As a user, I want to enter my emergency contact information so that the company can only contact me in case of emergencies.
User Story 2: As a user, I want to modify any of my personal information by logging into my profile and selecting "Edit".
User Story 3: As a user, I want to be able to view all of my personal information on one page and make edits.
User Story 4: As a user, I want to be able to submit a data modification request to the HR department.
User Story 5: As a user, I want to receive a notification confirming or rejecting my data modification request from the HR department.
Acceptance Criteria:
AC 1.1: The employee can enter their emergency contact information.
AC 1.2: Emergency contact information includes at least phone number and contact name fields.
AC 2.1: The employee can access their profile page.
AC 2.2: The profile page displays all of the employee's data.
AC 3.1: The employee can edit each field of their personal data.
AC 3.2: The editing process happens within the same page.
AC 4.1: Upon saving the edits, the employee submits a modification request to the HR department.
AC 4.2: The modification request includes all the data that was edited.
AC 5.1: The employee receives a notification regarding the status of their data modification request (approval or rejection).
AC 5.2: The notification clarifies the changes that were approved or rejected.
2. Stakeholder: Human Resources (HR) Department
User Story 1: As an HR user, I want to view all employee data modification requests in a single list.
User Story 2: As an HR user, I want to view each employee's data modification request separately, showing each modified field and the proposed change.
User Story 3: As an HR user, I want to handle each change in an employee's data modification request in a detailed manner, following the same process as handling regular requests in the system, with the ability to:
Approve the change: Approval means accepting the proposed change and applying it to the employee's data.
Reject the change: Rejection means not accepting the proposed change, with the ability to write explanatory notes on what was rejected.
Redirect the request: Redirecting means transferring the modification request to another department that specializes in reviewing the proposed modification, with explanatory notes on what was redirected.
Request more information: Requesting more information means requesting additional data from the employee to determine the accuracy of the proposed modification, with explanatory notes on what was requested.
User Story 4: As an HR user, I want to send a notification to the employee confirming or rejecting their data modification request, explaining the changes that were approved or rejected, and detailing any explanatory notes.
User Story 5: As an HR user, I want to send a notification to the employee if their data modification request is redirected, explaining the department it was redirected to, and detailing any explanatory notes.
User Story 6: As an HR user, I want to send a notification to the employee if more information is requested to determine the accuracy of the proposed modification, explaining the data required, and detailing any explanatory notes.
Acceptance Criteria:
AC 1.1: The data modification request list displays all submitted requests.
AC 1.2: Each modification request appears separately with employee details and the data requested to be modified.
AC 2.1: The HR department can view the details of each modification request.
AC 2.2: The modification request details include each edited field and the proposed new value.
AC 3.1: The HR department has the authority to approve each modification individually.
AC 3.2: The HR department has the authority to reject each modification individually.
AC 3.3: When rejecting a modification, the HR department can write explanatory notes.
AC 4.1: The HR department sends a notification to the employee regarding the status of their data modification request.
AC 4.2: The notification clarifies the changes that were approved or rejected.
AC 4.3: The notification includes explanatory notes in case of any rejection.
AC 5.1: The HR department can redirect a data modification request to another department.
AC 5.2: Upon redirection, the HR department writes explanatory notes clarifying the reason for redirection and the department it was redirected to.
AC 5.3: The HR department sends a notification to the employee informing them of the request redirection.
AC 5.4: The redirection notification clarifies the department it was redirected to and the reason for redirection.
3. Stakeholder: Human Resources Management System (HRMS)
User Story 1: As an HRMS record, I want to store all employee data, including emergency contact information.
User Story 2: As an HRMS record, I want to allow users to enter their emergency contact information.
User Story 3: As an HRMS record, I want to allow users to modify their personal information.
User Story 4: As an HRMS record, I want to receive employee data modification requests from users.
User Story 5: As an HRMS record, I want to send employee data modification requests to the HR department.
User Story 6: As an HRMS record, I want to receive HR department responses to employee data modification requests.
User Story 7: As an HRMS record, I want to send notifications to users confirming or rejecting their data modification requests.
Acceptance Criteria:
AC 1.1: The HRMS can store all employee data, including emergency contact information.
AC 1.2: The HRMS allows users to enter their emergency contact information.
AC 2.1: The HRMS allows users to modify their personal information.
AC 3.1: The HRMS receives employee data modification requests from users.
AC 3.2: The HRMS sends employee data modification requests to the HR department.
AC 4.1: The HRMS receives HR department responses to employee data modification requests.
AC 4.2: The HRMS sends notifications to users confirming or rejecting their data modification requests.
AC 4.3: The notifications sent by the HRMS include details of the approved or rejected changes and any explanatory notes.
AC 5.1: The HRMS sends notifications to users informing them of their request redirection, including the department it was redirected to and any explanatory notes.
AC 5.2: The HRMS sends notifications to users requesting more information to determine the accuracy of the proposed modification, including the data required and any explanatory notes.
Notes:
The word "Employee" has been replaced with "User" in the employee-related user stories to make the language more generic.
البيانات الشخصية / Personal Data
Table 19
الاسم الكامل
البيانات الشخصية
Full Name
Yes
The employee's name should consist of letters and may include two or three parts. Example: "Mohamed A Ghali"
Personal Data
1
رقم الهوية
البيانات الشخصية
ID Number
Yes
Saudi National ID: a national ID number consisting of ten digits was issued.
Personal Data
2
تاريخ الاصدار
البيانات الشخصية
Release Date
3
جهة الإصدار
نعم
Issuing Authority
Yes
4
Identification Card
5
مدة سير بطاقة الهوية
البيانات الشخصية
Duration of validity of the ID card
6
البريد الإلكتروني
البيانات الشخصية
Email
Yes
The email address should consist of characters, numbers, and symbols, followed by "@" and then the domain name. Example: "XX_zz@XX.XX"
Personal Data
7
رقم الهاتف
البيانات الشخصية
Phone Number
Yes
phone numbers are assigned by telecommunications authorities or service providers and follow certain conventions based on country codes, area codes, and subscriber numbers
Personal Data
8
تاريخ الميلاد
البيانات الشخصية / معلومات الميلاد
Date of Birth
Yes
Day / Month / Year AD, e.g., 11-4-2024 AD, or can be in Hijri date format: 1445/10/2 AH.
Personal data/birth information
9
مدينة الميلاد
البيانات الشخصية / معلومات الميلاد
City of Birth
Yes
اختيار من المدن التي تخص الدولة
Personal data/birth information
10
وثيقة الميلاد
البيانات الشخصية / معلومات الميلاد
Birth document
No
Personal data/birth information
11
دولة الميلاد
البيانات الشخصية / معلومات الميلاد
Country of Birth
Yes
اختيار من دول العالم
Personal data/birth information
12
اضافة عنوان
البيانات الشخصية / العناوين
13
رقم المبني
البيانات الشخصية / العناوين
14
اسم الشارع
البيانات الشخصية / العناوين
15
الدولة
البيانات الشخصية / العناوين
16
المدينة
البيانات الشخصية / العناوين
17
نوع العنوان
البيانات الشخصية / العناوين
18
مدينة الإقامة
البيانات الشخصية / العناوين
City of Residence
Yes
اختيار من دول العالم
Personal data/residency information
19
دولة الإقامة
البيانات الشخصية / معلومات الإقامة
Country of Residence
Yes
اختيار من المدن التي تخص الدولة
Personal data/residency information
20
الجنسيات
البيانات الشخصية
Nationalities
Yes
تظهر الجنسية الاول علي اساس محل الميلاد و يمكن اضافة جنسات اخري و يجب وجود وثيقة اثبات لها
Personal Data
There are no rows in this table
Duration of validity of the ID card
User Story for Employee:
As an employee, I want to be able to view my ID card's validity period and renewal date so that I can renew it on time and avoid the risks associated with using an expired ID card.
Acceptance Criteria:
The employee can access the ID card information section of their profile through their user interface.
The ID card information section should display:
ID card validity period (in years).
ID card issuance date.
Required renewal date.
A notification should be sent to the employee one month before the renewal date as a reminder.
The required renewal date should be displayed on the employee's calendar.
User Story for HR:
As an HR representative, I want to be able to enter ID card validity information for employees, determine the required renewal date, and receive an automatic notification one month before the renewal date.
Acceptance Criteria:
The HR representative can access the ID card information section in an employee's profile through their user interface.
The user interface should allow the HR representative to:
Enter the employee's ID card validity period (in years).
Enter the ID card issuance date.
Automatically calculate the required renewal date.
Send a notification to the employee one month before the renewal date.
The ID card status (valid or expired) should be displayed on the employee's calendar.
The renewal date record for any documents should be displayed in a color agreed upon with the client.
The HR representative should be able to generate reports on ID card expiration dates for employees.
Address
User Story for Employee:
As an employee, I want to be able to add new addresses and edit existing addresses
and enter address details such as building number, street name, country, and city
and choose the address type (residence, mailing, city of birth, etc.)
and be able to request a review of any changes to my addresses
so that I can keep my contact information accurate and up-to-date.
Acceptance Criteria:
The employee can add new addresses through their profile information section.
The employee can edit their existing addresses through their profile information section.
The employee can enter address details such as building number, street name, country, and city.
The employee can choose the address type (residence, mailing, city of birth, etc.).
The employee can request a review of any changes to their addresses through their profile information section.
Employee address change requests should be reviewed by an HR representative before approval.
Employee addresses should be updated in the system after the request is approved.
User Story for HR:
As an HR representative, I want to be able to review and approve or reject employee address add/edit requests
and add a residence address for a new employee
and view all employee addresses in one place
so that I can ensure the accuracy and validity of employee contact information.
Acceptance Criteria:
The HR representative can access and review employee address add/edit requests submitted through the system.
The HR representative can approve or reject employee address add/edit requests based on their review.
The HR representative can add a residence address for a new employee when creating the employee's account.
The HR representative can view all employee addresses in the employee's profile information section in the system.
Nationalities
User Story for Employee:
As an employee, I want to be able to view and update my nationality information
so that I can keep my personal information accurate
and facilitate work-related international travel procedures.
Acceptance Criteria:
The employee can access the nationality information section of their profile through their user interface.
The nationality information section should display:
The employee's primary nationality based on birthplace.
A list of additional nationalities added by the employee.
An "Add New Nationality" option.
The user interface should allow the employee to enter new nationality information, including:
Country name.
Date of acquiring nationality (if applicable).
Nationality document identification number (if applicable).
The user interface should allow the employee to attach an image of the nationality document.
Nationality information update requests should be sent to an HR representative for review and approval.
The employee should be notified of the outcome of their nationality information update request.
Upon approval, the employee's nationality information should be updated in the database.
User Story for HR:
As an HR representative, I want to be able to review and process employee nationality information update requests
so that I can maintain the accuracy of employee information
and facilitate the management of work-related international travel procedures.
Acceptance Criteria:
The HR representative can access a list of employee nationality information update requests through their user interface.
The list of employee nationality information update requests should include information about each request, such as:
Employee name.
Requested new nationality.
Image of the nationality document.
The user interface should allow the HR representative to:
Review the nationality document.
Approve or reject the nationality information update request.
Send feedback to the employee regarding the request.
The employee should be notified of the outcome of their nationality information update request.
Upon approval, the employee's nationality information should be updated in the database.
ارقام الطوارئ / Emergency Contacts
Table 20
اسم الحقل
إلزامي
الفئة
Field Name
Mandatory
Specifications
Category
يتم الادخال من
1
اسم الشخص
لاء
ارقام الطوارئ
Person's Name
No
The employee's name should consist of letters and may include two or three parts. Example: "Mohamed A Ghali"
Emergency Contacts
Employee
2
رقم التواصل
مطلوب لو اسم الخانه اللي قبله اتكتبب
ارقام الطوارئ
Contact Number
No
phone numbers are assigned by telecommunications authorities or service providers and follow certain conventions based on country codes, area codes, and subscriber numbers
Emergency Contacts
Employee
3
صلة القرابة
مطلوب لو اسم الخانه اللي قبله اتكتبب
ارقام الطوارئ
Relationship
No
Choices
Emergency Contacts
Employee
There are no rows in this table
Employee User Story:
As an employee, I want to be able to add emergency contact information, so that my designated contact can be reached in case of an emergency, while ensuring that my emergency contact information is shared only with HR personnel and supervisors in the system.
Acceptance Criteria:
I should be able to add the name of my emergency contact.
I should be able to add the contact number of my emergency contact.
I should be able to specify the relationship between me and my emergency contact.
I should be able to save my emergency contact information.
I should be able to verify that my emergency contact information is shared only with HR personnel and supervisors in the system.
HR User Story:
As an HR employee, I want to be able to access employee emergency contact information, so that I can contact the employee's designated contact in case of an emergency.
Acceptance Criteria:
I should be able to access the employee's emergency contact name.
I should be able to access the employee's emergency contact phone number.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.