SRS Documentation

Damex Digital Client Portal

Shakhawat Ullah Badhon

25th May, 2023
SRS Documentation for Damex Digital Client Portal

Table of Contents
Table of Contents 1
Introduction 4
Functional Requirements 5
1. Admin Portal 5
1) Orders 5
2) Customers 5
3) Packages 5
4) Product Catalogue 6
5) Projects 6
6) Resource Management 6
7) Tickets 6
8) Live Chat 6
9) Users 6
10) Team 7
11) Reports 7
12) Notification Settings 7
13) Permissions & Preferences 7
2. Employee Portal 7
1) Tasks 7
2) Projects 7
3) Live Chat 8
4) Tickets 8
5) Clients 8
6) Team 8
7) Reports 8
3. Client Portal 8
1) Account Management 8
2) Manage Subscription 8
3) Invoices 9
4) Payment Method 9
5) Tasks 9
6) Analytics and Reports 9
7) File Access 9
8) Live Chat 9
9) Ticket Submission 9

1
SRS Documentation for Damex Digital Client Portal

10) Notifications 10
11) Feedback and Ratings 10
Non-Functional Requirements 10
1. Performance 10
1.1. Response Time: 10
1.2. Scalability: 10
2. Security 10
2.1. Authentication: 10
2.2. Data Protection: 10
2.3. Backup and Recovery: 11
3. Accessibility 11
3.1. Usability: 11
3.2. Compatibility: 11
3.3. Assistive Technology: 11
Reliability 11
4.1. Availability: 11
4.2. Disaster Recovery: 11
4.3. Error Handling: 11
Maintenance and Support 12
5.1. Upgrades and Maintenance: 12
5.2. Support: 12
Compliance 12
6.1. Legal and Regulatory Compliance: 12
6.2. Industry Standards: 12
Example User Flow 12
Admin User Flow 12
Employee User Flow 13
Client User Flow 14
Use Cases 14
Admin Portal 14
1.1 Orders 14
1.2 Customers 15
1.3 Packages 15
1.4 Projects 15
1.5 Resource Management 16
1.6 Tickets 16
1.7 Live Chat 16
1.8 Reports 16

2
SRS Documentation for Damex Digital Client Portal

1.9 Permissions & Preferences 17

2. Employee Portal 17
2.1 Tasks 17
2.2 Live Chat 17
2.3 Tickets 17
2.4 Reports 18
3. Client Portal 18
3.1 Account Management 18
3.2 Manage Subscription 18
3.3 Invoices 18
3.4 Tasks 19
3.5 Live Chat 19
3.6 Ticket Submission 19
3.7 Notifications 19
3.8 Feedback and Ratings 20
Assumptions 20
Dependencies 21
User Interface Guidelines 22
1. Overall Design 22
2. Homepage 22
3. Login/Registration 22
4. Client Portal 22
5. Admin Portal 23
6. Employee Portal 23
7. Accessibility 23
8. Performance 23
9. Feedback 23
10. Error Handling 24
Data Requirements 24
1. User Data: 24
2. Service Data: 24
3. Order Data: 24
4. Support Data: 25
5. Project and Resource Management Data: 25
6. Analytics and Reports Data: 25
7. Feedback and Ratings Data: 25
Acceptance Criteria 26
Page Structure 26

3
SRS Documentation for Damex Digital Client Portal

Admin Portal: 26
Employee Portal: 28
Client Portal: 28

Introduction
This Software Requirements Specification (SRS) document describes the requirements and
specifications for developing a Client Portal for our Digital Marketing Agency, an integrated
platform designed to streamline operations, improve client interaction, and enhance internal
communication and productivity.

The primary aim of this portal is to provide our clients with a seamless and intuitive interface to
access our digital marketing services, manage their subscriptions, monitor the progress of tasks,
access analytical reports, and communicate effectively with our team. Furthermore, the portal is
intended to facilitate better resource allocation, task management, and revenue tracking within
the agency, ensuring operational efficiency and superior service delivery.

This SRS outlines the expected functionality of the different components of the portal, including
the Admin, Employee, and Client interfaces. It also provides details about the interaction between
these components and the necessary rules and guidelines for their implementation.

