Skip to main content

Security

Who should see cost and salary? Field-level security explained

Most leaks are not hacks. They are a cashier exporting a list that happened to include the cost column.

Invoice form with the cost column masked for a cashier role

· 5 min read · By Proaqsa ERP

Rows and fields

Row-level security decides which records a person can see (their company, their branch). Field-level security decides which columns of those records they can see (cost, margin, salary, phone). Both must be enforced on the server, not by hiding a column in the browser.

Hiding a column in the interface is cosmetic: the data still travels to the browser, still lands in exports and still appears in the print view. Real field-level security removes the value before it leaves the server, everywhere the field could appear.

Where fields leak

  • List views and search results
  • Edit forms and read-only views
  • CSV and spreadsheet exports
  • Printed documents and PDF statements
  • Reports and dashboards
  • API responses and mobile screens

A rule that applies to four of the six is not a rule.

How Proaqsa ERP applies it

Field rules are attached to roles and evaluated on the server for every surface — lists, forms, prints, ledgers and stock reports, including their CSV downloads. A cashier sees price, never cost or margin; an HR user sees attendance, never salary unless granted. Row rules scope by company and location. See security and the platform module.

Security

Scoped by default, enforced on the server.

FAQ

Frequently asked questions

Can I hide the cost price from sales staff?

Yes. Cost and margin are field-controlled; roles without the grant never receive the values.

Does it apply to exports?

Yes. Exports, prints, reports and mobile screens are shaped by the same server-side rules.