Skip to content
WorkMagix

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.

Four lines, People, Projects, Time and Workplace operations, meet at one node and become the WorkMagix mark.
  • Ananya GuptaJoining documents4 of 4 verified
  • Mobile app redesignCheckout flow screensEstimate 16 h changed to 22 h
  • Priya Nair · Ahmedabad09:41 clocks in
  • Ishaan KapoorLaptop IL-LAP-014Return pending
Conceptual visualization

§ 02 — Where it breaks

Work gets lost where people and projects meet.

  1. 01

    A new joiner's details get retyped into three tools.

  2. 02

    A deadline moves, and nobody can say why.

  3. 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

By default. Your work policy can change this.

See the project delivery solution
Timer during the break is drawn as illustration only.

§ 04 — Mobile app redesign

See what changed and why.

Client added a cash-on-delivery option.

Daniel Mathew, 08 Oct
Conceptual visualization

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.

An open folder of documents, the top page stamped with a green check

Ananya Gupta · Senior frontend developer, Pune

  1. 28 SepOffer acceptedAnanya accepts the frontend role.
  2. 29 SepHR starts joiningKavya Iyer starts joining; offer details carry over.
  3. 09 OctDocuments collected and verifiedFour of four documents verified.
  4. 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

§ 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

§ 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
Shared foundationOne loginRoles and scopesAudit log
Conceptual visualization Three areas on one foundation.
Explore the platform

§ 08 — Magix AI

Ask Magix AI. It's quicker than finding the screen.

Simulated example

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.
See what Magix AI can do

§ 09 — Roles and permissions

Decide who sees and does what.

  1. Create roles, including custom roles
  2. Set permissions by module and action
  3. Limit data by scope
  4. See recorded actions in the audit log
  5. 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
Review security

Viewing as HR

  • People records and joining documentsVisible
  • Leave and attendance for everyoneVisible
  • HiringVisible
  • Project task detailsHidden
Conceptual visualization Illustrative. Real scopes are set per role by your admin; actions are recorded in the audit log.

§ 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

Request sample
// PLACEHOLDER · request sample to be copied from the
// published API reference and checked against the docs.
// No endpoint is shown until then.

See developer options

§ 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.