The document is intended to serve as the main guide for the development team throughout the
design and development process, and to act as a reference point to minimize any ambiguity or
confusion. It will ensure that the software developed meets the needs of the users, adheres to
the quality standards of the organization, and aligns with our overarching business objectives.

It is expected that all stakeholders involved in the development process, including project
managers, designers, developers, quality assurance personnel, and business analysts, will
thoroughly understand and adhere to the specifications and requirements outlined in this
document.

This SRS document is divided into different sections that deal with the system's functionalities,
user interfaces, performance, design constraints, and other attributes in detail. By clearly defining
these aspects, we aim to ensure a coherent understanding and smooth execution of the project.

4
SRS Documentation for Damex Digital Client Portal

Functional Requirements
This section outlines the functional requirements of the client portal for our digital marketing
agency. Each function is described in detail to provide a comprehensive understanding of the
system's capabilities. These functional requirements are divided into three main sections: the
Admin Portal, the Employee Portal, and the Client Portal.

1. Admin Portal
The Admin Portal is the control center for the entire platform, allowing the admin to manage
various aspects, from orders and customers to packages and team management.

1) Orders

1.1 New Orders: The system should allow the admin to view all new orders placed by
clients.

1.2 Invoices: The system should allow the admin to generate and manage invoices for all
orders.

2) Customers

2.1 Create New Customer: The system should enable the admin to create new customer
profiles, including relevant details like name, contact information, and preferred services.

2.2 All Customers: The system should provide a comprehensive view of all customers,
including their order history, active subscriptions, payments, and contact information.

3) Packages

3.1 Create New Packages: The system should allow the admin to create new service
packages, define their features, set their pricing, and make them available for purchase.

3.2 All Packages: The system should provide a list of all created packages and their
details.

5
SRS Documentation for Damex Digital Client Portal

4) Product Catalogue

4.1 Products: The system should allow the admin to add or remove products/services
offered by the agency.

4.2 Plans: The system should allow the admin to create different plans for each
product/service.

4.3 Addons: The system should enable the admin to offer addons to the main packages
or products.

4.4 Charges: The system should allow the admin to set up one-time or recurring charges
for each product, plan, or addon.

4.5 Coupons: The system should provide an option for the admin to create, manage, and
deactivate discount coupons.

5) Projects

5.1 Task Management: The system should provide a dashboard where the admin can
assign tasks to employees, track their progress, and mark them as completed.

6) Resource Management

6.1 Workload Tracking: The system should provide tools for the admin to monitor the
workload of each employee, ensuring balanced task allocation.

6.2 Performance Monitoring: The system should have capabilities for the admin to track
employee performance, including task completion rate, client feedback, etc.

7) Tickets

7.1 Ticket Management: The system should allow the admin to view, assign, and manage
the resolution of support tickets raised by clients.

8) Live Chat

8.1 Chat Management: The system should enable the admin to monitor live chat
communications between the clients and the team, and participate if necessary.

9) Users

9.1 User Management: The system should allow the admin to create, edit, or deactivate
accounts for employees, assign roles, and manage permissions.

6
SRS Documentation for Damex Digital Client Portal

10) Team

10.1 Team Overview: The system should provide a comprehensive overview of the team,
including roles, workloads, and performance metrics.

11) Reports

11.1 Report Generation: The system should enable the admin to generate detailed reports
on agency performance, client performance, revenue, and employee productivity.

12) Notification Settings

12.1 Notification Customization: The system should allow the admin to customize the
settings for system-wide notifications.

13) Permissions & Preferences

13.1 Permission Management: The system should enable the admin to set and manage
permissions for various roles within the system.

13.2 Preferences: The system should allow the admin to set preferences for system
behaviours, defaults, and personalized settings.

2. Employee Portal
The Employee Portal is a user interface designed for agency employees to manage their tasks,
interact with clients, and monitor their workload.

1) Tasks

1.1 Task Dashboard: The system should display a list of tasks assigned to the employee,
along with their status and deadlines.

1.2 Task Management: The system should allow employees to mark tasks as completed
or communicate any issues or delays.

