A field only some roles read or change

The customer asks: Only the pharmacist may see a patient's ID number, and only the manager may change a supplier's bank details

• Verdict: Ready, with limits (5)
• Door: Manifest · area: Setup and administration › Roles, lists and data rules
• Recipe: Shipping your own data in a manifest
• Sample: none yet
• Checked: run by the product 2026-10-24 (the role-limited field lane's walk, phone, counter and tablet frames: a Customer field read and written by one role only, found by search and shown on the customer's profile for that role, absent for a cashier without it, and never stored on the till's device); not run by a kit sample

What you build

A field your manifest adds carries write_roles (who change it, and so read it) and read_roles (who read it), from POS version 2.1.0; the installer gives it a permission level of its own. The keys and refusals: the manifest recipe, A field only named roles read or change.

Limits

• Only a field your manifest adds: a field iVendNext already has keeps the retailer's own permissions.
• An update cannot change the roles of a field already installed; a record type has nine levels, so group limited fields into few role sets.
• System Manager reads a field limited by read_roles only if you name it.
• An Item field limited to roles is never shown on a till or a receipt, for anyone.
• A print format, notification, report, card or chart of the same manifest may not name a field only some roles read; a register book's column is not checked for one, and prints it to whoever may print the book.

Tell the customer

The field is changed only by the roles you name; when you limit reading too, a user without those roles does not see it, at the till or in Desk.

What next

1. Tell the customer the 5 limits above, and write them into the proposal.
2. Follow the recipe: Shipping your own data in a manifest.
3. Build and test it on your sandbox (request one if you have none; what is on it).
4. Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
5. Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.

Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.

Related needs

• Each role sees and does only what it should — Ready, with limits (2)
• Extra fields on a purchase order and its lines, a goods receipt, a stock transfer, an expense or the till close — Ready, with limits (1)
• Keep our own records, such as a warranty register, in iVendNext with their own screens and print formats — Ready, with limits (2)
• Change the limits and who is told in one settings page, not in each rule — Ready, with limits (3)

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit