Xmatix
01 · TWO-LAYER ACCESS MODEL
What users can do. What users can see. Separated.
Profiles and field-level permissions govern actions. Record-access policies and ownership govern visibility. Two independent layers — so a permissions change never silently exposes data, and Sense inherits both.
LAYER 1 · CAN DO
Create ordersallowed
Edit price listsdenied
Field: credit limitread-only
LAYER 2 · CAN SEE
Own accountsvisible
Team's territoryvisible
Other regionshidden
National Sales
West BU
Pune team
Mumbai team
South BU
Bengaluru team
+ Partner reps
role hierarchies◆record sharing◆internal vs external
02 · REAL-ORG STRUCTURES
Your org chart, not a permissions puzzle.
Role hierarchies, teams, business units, and record sharing that mirror how the company actually runs — including external audiences like partner reps and distributors, kept firmly outside internal data.
03 · ACCOUNTABILITY
"Why can this user see this record?" Answered.
A full audit trail on every object, a recycle bin with retention, and access diagnostics that trace the exact rule granting visibility — ownership, hierarchy, or share.
04 · OPERATED FOR THE ENTERPRISE
Run like infrastructure, not a shared spreadsheet.
Isolated environments
Sandbox and production are separate worlds — test data never leaks into the real books.
Per-tenant data isolation
Your data lives in your tenant. Multi-tenant efficiency without multi-tenant exposure.
Immutable release promotion
Changes ship as versioned, promoted releases — auditable, repeatable, reversible.