2) Projects

2.1 Project Access: The system should allow employees to access details of projects they
are assigned to, including the client's brief, deadlines, and other relevant information.

7
SRS Documentation for Damex Digital Client Portal

3) Live Chat

3.1 Chat Participation: The system should allow employees to engage in live chat
conversations with clients, answering queries, and providing updates.

4) Tickets

4.1 Ticket Response: The system should enable employees to respond to and resolve
support tickets assigned to them.

5) Clients

5.1 Client Access: The system should provide employees with access to relevant client
information necessary for their tasks, subject to permissions set by the admin.

6) Team

6.1 Team Communication: The system should provide tools for employees to collaborate
with team members, including internal chat and project discussion forums.

7) Reports

7.1 Report Submission: The system should allow employees to submit reports upon task
completion, including a summary of work, hours logged, and any notable outcomes or
challenges.

3. Client Portal
The Client Portal is designed to provide clients with a user-friendly interface to manage their
accounts, make payments, interact with the agency, and monitor the progress of their projects.

1) Account Management

1.1 Profile Management: The system should allow clients to manage their account details,
including contact information, and payment methods.

2) Manage Subscription

2.1 Subscription Management: The system should provide clients with an interface to
view, purchase, upgrade, downgrade, or cancel service packages.

8
SRS Documentation for Damex Digital Client Portal

3) Invoices

3.1 Invoice Access: The system should allow clients to view past invoices and payment
history.

3.2 Online Payments: The system should provide a secure payment gateway for clients
to make payments for their subscriptions.

4) Payment Method

4.1 Payment Details: The system should provide a secure method for clients to add, edit,
or remove their payment methods.

5) Tasks

5.1 Task Tracking: The system should provide an interface for clients to track the progress
of tasks related to their projects.

6) Analytics and Reports

6.1 Report Access: The system should enable clients to access reports related to their
projects, such as Google Analytics & Search Console data.

6.2 Custom Reports: The system should provide options for clients to generate custom
reports based on their needs.

7) File Access

7.1 File Management: The system should provide a secure platform for clients to
download and upload files, such as reports or project resources.

8) Live Chat

8.1 Live Chat: The system should provide a live chat feature for clients to communicate
with the team for immediate support or query resolution.

9) Ticket Submission

9.1 Support Tickets: The system should provide an interface for clients to create, track,
and close support tickets if they encounter any issues or have queries.

9
SRS Documentation for Damex Digital Client Portal

10) Notifications

10.1 Alerts: The system should send alerts to clients about updates related to their
account, tasks, invoices, and more.

11) Feedback and Ratings

11.1 Feedback Submission: The system should provide an interface for clients to provide
feedback or ratings on completed tasks and overall service.

This functional requirements section is comprehensive, but it is crucial to remember that

requirements may change or evolve based on business needs, customer feedback, and during
the process of design and development.

Non-Functional Requirements
1. Performance

1.1. Response Time:

The platform must have great load times, and response times, and should feel buttery smooth.

1.2. Scalability:

The platform should be able to handle a large number of users simultaneously without a
decrease in performance.

2. Security

2.1. Authentication:

The platform should use secure authentication methods, such as password hashing or
multi-factor authentication, to protect user accounts.

2.2. Data Protection:

The platform should use encryption to protect user data and prevent unauthorized access.

10
SRS Documentation for Damex Digital Client Portal

2.3. Backup and Recovery:

The platform should have backup and recovery procedures in place to ensure the integrity and
availability of user data.

3. Accessibility

3.1. Usability:

The platform should be easy to use and navigate for users with varying levels of technical
expertise.

3.2. Compatibility:

The platform should be compatible with all major web browsers and mobile devices.

3.3. Assistive Technology:

The platform should be accessible for users with disabilities, including support for screen readers,
captioning, and audio descriptions. Optional.

Reliability

4.1. Availability:

The platform should be available 24/7 with minimal downtime.

4.2. Disaster Recovery:

The platform should have procedures in place to recover from disasters or system failures.

4.3. Error Handling:

The platform should handle errors gracefully and provide meaningful error messages to users.

