Changing what a role can do

There are six Torqix roles and there will be six: owner, manager, service advisor, technician, accountant, front desk. Your shop can give any one but Owner a name of its own above the permission matrix; the built-in name stays beside it, and clearing the box returns it. The name changes no access. The table of who-can-do-what is a form you edit for your shop, one key at a time.

Open Team and follow What each role can do. You need the team key. The page says what it is: Every key in the product, said in plain words, and yours to change. This table is generated from the rules the server enforces — it is not a description of them, so a box you tick here is the same answer the server gives on the next page load.

Moving a key

Rows are things a person does, grouped the way the day is — running the business, looking after people, customers and cars, selling and working the job, money in, books and pay, the record. Columns are the six roles. Tick a box to give that role the key here, untick to take it away, then press Save the matrix.

It reaches everybody holding that role on their next page load — not their next sign-in, and including whoever you hire next year. A cell you have moved shows the caption changed here underneath it, so a screen full of ticks still tells you at a glance which ones are yours.

Only your disagreements are stored. Putting a cell back the way it started does not record a decision, it removes one — the row is deleted and that role goes back to the standard answer. That is why the header can say Standard everywhere or 3 changed for this shop rather than counting every box on the page.

A save is all or nothing. One cell you are not allowed to move refuses the whole save, and nothing changes until you fix it. Saving a table you have not actually altered says The permission matrix is already set that way.

The six keys that never move

They are listed on the page under The keys no shop can move, and why, each with its reason, and they render as plain Yes and No rather than as boxes. The database refuses them as well as the screen, so there is no route round it.

Run the account

The plan, the bill and cancelling are between the shop and Torqix, and they stay with the owner.

Add people and set their access

It is the key that edits this very table and the one that switches a locked-out teammate back on. A shop that could take it from everybody would have no way back in.

Run payroll

Who may appoint an owner is worked out from this key, so handing it to another role would let that role appoint owners.

Read the audit trail

It reads the record of changes made on this screen. Who may read that is not a setting this screen gets to hold.

Work any repair order

A technician is kept away from rates, prices, totals and invoices by only ever loading their own tickets — a fence in the query, not a checkbox. Granting this would open every ticket in the shop to them.

Work their assigned repair orders

The narrowed half of the key above, decided per ticket rather than per role. It is fixed alongside it.

The whole owner column is fixed too, and the page argues it rather than asserting it: an owner holds every key in the shop for the same reason they see every figure in it, and a shop that could lock its own owner out would have nobody left to unlock it.

When it says no

• Trying to move a fixed key names it and gives the reason — “Run the account” is not a key a shop can move. and then why.
• Editing your own role is refused: You are a Manager, so changing what a Manager can do changes your own access and everybody else's with your role. Ask an owner to make this one.
• Handing out something you do not hold is refused: You cannot give a Service Advisor “Export the books” while your own role does not carry it. An owner can.
• Without the team key you do not get the screen at all: Changing what a role can do needs the team key, and your role does not carry it.

Every save writes one line to the permission trail at the bottom of Team and to the audit trail, naming the cells you moved — something like changed what roles can do at this shop: Service Advisor · give money back → on; Technician · book the calendar → back to the role default (off). It is written against the shop rather than against a person, because that is what a matrix change is: the rules changed, not one person's access.

If you run more than one location, the trail on Team shows the changes made at the shop you are signed in to, plus the few that belong to the whole account rather than to any one location — an API key, an account-level setting. A change made at another location is on that location's own Team screen, and the audit trail follows the same rule. Nobody reads another shop's permission history from here.

Checking it person by person

The matrix answers "what can a manager do". The other link on Team — Who can see costs? — answers "what can this person do, and why", one column per human being, with the provenance under each answer: role, set for shop, set for them, money switch. Those send you to three different screens to change, which is exactly why it distinguishes them.