Projects and people, in one place.
The gap
Work gets lost where people and projects meet.
A new joiner's details get retyped into three tools.
A deadline moves, and nobody can say why.
Someone leaves, and their tasks go quiet.
One working day
One working day, connected.
Attendance and task time sit on the same record, so the day explains itself. Choose a row to see its screen.
By default. Your work policy can change this.
See the project delivery solutionAttendance starts for the day at the Ahmedabad branch.
Plans that explain themselves
See what changed and why.
Original and target estimates, a moved deadline and the recorded reason, beside the time entries.
Reason recorded
Client added a cash-on-delivery option. Daniel Mathew, 08 Oct.
Joining to leaving
From accepted offer to first login, and a clean exit when it is time.
HR starts joining when the offer is accepted. Exit letters wait until clearance and asset return are complete.
See the HR teams solutionSample data · Ananya Gupta · Senior frontend developer, Pune
28 Sep
Offer accepted
Ananya accepts the frontend role.
29 Sep
HR starts joining
Kavya Iyer starts joining; offer details carry over.
09 Oct
Documents collected and verified
Four of four documents verified.
10 Oct
Login sent
Ready for the first day, 12 Oct.
Start with your team
Start with your team, or with the problem.
Arrive with your team or your problem, not a module name.
HR teams
Joining to leaving, on one record.
- Joining documents collected and verified
- Exit handover, clearance and asset return
Magix AI
Ask Magix AI. It's quicker than finding the screen.
- Answers come from records you're allowed to see.
- It can also answer general questions from the AI model.
- Powered by third-party AI models. Your admin decides if it's on. It can make mistakes, so check what matters.
Who is out next week?
Two people are out next week: Priya Nair (19 Oct) and Aarti Shah (21 to 22 Oct).
Simulated example · fixed answer from the demo company
Try a sample question
Access
Decide who sees and does what.
Precise controls, and the limits stated next to them.
Admins can
- Create roles, including custom roles
- Set permissions by module and action
- Limit data by scope
- See recorded actions in the audit log
- Sign people out of active sessions
Stated limits
- Magix AI is off until your admin turns it on
- The MCP server is off until an admin enables it
See a role
Visible for manager
- Team leave and attendance
- Projects and tasks they lead
- Time entries for their team
Hidden for manager
- Hiring and joining documents
- Company-wide roles
Illustrative. Real scopes are set per role by your admin; actions are recorded in the audit log.
- REST API v1
- OAuth 2.1 and a public OpenAPI document.
- MCP server
- Acts with the person's permissions; off until an admin enables it.
// PLACEHOLDER · request sample to be copied from the
// published API reference and checked against the docs.
// No endpoint is shown until then.See it with your own team's questions.
A walkthrough of projects, people and workplace operations, shaped around the questions your team brings.