11
SRS Documentation for Damex Digital Client Portal

Maintenance and Support

5.1. Upgrades and Maintenance:

The platform should be regularly updated and maintained to ensure its reliability and security.

5.2. Support:

The platform should have a support system in place to assist users with technical issues or
questions.

Compliance

6.1. Legal and Regulatory Compliance:

The platform should comply with all applicable laws and regulations related to e-learning, data
protection, and privacy.

6.2. Industry Standards:

The platform should adhere to industry standards for e-learning, including accessibility and
interoperability standards.

Example User Flow

Admin User Flow
1. Login: The admin logs into the system using their credentials.
2. Dashboard: The admin arrives on the dashboard which presents a high-level overview of
the system including recent orders, active tasks, new customer registrations, and recent
tickets.
3. Customer Management:
a. The admin selects the 'Customers' option in the menu.
b. The admin can view all customers, and select a specific customer to view their
details.
c. The admin can create a new customer profile by entering relevant details such as
name, contact information, and service preferences.

12
SRS Documentation for Damex Digital Client Portal

4. Package Management:
a. The admin navigates to 'Packages' in the menu.
b. The admin can view all packages, edit existing ones, or create new packages by
specifying the services included and the pricing.
5. Task Assignment:
a. The admin selects 'Projects' in the menu and views the ongoing projects.
b. The admin assigns tasks to employees by selecting the employee and specifying
the task details.
6. Ticket Management:
a. The admin navigates to 'Tickets' in the menu.
b. The admin can view all tickets, assign them to employees, and monitor the ticket
status.
7. Logout: The admin logs out of the system once their tasks are complete.

Employee User Flow

1. Login: The employee logs into the system using their credentials.
2. Dashboard: The employee arrives on the dashboard, which presents a summary of their
assigned tasks, open tickets, and ongoing projects.
3. Task Management:
a. The employee selects 'Tasks' from the menu.
b. The employee can view their assigned tasks and select a specific task to view its
details.
c. The employee can mark the task as complete or communicate any issues/delays.
4. Ticket Response:
a. The employee navigates to 'Tickets' in the menu.
b. The employee can view the tickets assigned to them, respond to them, and mark
them as resolved.
5. Chat Participation:
a. The employee opens the 'Live Chat' from the menu.
b. The employee can respond to live chat messages from clients.
6. Logout: The employee logs out of the system once their tasks are complete.

13
SRS Documentation for Damex Digital Client Portal

Client User Flow

1. Registration/Login: The client registers for a new account or logs into the system using
their credentials.
2. Dashboard: The client arrives on the dashboard, which shows a summary of their active
subscriptions, ongoing projects, and recent invoices.
3. Subscription Management:
a. The client selects 'Manage Subscription' from the menu.
b. The client can view their current subscription, change (upgrade/downgrade) their
subscription, or cancel their subscription.
4. Invoice and Payment:
a. The client navigates to 'Invoices' in the menu.
b. The client can view their past invoices, make payments for outstanding invoices,
and view their payment history.
5. Task Tracking:
a. The client selects 'Tasks' from the menu.
b. The client can view the progress of tasks related to their projects.
6. Support Interaction:
a. For live chat, the client opens the live chat interface from the menu or the
dashboard and sends a message.
b. For support tickets, the client goes to 'Ticket Submission' in the menu, creates a
new ticket with the details of their issue or query, and submits it.
7. Logout: The client logs out of the system once they have completed their tasks.

Use Cases
Below is a high-level use case for each key feature, broken down by user role:

Admin Portal

1.1 Orders

Use Case: Process New Orders

Actor: Admin

Description: The admin reviews new orders, confirms the details, and processes the orders
accordingly.

14
SRS Documentation for Damex Digital Client Portal

Use Case: Manage Invoices

Actor: Admin

Description: The admin views, generates, sends, and manages invoices for client orders and
subscriptions.

1.2 Customers

Use Case: Manage Customer Accounts

Actor: Admin

Description: The admin creates, edits, and deactivates client accounts. They oversee client
subscriptions, payments, and access levels.

1.3 Packages

Use Case: Manage Service Packages

Actor: Admin

