Datastore permissions decide who may read or write a datastore. Field Security goes a level deeper, deciding who may read or write an individual field.
It is what you reach for when most of a record is fine for everyone with access, but a few columns are not — a salary on an employee record, a clinical note on a case, a margin on a quotation, bank details on a supplier.
Where to find it
Go to Datastores, open the datastore you want to secure, and click Field Security in the row of buttons above the field list — alongside Workflow Rules, Table Actions, Permissions and the rest. It is per-datastore by design.
The three access levels
- No Access — the field is hidden and cannot be written.
- Read-only — visible, but cannot be changed.
- Write — normal access, still governed by the datastore's own permissions.
It applies everywhere
Field Security is enforced centrally rather than by individual screens, so a restricted field is restricted wherever it would otherwise appear — forms, browse views, custom queries, exports and document templates.
Worked Examples
- HR system: salary visible to HR and the employee's own manager, hidden from everyone else.
- Sales: cost price and margin write-access for finance, read-only for sales managers, hidden from sales staff.
- Healthcare: clinical notes restricted to clinicians while administrative staff still manage the appointment.
- Supplier records: bank details visible only to accounts payable.