For system administrators
Permission management and master data: decide who sees and changes what
With permission management in ELX, administrators decide what each user can do on every screen and which branches and districts they see. They also set stage time limits and contract guides, backed by an audit log of who changed master data and key operational records, and when.
What permission management covers in ELX
This module is the ELX control centre: it decides who opens each screen, which records they see, how a work order moves between stages, and which approved lists everyone picks from.
One permission matrix, per screen and action
Grant each user show, add, update, delete, change status, show others’ data, relay and import rights on every screen. The side menu lists only the screens they may open.
Data scoped to branches and districts
Link users to their branches, cities and districts, or to every district in selected cities. Their lists and dashboard stay inside that scope; administrators see everything.
Audit log with per-record history
Adds, edits, deletes and status changes on master data and key operational records are logged with user, date and a record snapshot, and administrators can open any record’s full history.
Stage time limits and mandatory data
Set each stage’s allowed days and relay mode (automatic, or manual through a distribution basket), make notes or attachments mandatory, and require a delay justification once the limit is passed.
General configuration and email server
One screen for the VAT rate used in extracts, time-limit counting, sequence-by-contract numbering and issuing materials from the project screen, plus outgoing SMTP settings with a test email.
Contract, item and material guides
Each contract keeps its own items and prices. Within it, materials and drill types link to the implementation items they produce, which are added to the project when materials are issued or drill types chosen, if enabled.
Offices, regions, cities and districts
A linked region, city and district hierarchy; missing records are added from OpenStreetMap after a preview. Each administrative office covers set districts and is tagged on work orders.
Bilingual interface and field help
Arabic right to left, English left to right. Rename screens and interface text per language, and add help, with an optional image or video, to any field.
From setup to daily control
- 1
Build the master data
Define branches, warehouses, contracts and administrative offices, add missing cities and districts from OpenStreetMap, and import implementation items and materials from Excel after reviewing the differences.
- 2
Create users and set their scope
Give each employee a user code and password, link them to their branches and districts, and send them a test Telegram message.
- 3
Grant permissions
Review the user’s current rights, then tick actions per screen or for all screens at once. Their side menu is rebuilt on save.
- 4
Set the stage rules
Choose each stage’s time limit, relay mode and what relay requires: notes, attachments or a delay justification.
- 5
Review the audit log
When questions arise, open the record’s full history: who changed what, and when.
Why electrical contractors need clear access governance
In shared spreadsheets everyone sees everything, nobody can tell who changed a price or removed a record, and branch and contract data blur together. In ELX every user works within clear limits, and changes to master data and key operational records leave a trace.
- Only the assigned user — or someone holding “show others’ data” — can open a work order.
- Relay and import are rights of their own, separate from editing.
- Manual stage changes require a note and are logged separately.
- Deleting stock documents, work orders and estimates is a soft delete that stays traceable.
What administrators configure, and why it matters
| Setting | What it holds | Why it matters |
|---|---|---|
| Company profile and printouts | Name, commercial registration, VAT number, logo, print header and footer | The header and footer appear on achievement certificates, material balance reports and stock vouchers |
| VAT rate | The rate set in general configuration | Used to calculate VAT and the invoice total on each extract |
| Time-limit counting | From relay or from receipt | Sets when each stage’s day count starts |
| Outgoing email server | SMTP settings with a test email | Sends permit, matching and disconnection forms and password-reset codes |
| User accounts | User code, password, branches, districts, Telegram number | Alerts go to the right people and data stays in each user’s scope |
| Screen catalogue | Screen and permission names per language, menu order | Screens carry your team’s own terms, and the order can be exported to another environment |
Permissions and settings FAQ
Can I give an employee view-only access to one screen?
Yes. ELX grants permissions per user at screen and action level, so you can enable “show” on its own without add, update or delete. A user who opens a screen they have no right to is sent to an unauthorized page, and the mobile-ready API for field apps uses the same permissions to decide which screens a user gets.
Does ELX record who changed or deleted data?
Yes. ELX logs adds, edits, deletes and status changes on master data and key operational records such as work orders, projects and order distribution, with user, date and a record snapshot. Manual stage changes are logged separately with their note, and deleting work orders, stock documents or estimates is a traceable soft delete. See our guide to user permissions and audit trails.
Can each branch team see only its own work orders?
Yes. Once a user is linked to their branches, cities and districts, their lists and dashboard stay within that scope, while administrators see everything. Only the assigned user — or someone with “show others’ data” — can open a work order, so ownership stays clear at every stage.
Can we import contract items and prices from Excel?
Yes. In the implementation items and materials guides you upload an Excel file; ELX compares each row with existing data, marks it new, update or skip, and shows errors and warnings before anything is applied. Each contract keeps its own item list and prices, and imports require the Import permission. When you first move to ELX, Matrix can also migrate your existing guides and data from Excel.
Can administrators set a time limit for each work order stage?
Yes. Each stage gets an allowed number of days, counted from relay or from receipt. You can make notes or attachments mandatory and require a delay justification, with text and files, before an overdue order is relayed. Overdue orders are flagged in the stage lists. Learn more in our work order SLA guide.
Can we rename screens to match our own terminology?
Yes. In the screen catalogue, administrators rename any screen or permission in Arabic and English and reorder each section’s screens by drag and drop. Interface words and system messages are edited per language in one grid, and any field can carry help text with an optional image or video. If you need more than new names, Matrix customises screens, reports and stages to your company’s needs.
Articles about Permissions, settings & master data
Saudi PDPL for Contractors: What Systems Must Handle
Saudi PDPL for contractors: subscriber and technician data in work orders, data subject rights, 72-hour breach reporting and questions for your vendor.
Read articleNCA Essential Cybersecurity Controls for Contractors
What the NCA Essential Cybersecurity Controls (ECC-2:2024) require, who must comply, how third-party clauses reach contractors, and what to ask vendors.
Read articleUser Permissions and Audit Trail in Contractor Systems
Set user permissions and audit trail rules for a contractor system: rights per screen and action, branch and district scope, and proof of who changed what.
Read articleWhat Is a Contractor Extract (Mustakhlas)?
What a contractor extract is, interim vs final extracts, and how to group completed work orders, deduct fines and add 15% VAT for a correct invoice total.
Read articleWhat Is a Material Estimate (Muqaysa) in Utility Work?
What a material estimate (muqaysa) is in utility projects, how to build one per work order or import it from Excel, and how to use it to catch gaps early.
Read articleWork Order SLA: Time Limits and Delay Justifications
Learn what a work order SLA (tazmeen) is, how to set day limits per stage, when to require delay justifications, and how to catch overdue orders early.
Read articleDigital Transformation for Electrical Contractors
Digital transformation for electrical contractors in Saudi Arabia, step by step: move from spreadsheets to one system for work orders, stock and extracts.
Read article
Want to see ELX on your own projects?
Request a demo from our team on WhatsApp and see how work orders, extracts and warehouses run in one system.