Description: The admin creates, edits, and deactivates service packages. They set pricing and
define package details.

1.4 Projects

Use Case: Task Assignment and Monitoring

Actor: Admin

Description: The admin assigns tasks to employees, monitors task status, and coordinates
project progress.

15
SRS Documentation for Damex Digital Client Portal

1.5 Resource Management

Use Case: Resource Allocation

Actor: Admin

Description: The admin tracks employee workload, performance, and overall resource allocation
to ensure optimal productivity.

1.6 Tickets

Use Case: Ticket Management

Actor: Admin

Description: The admin oversees the status of support tickets, assigns them to team members,
and ensures timely resolution.

1.7 Live Chat

Use Case: Manage Live Chat Communications

Actor: Admin

Description: The admin monitors and responds to live chat communications, and assigns chats to
appropriate team members.

1.8 Reports

Use Case: Generate Reports

Actor: Admin

Description: The admin generates comprehensive reports on overall agency performance,

individual client performance, or employee productivity.

16
SRS Documentation for Damex Digital Client Portal

1.9 Permissions & Preferences

Use Case: Manage System Permissions and Preferences

Actor: Admin

Description: The admin sets and manages system permissions and preferences to control access
levels and personalize user experiences.

2. Employee Portal

2.1 Tasks

Use Case: Task Management

Actor: Employee

Description: The employee views and manages tasks assigned to them, marking tasks as done
and providing updates as needed.

2.2 Live Chat

Use Case: Client Interaction via Live Chat

Actor: Employee

Description: The employee participates in live chat conversations with clients, answering queries
and providing updates.

2.3 Tickets

Use Case: Resolve Support Tickets

Actor: Employee

Description: The employee responds to and resolves support tickets assigned to them, updating
ticket status upon completion.

17
SRS Documentation for Damex Digital Client Portal

2.4 Reports

Use Case: Report Submission

Actor: Employee

Description: The employee submits reports upon task completion, including a summary of work,
hours logged, and any notable outcomes or challenges.

3. Client Portal

3.1 Account Management

Use Case: Manage Personal Account

Actor: Client

Description: The client manages their account details, including contact information and payment
methods.

3.2 Manage Subscription

Use Case: Subscription Management

Actor: Client

Description: The client views, purchases, upgrades, downgrades, or cancels service packages.

3.3 Invoices

Use Case: Invoice and Payment Management

Actor: Client

Description: The client views past invoices, makes payments, and manages payment methods.

18
SRS Documentation for Damex Digital Client Portal

3.4 Tasks

Use Case: Task Tracking

Actor: Client

Description: The client tracks the progress of tasks related to their projects, seeing what tasks
have been done and which are still pending.

3.5 Live Chat

Use Case: Interaction via Live Chat

Actor: Client

Description: The client uses the live chat feature to ask questions, request updates, and
communicate with the service team.

3.6 Ticket Submission

Use Case: Submit Support Ticket

Actor: Client

Description: If they encounter issues or have queries, the client creates support tickets for
resolution.

3.7 Notifications

Use Case: Receive Notifications

Actor: Client

Description: The client receives alerts related to their account, tasks, invoices, etc., ensuring
they're informed of important updates.

19
SRS Documentation for Damex Digital Client Portal

3.8 Feedback and Ratings

Use Case: Provide Feedback and Ratings

Actor: Client

Description: The client provides feedback or ratings on completed tasks and overall service,
contributing to service improvement and employee performance evaluation.

Please note that these use cases provide an overview, and more specific use cases may be
created based on the detailed requirements of each feature.

Assumptions
1. User Capabilities:
a. All users have basic computer literacy, including the ability to navigate the web
portal, enter information in text fields, and understand common user interface
elements.
b. All users have reliable access to the Internet and a device that meets the minimum
system requirements.
2. Software Development:
a. The development team has the necessary skills and resources to implement all
features and functionality as outlined in the SRS.
b. The development timeline and resource allocation as outlined in the project plan
are accurate and sufficient.
3. Third-party Integration:
a. The project assumes seamless integration with Google Analytics & Search
Console API, payment gateways, and other third-party services mentioned in the
requirements.
b. These third-party services will remain stable and continue to provide the required
functionalities during the development and after the launch of the client portal.
4. Client Data:
a. It is assumed that the clients will provide accurate information when registering for
an account, subscribing to services, and interacting with the portal.
b. All clients consent to the data privacy practices stated in the agency's privacy
policy.
5. Maintenance and Support:

