Permissions for coding-assistant search — Non-technical — Bachelor’s https://thesis.uya.no/proposals/an-assistant-that-knows-its-boundaries/?degree=bachelor#nontechnical-track FINAL RESULT A permission matrix and an escalation path for unclear requests. WHAT TO DO Document who should access each kind of coding-assistant document. DATA 12 paper access scenarios (planned) 8 determinate and 4 ambiguous cases covering roles, copied information and cross-project answers. Prepare equivalent prose policies and permission tables. HOW TO TEST IT Use the paper role/document scenarios; record determinate decisions separately from policy ambiguities. Plan 4 participant sessions. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare 12 paper access scenarios and a separate answer sheet or coding sheet. 3. Run one pilot and fix unclear questions. 4. Collect the named evidence with consent. 5. Group the findings with the stated categories and check the answer sheet. 6. Produce a permission matrix and an escalation path for unclear requests. List the three most useful changes. EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. ACCESS OR PEOPLE Recruit software/IT staff; no assistant implementation.