Projects and people,in one place.
Manage projects, people and everyday workplace operations in one system.
A guided walkthrough with our team. Bring your own questions.
Fig. 1 — Four lines meet at one node
People, work and workplace operations, on one foundation.
- Ananya GuptaJoining documents4 of 4 verified
- Mobile app redesignCheckout flow screensEstimate
16 hchanged to 22 h - Priya Nair · Ahmedabad09:41 clocks in
- Ishaan KapoorLaptop IL-LAP-014Return pending
§ 02 — Where it breaks
Work gets lost where people and projects meet.
- 01
A new joiner's details get retyped into three tools.
- 02
A deadline moves, and nobody can say why.
- 03
Someone leaves, and their tasks go quiet.
Fig. 2 — Lines that stop short of the node.
§ 03 — Mon 12 Oct · Priya Nair · Designer · Ahmedabad
One working day, connected.
Priya clocks in
Attendance starts for the day at the Ahmedabad branch.
Recorded Attendance starts for the day
She starts a timer
Time is logged against Checkout flow screens.
Recorded Time is logged against that task
She starts another timer
Design system tokens audit starts. By default, the first timer pauses: one timer runs at a time.
Recorded By default, the first timer pauses
She clocks out
Clocking out pauses the running timer. It does not stop or delete it.
Recorded The running timer pauses, not stops
Plan versus actual
Daniel Mathew, the project lead, opens plan versus actual. Priya's time entries are already there.
Recorded Yesterday's time entries are already there
By default. Your work policy can change this.
See the project delivery solution§ 04 — Mobile app redesign
See what changed and why.
Client added a cash-on-delivery option.
Estimate 22 h, deadline 16 Oct. Reason recorded.
Explore projects§ 05 — The record, from first day to last
From accepted offer to first login, and a clean exit when it is time.

Ananya Gupta · Senior frontend developer, Pune
- 28 SepOffer acceptedAnanya accepts the frontend role.
- 29 SepHR starts joiningKavya Iyer starts joining; offer details carry over.
- 09 OctDocuments collected and verifiedFour of four documents verified.
- 10 OctLogin sentReady for the first day, 12 Oct.
HR starts joining when the offer is accepted. Exit letters wait until clearance and asset return are complete.
See the HR teams solution
Ishaan Kapoor · last day 30 Oct
- 01 OctTasks handed over3 of 4 tasks accepted by Priya Nair.
- 30 OctClearance and asset returnLaptop IL-LAP-014 and ID card pending.
- After clearanceLetters issuedBlocked until clearance and asset return are complete.
HR starts joining when the offer is accepted. Exit letters wait until clearance and asset return are complete.
See the HR teams solution§ 06 — Who it is for
Start with your team, or with the problem.
See projects and people together.
- Projects and people on one record
- Roles that decide who sees what
Joining to leaving, on one record.
- Joining documents collected and verified
- Exit handover, clearance and asset return
Plans, time and changes in one place.
- Estimates and moved deadlines with reasons
- Time entries beside each task
Assets, visitors, vendors and expenses.
- Assets assigned and returned
- Visitor register and vendor records
Roles, scopes and recorded actions.
- Module-by-action permissions
- Audit log records actions
§ 07 — The construction
People, work and workplace operations, on one foundation.
People
- People
- Attendance
- Leave
- Hiring
Work
- Projects
- Tasks
- Time
- Chat
- Files
Workplace operations
- Assets
- Visitors
- Vendors
- Expenses
§ 08 — Magix AI
Ask Magix AI. It's quicker than finding the screen.
Who is out next week?
Answer: Two people are out next week: Priya Nair (19 Oct) and Aarti Shah (21 to 22 Oct).
- 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.
§ 09 — Roles and permissions
Decide who sees and does what.
- 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
- Magix AI is off until your admin turns it on
- The MCP server is off until an admin enables it
Viewing as HR
- People records and joining documentsVisible
- Leave and attendance for everyoneVisible
- HiringVisible
- Project task detailsHidden
Viewing as Manager
- Team leave and attendanceVisible
- Projects and tasks they leadVisible
- Time entries for their teamVisible
- Hiring and joining documentsHidden
- Company-wide rolesHidden
Viewing as Employee
- Own leave, attendance and tasksVisible
- Projects they work onVisible
- Other people's recordsHidden
- Roles and permissionsHidden
§ 10 — Build on it
Connect through a documented API, or an assistant through MCP.
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.
Roles and scopes
// PLACEHOLDER · request sample to be copied from the
// published API reference and checked against the docs.
// No endpoint is shown until then.§ 11 — Your questions
See it with your own team's questions.
A walkthrough of projects, people and workplace operations, shaped around the questions your team brings.