20
SRS Documentation for Damex Digital Client Portal

a. Post-launch, the system will receive timely maintenance and support from the
development team to ensure its smooth operation and to address any technical
issues.
b. Users (admins, employees, clients) will report bugs or issues to the development
team in a timely manner.
6. Security:
a. The system is assumed to be secure from external threats and attacks. Necessary
precautions like encryption, secure sockets layer (SSL), and secure coding
practices will be used to maintain data integrity and privacy.
7. Hardware/Infrastructure:
a. The infrastructure supporting the web portal (servers, network, etc.) is robust and
reliable, with minimal downtime.

Dependencies
1. Third-party Services:
a. The project relies on Google Analytics & Search Console API for analytics and
reporting functionalities. A change in these services or their APIs could affect the
project timeline and functionality.
b. The project is dependent on third-party payment gateways for processing client
payments. Any issues or changes with these services could affect the project.
2. Development Team:
a. The project is dependent on the availability and skills of the development team.
Delays or changes in team composition can impact the project timeline and
quality.
3. User Input:
a. The project requires input and feedback from users (clients, employees, and
admin) during various stages of development for testing and refinement. Delays in
receiving this input can affect the project timeline.
4. Hardware/Software Resources:
a. The project is dependent on the availability and proper functioning of necessary
hardware/software resources, such as servers, databases, and development tools.
5. Internet Connectivity:
a. Reliable internet connectivity is required for the smooth operation of the client
portal. Any internet-related issues can hinder the use of the portal by clients,
admins, and employees.
6. Legal and Regulatory Compliance:

21
SRS Documentation for Damex Digital Client Portal

a. The project is dependent on the necessary permissions and compliance with legal
and regulatory standards, especially regarding data privacy and financial
transactions.
7. Security Dependencies:
a. The project's security depends on various factors, including the secure coding
practices of the development team, the security features of third-party
integrations, and the overall cybersecurity environment. Any security breaches or
threats can affect the project.

User Interface Guidelines

1. Overall Design
● The interface should be clean, professional, and easy to navigate. Ensure that it aligns
with your company's branding and color scheme.
● Typography should be readable and consistent throughout the interface. Use fonts that
are web-friendly and harmonize well with the overall design.
● The layout should be responsive to ensure the portal looks and functions well on different
devices and screen sizes.
● Consistency should be maintained in design elements such as buttons, icons, color
codes, font styles, sizes, and spacings.

2. Homepage
● It should clearly indicate the user type (admin, employee, or client) and present the most
important or frequently accessed information and functionalities.
● Include an easily accessible navigation menu.

3. Login/Registration
● This should be straightforward and secure. For registration, only ask for necessary
information to simplify the process.
● Employ clear error messages and form validation to assist users.

4. Client Portal
● The dashboard should provide a summary view of the client's account, including active
subscriptions, recent invoices, and task status.

22
SRS Documentation for Damex Digital Client Portal

● Navigation to account settings, subscription management, and other features should be

intuitive.
● The invoice page should clearly present all past and present invoices. It should be easy to
make payments or query an invoice.
● The tasks section should provide a clear view of all the tasks, their status, and any
necessary details.
● The live chat and support ticket functions should be easily accessible from all pages.

5. Admin Portal
● The dashboard should provide a high-level overview of key metrics, including new orders,
total clients, outstanding invoices, and task statuses.
● The navigation menu should make it easy to switch between managing orders, clients,
packages, projects, tickets, and other functions.
● Admins should have the ability to customize views and reports to meet their individual
needs.
● Ensure secure and easy management of other users (clients and employees), including
adding, editing, or deactivating accounts.

6. Employee Portal
● The dashboard should highlight the tasks assigned to the employee, with a clear
indication of deadlines and task statuses.
● The interface for managing tasks and support tickets should be easy to use and efficient,
reducing the time spent on administrative tasks.
● Provide a simple and secure method for employees to submit task completion reports.

