Permissions for coding-assistant search — Non-technical https://thesis.uya.no/proposals/an-assistant-that-knows-its-boundaries/#nontechnical-track BACHELOR Final result: A permission matrix and an escalation path for unclear requests. Task: 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. Requires: Recruit software/IT staff; no assistant implementation. Method: 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. MASTER Final result: Policy clarification table and source-display recommendations. Research question: Explain mismatches between permission policy and users’ expectations of assistant access. Contrast prose and permission-table cases using contextual integrity; separate ambiguous policy from incorrect interpretation. Research result: A theory-based account of access expectations and unresolved governance decisions. STEPS Study, compare and explain 1. Read the newest papers and write one exact research question. 2. State which people, cases or documents you will study and what you will compare. 3. Write the selection rules, questions and analysis steps for 12 paper access scenarios + 8 IT interviews. 4. Run one pilot. Fix unclear questions or categories, then keep the guide unchanged. 5. Collect the named interviews, cases or documents with consent. 6. Analyse them with the stated comparison or coding method. Keep disagreements and missing data. 7. Report the answer, the evidence and the practical output named in the assignment. CURRENT PROJECT LITERATURE Retrieval-Augmented Generation Classification and Access Control (2024, technical publication): https://www.tdcommons.org/dpubs_series/7382/ Describes current permission, classification and monitoring controls for RAG data. Integrating Access Control with Retrieval-Augmented Generation (2025, peer-reviewed): https://doi.org/10.1145/3672608.3707848 Implements and evaluates fine-grained access control for sensitive RAG content. IS THEORY STARTING POINTS Nissenbaum (2004) — Privacy as Contextual Integrity: https://digitalcommons.law.uw.edu/wlr/vol79/iss1/10/ Analyse recipient, purpose and information flow rather than treating privacy as a role label. Orlikowski & Gash (1994) — Technological Frames: https://dl.acm.org/doi/10.1145/196734.196745 Compare how roles interpret the purpose, operation and use of the same system. Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points. PILOT QUESTION Which access-policy rules do users misunderstand when answers combine multiple sources? EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. FIRST THREE ACTIONS 1. Prepare a pilot with 2 examples from: 12 access scenarios + 8 interviews. Write the task questions and a reference answer sheet. 2. Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact. 3. Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample. INTERVIEW QUESTIONS - Which sources may this role read under the policy? - Does combining two permitted facts change your decision? - Which wording in the policy or answer is unclear? LITERATURE SEARCH AI assistant access control information disclosure user understanding qualitative scenario study DATA 12 paper access scenarios + 8 IT interviews (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 Compare policy comprehension for clear cases with balanced, non-overlapping versions. Score clear cases against the policy key. Analyse ambiguous ownership cases and escalation reasons separately. FINAL RESULT Policy clarification table and source-display recommendations. ACCESS OR PEOPLE Recruit software/IT staff; no assistant implementation. TEMPLATES https://thesis.uya.no/starters/an-assistant-that-knows-its-boundaries/nontechnical/study-plan.csv https://thesis.uya.no/starters/an-assistant-that-knows-its-boundaries/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/an-assistant-that-knows-its-boundaries/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.