Skip to main content

Features

Everything Matrix does, and nothing it does not

Nine areas of one product, sharing one user directory, one permission catalogue and one database. Each page below sets out what the capability does, the problem it solves and how teams put it to work.
Illustration of My Dashboard: the KPI strip and widgets are the product's own, and each one is hidden automatically if the viewer's role does not grant the matching permission. Placeholder values.

Browse by area

The names here are the product's own — the same words you will see in the sidebar once you are inside.

Project management: boards, backlogs, epics and sprints

Plan work in the backlog, run it on a board your team configures, and group it under epics and sprints. Every issue keeps its own key, type, priority, assignee and history.

Read the detail

Daily Status Reports: hours against a project and an issue

A DSR is one day of work, recorded against the project and the issue it belongs to. That single habit is what makes every hours report in Matrix trustworthy.

Read the detail

Attendance and leave, in the same place as the work

Attendance comes out of your attendance machine and into Matrix as a file, not as retyping. Leave runs from application to approval with everyone kept informed by email.

Read the detail

Reports across delivery, hours, attendance and leave

Sixteen reports that read the data your team already enters. No export step, no separate warehouse, no reconciling two systems that disagree.

Read the detail

CRM: organisations, contacts, leads and deals

The commercial side of the business, in the system that already knows your projects and your people. No second login, no separate user directory, no copying a won deal into a project tool by hand.

Read the detail

Hiring, the employee directory and the org chart

From the applicant with a CV attached to the employee with a reporting line, a document set and a leave balance — one record, followed all the way through.

Read the detail

Hardware assets, allocated to the people who have them

Every laptop, monitor and dock, with a status you can count and an owner you can name — in the same directory as the employees they are issued to.

Read the detail

Portfolio and enterprise views above the project

One project is a board. Four related projects are a portfolio. Everything the company has running is the enterprise view — the same work, at three altitudes.

Read the detail

Roles and permissions from one catalogue

Matrix has one list of named permissions. It decides what appears in the sidebar, which routes resolve, and what the API will answer — so access is a single decision, not three that have to agree.

Read the detail

Gini Assistant: ask your workspace, inside your permissions

Some questions are faster asked than navigated to. Gini Assistant answers them inside the session you are already in — within the same permissions, the same company boundary and an audit record for anything it changes.

Read the detail

Where next

Reading paths

Three ways through the same material, depending on why you are here.

Evaluating for a services business

Start with the IT services solution page, then reports and pricing.

Comparing against what you have

Read Matrix vs Jira or Matrix vs spreadsheets to see what changes when everything shares one workspace.

Doing the security review

Go straight to security and roles and permissions, then send us your questionnaire.

See it with your own projects in it

Create a workspace, add one project and run a sprint through it. That is the fastest way to find out whether the shape fits your team.