7. Accessibility
● Ensure the design meets accessibility standards to serve users with different abilities. This
includes color contrast, font size options, keyboard navigation, and alt text for images.

8. Performance
● Design for quick loading times by optimizing images, limiting complex animations, and
keeping the design elements simple and functional.

9. Feedback
● Include user-friendly ways for all user types to provide feedback about the system, report
bugs, or ask for help.

23
SRS Documentation for Damex Digital Client Portal

10. Error Handling

● Design clear and helpful error messages. Guide users to the next step if something goes
wrong.

Data Requirements
1. User Data:
This includes the information needed to manage accounts for the admin, employees, and clients:

a. Admin: Name, Email, Contact number, Password, Role (all admins), and Status
(active/inactive).
b. Employees: Name, Email, Contact number, Password, Role (assigned by admin),
and Status (active/inactive).
c. Clients: Name, Email, Contact number, Password, Company name, Address,
Payment Information, Status (active/inactive).

2. Service Data:
This includes the information about the services provided by your digital marketing agency:

a. Packages: Package ID, Package Name, Description, Price, Duration, Features

included, and Status (available/unavailable).
b. Tasks: Task ID, Associated Package, Description, Status (assigned/in
progress/completed).

3. Order Data:
This includes data related to service orders:

a. Orders: Order ID, Client ID, Package ID, Order Date, Payment Status, Start and End
Date, Status (active/cancelled/completed).
b. Invoices: Invoice ID, Associated Order ID, Client ID, Issue Date, Due Date, Total
Amount, Payment Status.

24
SRS Documentation for Damex Digital Client Portal

4. Support Data:

This includes data related to the support tickets and live chats:

a. Tickets: Ticket ID, Client ID, Issue Description, Submission Date, Resolution Date,
Status (open/in progress/closed).
b. Live Chats: Chat ID, Client ID, Employee ID, Start Time, End Time, Chat Transcript.

5. Project and Resource Management Data:

This includes data related to projects, tasks, and resource allocation:

a. Projects: Project ID, Associated Client ID, Start Date, End Date, Status
(active/completed).
b. Task Assignment: Task ID, Assigned Employee ID, Start Date, End Date, Status
(assigned/in progress/completed).

6. Analytics and Reports Data:

This includes data from Google Analytics and Search Console:

a. Analytics: All necessary data pulled from Google Analytics & Search Console API
to provide insights on website traffic, user behavior, SEO performance, etc.

7. Feedback and Ratings Data:

This includes data related to client feedback and ratings:

a. Feedback: Feedback ID, Client ID, Associated Order ID or Task ID, Feedback Text,
Date.
b. Ratings: Rating ID, Client ID, Associated Order ID or Task ID, Rating Score (out of
5), Date.

All data should be stored securely with privacy considerations. Sensitive data, such as passwords
and payment information, should be encrypted. Compliance with regulations such as GDPR
should be ensured.

25
SRS Documentation for Damex Digital Client Portal

Acceptance Criteria
1. Users can create and manage their accounts, including updating their account information
and deleting their accounts.
2. Instructors can create and manage courses, including uploading course content, updating
course information, and viewing course analytics.
3. Learners can enroll in courses, track their progress through courses, receive feedback on
assessments and assignments, and earn certificates of completion.
4. The platform includes communication and collaboration features, such as discussion
forums, and moderators can remove inappropriate content.
5. The AI chatbot provides users with personalized recommendations and support based on
their interactions with the platform, using natural language processing technologies to
provide accurate and helpful responses.
6. Gamification features include badges, rewards, and leaderboards that incentivize and
motivate learners to complete courses and engage with the platform.
7. The platform is compatible with mobile devices and provides a responsive design that
adjusts to different screen sizes.
8. The platform uses secure data storage and encryption to protect user data, and users are
provided with clear and transparent information about how their data is used and stored.
9. The platform complies with all applicable laws and regulations, including privacy laws and
accessibility guidelines.

