xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs
OVERVIEW · Last reviewed

xMatix Knowledge Center

The Knowledge Center is the documentation for the xMatix platform. It explains how to use each module, how to set up and run xMatix for your organization, how to tailor it, and how to build on it. Start from your role if you are new, or go straight to the module you work in. Each module manual explains the everyday tasks first, then the configuration behind them, then what to do when something goes wrong.

Overview

The documentation has seven groups, in the same order as the sidebar on this page:

GroupWho it is forWhat you find there
Getting StartedEveryone, on day oneSigning in, finding your way around, the mobile app, getting help, and a learning path for each job role
AdministrationThe people who run xMatix for an organizationUsers and access, security profiles, licensing, numbering, templates, data import and export
PlatformAdministrators and implementersThe ideas the whole platform shares, customization tools and integrations
ProductsUsers and administrators of each moduleOne manual per module, from CRM to Payroll
Analytics & AIReport authors, analysts and Sense usersReports, dashboards, Data Studio and xMatix Sense
DeveloperDevelopers and integratorsThe CLI, the data API, the MCP endpoint and connector authoring
Help & ReferenceEveryoneField-by-field entity reference, troubleshooting, FAQ and release notes

When to use it

  • You need to do a task. Open the module manual and find the page labelled HOW-TO. It has numbered steps, the exact menu path and button names, and what you should see after each step.
  • You need to understand something. Pages labelled CONCEPT or OVERVIEW explain how a feature works and how it connects to the rest of the process.
  • You need to know what a field means. The entity reference lists every field of every business entity. Most module pages also have a Fields table for the form they describe.
  • Something is not working. Start with Troubleshooting. Most module pages also end with Common problems: the symptom, its cause and the fix.
  • You are setting xMatix up. Read the Configuration and Permissions sections of a module page, then the administration guide.

How each page is built

Under the title of every page you see a label and a date:

  • The label tells you what kind of page it is: OVERVIEW, CONCEPT, HOW-TO, REFERENCE, TROUBLESHOOTING or FAQ.
  • Last reviewed is the date the page was last checked against the product. It is updated every time the page is revised, and it is the best guide to how current the page is.

Module pages follow one structure, so you always know where to look. Sections that do not apply to a topic are left out:

SectionWhat it gives you
Overview, When to use it, How xMatix handles itWhat the feature is, where it fits and what the platform does for you
PrerequisitesWhat must already be set up or recorded
ProcedureNumbered steps for each task
FieldsWhat each field on the form means, its allowed values and defaults
Business rulesValidations, automatic calculations, numbering and status changes
ExampleA worked example with invented data
TrainingA practice exercise and a quick reference
PermissionsWhat access each task needs, and what you see without it
ConfigurationThe settings and setup screens an administrator uses
Common problems and Common questionsSymptoms with fixes, and short answers to frequent questions

Prerequisites

You do not need an account to read the Knowledge Center. To follow a procedure in the product, you need:

Procedure

Step 1 — Search for a page

Type at least two characters into the Search docs… box at the top of the sidebar. Results appear as you type: up to eight pages whose title, description or headings contain every word you typed, each with its section. Select a result to open it. If you see No pages match., use fewer or shorter words. Search finds the words of a page's title, description and headings, not its whole text. Press Escape to close the results.

Step 2 — Browse by section

On this page, the sidebar lists every section in its group. On any other page, it lists the pages of the section you are in. The breadcrumb above the title (Home / Docs / section) takes you back to the section's index page or to this page.

Step 3 — Follow a learning path

Open Role guides and choose your job. Each role guide describes one job, then lists the pages that job needs in the order worth reading them. It points to the full procedures rather than repeating them.

Step 4 — Look up a field or term

For a field on a form, open the entity reference and find the entity (the kind of record, such as Order or Invoice). For a business term, see the glossary.

Getting started

New to xMatix? Start here.

Administration

  • Administration guide — users and access, record security, licensing, templates and numbering, data import and export, and sandboxes, each linked to the Setup screen where you do the task.

Platform

Product manuals

ManualWhat it covers
CRMAccounts, leads, opportunities, quotes, product configuration, demos, appointments and activities
SalesOrders, stock allocation and picking, invoicing, payments, pricing, credit limits, trade schemes and claims
Field SalesBeats, visit plans, in-outlet work on mobile, van sales, territory planning, prospecting and attendance
RewardsIncentive plans for people and partners, KPI configurations and compensation records
InventoryThe movement ledger, transfers, adjustments, lots, valuation and period balances
ProcurementRequisitions, purchase orders, goods receipts, supplier bills, auto-ordering and variance review
WarehousePicking, delivery orders and dispatch, cycle counting and storage locations
ServiceService orders, estimates and invoicing, labour time sheets, checklists, recommendations, campaigns and service contracts
Field ServiceThe dispatch console, skills and capacity routing, resource availability, automatic assignment and the technician's mobile day
SupportCases, SLA policies, queues and routing, knowledge, macros and collaboration
Telephony & MessagingCalls and messaging: who uses each feature and the order to set them up
Finance & AccountingThe ledger under every document, journals, banking, period close and statements
Tax CenterIndia GST returns, e-invoicing and e-way-bill preparation, and TDS/TCS compliance
PayrollEmployees, salary structures and the payroll run from calculation to payment
Expense ManagementExpense claims, their approval and how they post to the books
CommerceCatalogues, dealer ordering, per-account pricing, schemes, credit control, direct-to-consumer selling and the screens and records reference
PortalsCustomer- and partner-facing sites built on your organization's data
Mobile AppNavigation, working offline, capturing data in the field, approvals, and what administrators configure

