What Ask is for (ask)¶
Each collection says what its Ask questions may be about, and which sensitive data it opens (section 8.4):
"ask": {
"purpose": "Line 3 packaging: fillers, cappers and the case packer, their alarms, output and quality checks.",
"sensitive": { "pay-hr": "Authenticated/Roles/HR" }
}
purpose— up to 500 characters, the description the scope check judges a question against and the refusal sentence names. Absent = "this Ignition system and its data". Keep it to what the collection covers; it is not a place for instructions.sensitive— opens a category to askers holding the named security level. The categories arepersonal,pay-hr,medicalandcustomer-financial; a category not named is closed, so absent = all closed. A blank level or one this gateway does not have is refused at save, naming the field (ask.sensitive.pay-hr).
Edit both on the context-model page's Form tab (section Ask: the purpose, and one level per category picked
from the gateway's security levels — Closed keeps it closed, and a level can still be typed) or its
JSON tab. A context-model write needs the admin level from a session and is audited
(system.artekis.contextModel.put); when the save changed ask, the audit line says what: saved <revision>; ask
changed: purpose; opened pay-hr (Authenticated/Roles/HR); closed medical; personal <old> -> <new> (the purpose text
itself is not written to the log). Only an Artekis admin changes what Ask answers.