By meeting these acceptance criteria, the Damex Academy e-learning app will provide users with
a high-quality learning experience that is engaging, informative, and accessible. The platform will
support a range of learning styles and preferences, including self-paced learning, interactive
learning, and collaborative learning. The app will be secure, reliable, and compliant with all
relevant laws and regulations, ensuring that users can trust the platform and focus on their
learning goals.

Page Structure
Admin Portal:
1. Orders:
a. New Orders: A list of recent orders with details (Order ID, Client ID, Package ID,
Order Date, Status), ability to sort and filter orders, access to each order details.

26
SRS Documentation for Damex Digital Client Portal

b. Invoices: A list of all invoices issued (Invoice ID, Order ID, Issue Date, Due Date,
Total Amount, Payment Status), options to sort and filter invoices, access to each
invoice details.
2. Customers:
a. Create New Customer: A form to enter new customer information (Name, Email,
Contact Number, Company Name, Address, etc.), an option to assign a package,
and a button to save and create the account.
b. All Customers: A list of all customers with basic details, option to search
customers, links to edit or view each customer's account and subscription details.
3. Packages:
a. Create New Packages: A form to create a new package with details like Package
Name, Description, Price, Duration, Features included, and Status.
b. All Packages: A list of all packages with their details, options to edit, deactivate, or
view each package details.
4. Product Catalogue:
a. Products: A list of all products with their details, options to add new products, edit
or view each product.
b. Plans: A list of all plans, options to add new plans, edit or view each plan.
c. Addons: A list of all addons, options to add new addons, edit or view each addon.
d. Charges: A list of all charges, options to add new charges, edit or view each
charge.
e. Coupons: A list of all coupons, options to add new coupons, edit or view each
coupon.
5. Projects: A list of all projects with details (Project ID, Associated Client ID, Start Date, End
Date, Status), options to assign tasks to employees, view task status, sort, and filter
projects.
6. Resource Management: A dashboard to view employee workload, performance metrics,
overall resource allocation.
7. Tickets: A list of all support tickets (Ticket ID, Client ID, Issue Description, Submission
Date, Resolution Date, Status), options to assign tickets to team members, sort, and filter
tickets.
8. Live Chat: A live chat interface to monitor and respond to client communications, assign
chats to team members.
9. Users:
a. Team: A list of all team members with their roles, options to add new members,
edit roles and permissions, deactivate accounts.
b. Permissions & Preferences: A page to set and manage permissions for different
roles, customize platform preferences.

27
SRS Documentation for Damex Digital Client Portal

10. Reports: A page to generate various reports on agency performance, client performance,
or employee productivity.
11. Notification Settings: A settings page to customize the notifications that the platform will
send.

Employee Portal:
1. Tasks: A list of tasks assigned to them, options to mark tasks as done, sort, and filter
tasks.
2. Projects: A list of projects they are involved in, options to view project details, sort, and
filter projects.
3. Live Chat: A live chat interface to communicate with clients.
4. Tickets: A list of support tickets assigned to them, options to mark tickets as resolved,
sort, and filter tickets.
5. Clients: A list of clients they are working with, options to view client account information,
sort, and filter clients.
6. Team: A page to view team members and their roles.
7. Reports: A page to submit reports upon task completion

Client Portal:
1. Account Management: A settings page to manage their account details (Name, Email,
Contact Number, Company Name, Address, Payment Method).
2. Manage Subscription: A page to view their current service package, options to purchase,
upgrade, downgrade, or cancel service packages.
3. Invoices: A list of their past invoices, options to view invoice details, make payments.
4. Payment Method: A page to manage their payment methods.
5. Tasks: A list of tasks related to their account, options to track task progress.
6. Analytics and Reports: A page to access Google Analytics & Search Console reports,
generate custom reports.
7. File Access: A page to download and upload files as necessary, like reports or resources.
8. Live Chat: A live chat interface for immediate support or communications.
9. Ticket Submission: A page to submit support tickets if they encounter issues or have
queries.
10. Notifications: A dashboard to view alerts related to their account, tasks, invoices, etc.
11. Feedback and Ratings: A page to provide feedback or ratings on completed tasks and
overall service.

28