Analytics & AI

  • Analytics & Reporting — the report library, dashboards, scheduled email delivery, sharing and print formats.
  • Data Studio — governed data models, analysis-ready datasets, row-level security, archival and embedded BI.
  • xMatix Sense — the permission-scoped assistant, nudges, shelf photo analysis, AI Studio and the Setup Copilot.

Developer

  • Developer documentation — the xMatix CLI, the data API, the MCP endpoint, connector authoring and the script runtime.

Help & reference

  • Entity reference — every business entity's fields, actions, validations and relationships.
  • Troubleshooting — the first checks to make, and the route to every module's troubleshooting page.
  • Frequently asked questions — the questions evaluators and new customers ask most.
  • Release notes — where the monthly summaries of what changed are published.
  • Glossary — short definitions of the business terms used across xMatix.

Training

The Knowledge Center doubles as training material. If you are teaching xMatix:

  • Build the course from a role guide. Its reading order is a ready-made syllabus.
  • Many module pages end with a Training section. Practice exercise is a task the trainee does in a sandbox, with the result they should see. Quick reference is a short list of reminders to hand out.
  • Each Example section is a complete walkthrough with invented data. You can demonstrate it live before trainees try the exercise.
  • Practise in a sandbox, not in your live data. Where sandboxes are enabled for your organization, an administrator can create one. See Sandboxes and promoting changes.

Practice exercise

Type personalizing into Search docs… and open the page about lists and views. Note its label and Last reviewed date. Then use the sidebar on this page to open the Sales manual, and the breadcrumb to come back here.

Expected result: you reached Personalizing lists and views through search. You can read its label and review date under the title. The breadcrumb's Docs link brings you back to this page.

Quick reference

  • Search docs… matches titles, descriptions and headings. Every word you type must match.
  • HOW-TO pages have numbered steps. CONCEPT pages explain how something works.
  • Last reviewed under the title tells you how current a page is.
  • Field meanings are in the entity reference, and terms are in the glossary.
  • Something wrong? Look at Common problems on the module page, then Troubleshooting.
  • Missing an app or a button? Ask your administrator. Access is set per organization.

Permissions

Anyone can read the Knowledge Center without signing in. What you can do in the product is different: it depends on the security profiles your administrator gives you. Many module pages have a Permissions section that names the access each task needs. If a procedure mentions an app, a button or a field you cannot see, your access is the usual reason. See How the xMatix security model works and Troubleshooting access and sign-in.

Configuration

The documentation describes xMatix as it is delivered: the standard apps, forms, fields, actions and security profiles. Your organization can change much of this. Administrators can add or rename fields, redesign forms, add business rules and automation, and change what each profile allows, so your screens may differ from a page. Where a behaviour depends on a setting, the page names the setting and where to change it, not one organization's value. To see what can be tailored and with which tool, read Customization and The customization ladder.

Common questions

Where should I start if I'm brand new?

Start with Getting started with xMatix. It takes you from signing in to working comfortably in the product. Then open the role guide that matches your job. It lists the pages worth reading in order. If you administer xMatix for your organization, continue into the administration guide and the platform concepts, which explain the security and customization model behind every setting.

How is this documentation organized?

By audience first, then by product. Getting started and the role guides are for everyday users. The administration, platform and customization sections are for the people who configure xMatix. Each product has its own manual with procedures, field tables, configuration and troubleshooting, and the developer section covers the programmable surface. Every page shows its type and the date it was last reviewed under its title.

Why does my screen look different from the page?

The pages describe the standard configuration that xMatix is delivered with. Your organization may have added fields, redesigned forms, renamed items or changed what your security profile allows. A button or field you cannot see usually means your access does not include it, or your administrator has removed it from the form. Ask your administrator. They can check your security profile and the form design.

How current is a page?

Look at Last reviewed under the title. It is the date the page was last checked against the product, and it changes whenever the page is revised. The release notes section explains where summaries of product changes are published. When a page and the product disagree, the product is right. Report the difference through the channels in Where to get help.

Search did not find what I need. What else can I try?

Search matches the words of page titles, descriptions and headings, and every word you type must appear. Try one or two shorter words, such as the name of the record ("invoice") rather than a full sentence. You can also browse the module manual in the sidebar, look the record up in the entity reference, or ask Sense AI chat if your organization has it.