Start with the day, retain the project context
My Day lets people commit work to today, track progress and carry unfinished tasks forward. Those tasks still belong to projects and contribute to the wider delivery picture.
Company workspace
Project overviewAmalAxis Super Portal: Bring delivery context into one workspace.
AmalAxis Super PortalProduct videos
AmalAxis Super Portal brings project delivery, people operations, sales and client collaboration into one team workspace. Daily plans, tasks, milestones and controlled client portals keep work and updates connected, while role-based access gives each person the tools and information they need.
The company workspace challenge
Tasks, requests, project updates and client conversations need a shared context without giving every user the same access.
Who AmalAxis Super Portal connects
Team member
See the relevant work and next action.
Delivery owner
Coordinate project progress and handoffs.
Client collaborator
Access the information shared for their project.
What AmalAxis Super Portal brings together
Plan the work
Organise tasks and milestones around delivery.
Coordinate responsibility
Keep requests and ownership visible.
Share the right context
Provide a focused client-facing project view.
Follow the journey
01
Plan
Define the work and responsible person.
02
Coordinate
Handle requests and related updates.
03
Review
Inspect progress and open decisions.
04
Share
Present the appropriate project context to the client.
Project delivery
Plan
Prepare release notes
Doing
Fix import edge case Internal note: confirm project file
Review
Client review session
Explore the workflow
An internal operations and client-collaboration project for connecting team activity with the work being delivered.
Inside the build
The decisions behind the experience.
AmalAxis Super Portal is the company’s own operational workspace. Project delivery sits alongside daily planning, HR, sales, design, quality assurance and client communication. The challenge was to connect those activities while preserving a focused experience for each role and a controlled view for clients.
The design brief
Connect internal delivery to a deliberately controlled client view.
A shared workspace should connect the team’s work without exposing every internal detail to every audience.
The constraint
Tasks, internal notes and project activity are useful to the team but are not all appropriate for the client workspace. Sharing needs a defined publication boundary.
The tradeoff
Explicit promotion requires a team action, but avoids treating all internal project activity as automatically client-facing. The client experience can stay focused on the information intentionally shared.
Product scope
6
Project lifecycle phases
A shared structure across delivery disciplines
2
Primary workspaces
Internal team and external client
1
Daily planning loop
Commit, work, complete or carry forward
Make client sharing an explicit act
The Client Hub controls what moves into the external workspace. This gives clients a focused view while keeping internal notes and operational material inside the team.
Connect workflows across departments
A bug can become a task with synchronised status. Requests have approval chains, and project lifecycle steps bring several delivery disciplines into one view. The connections are as important as the individual modules.
A workflow in practice
From the trigger to the handoff.
A representative scenario through the implemented workflow.
- 01 · The situation
The team creates project activity while coordinating delivery.
- 02 · The product response
Internal records remain internal by default; selected activity or material is promoted through the client-sharing workflow.
- 03 · The next step
The client sees the published project context without receiving the entire internal workspace.
How it is built
The structure behind the workflow.
Workspace experience
React and Vite provide internal tools and a separate client layout. The responsive web application also supports installation as a PWA.
Connected services
Django manages tasks, projects, people, requests, CRM and supporting workflows. Permissions shape both access and available actions.
Coordination layer
Real-time chat, notifications and an AI assistant connect to the operational workflow. The assistant’s sensitive actions require confirmation.
Actual product screens
The product, up close.
My Day turns assigned work into a focused plan.
Original product interface captures. Screens use demonstration data; visible figures are not measured customer results.
System map
Connected by design.
SYSTEM BLUEPRINT / AmalAxis Super Portal
Select a component to exploreConnected by design.
01 The experiences
02 The shared foundation
03 What it connects
THE COMPLETE PICTURE
Shared project and people context
The client experience has a separate authentication namespace. The Client Hub governs which project information is shared externally.
| The work | Problem addressed | With AmalAxis Super Portal |
|---|---|---|
| Daily focus | Backlogs without a plan for today | A daily commitment and carry-forward loop |
| Delivery visibility | Updates split across departments | Project lifecycle and shared task context |
| Client communication | Email threads and scattered attachments | A controlled portal for project information |
| AI actions | A separate assistant with no workflow context | Permission-aware actions with confirmation for sensitive operations |
Delivered capability
Inside AmalAxis Super Portal.
The portal connects the Amal Axis team’s daily work with project-level oversight and a controlled client experience. It demonstrates how an internal platform can span many functions while keeping responsibilities and sharing boundaries clear.
The external view should be designed deliberately. A client portal is most useful when it presents the information clients need, with the team in control of publication.
Evidence & evaluation
What this case study establishes.
Client-portal gatekeeper code, internal-default project model fields and the workspace product brief.
This is a product engineering case study based on source code, project documentation and recorded screens. It describes implemented capabilities; customer performance gains have not been measured for this case study.
What to measure next
Suggested measures for a deployment evaluation, not reported results.
- Time from approved update to client publication
- Client requests awaiting a team decision
- Unintended-sharing regression results
Discuss the fit
Discuss a team or client-collaboration workflow that needs clearer ownership, access and handoffs.