{
  "title": "Permission inheritance explanation survey",
  "questions": [
    "Where did this access come from?",
    "Which permission label was unclear?",
    "What change warning was missing?"
  ],
  "question_notes": [
    "Check whether the user can distinguish access assigned directly from access inherited through a fictional group or parent workspace. Keep the explanation of the source, without collecting real group membership.",
    "Ask what action a displayed role appears to permit in the synthetic example. A recognizable role name can still leave the difference between viewing, editing and administration unclear.",
    "Find which consequence the user expects before a role change. Compare that expectation with the approved behavior of the demonstration; a survey response cannot establish the actual authorization state."
  ],
  "answer_guidance": [
    {
      "question": 1,
      "format": "Short open text",
      "reason": "Check whether the user can distinguish access assigned directly from access inherited through a fictional group or parent workspace. Keep the explanation of the source, without collecting real group membership.",
      "optional": true
    },
    {
      "question": 2,
      "format": "Short open text",
      "reason": "Ask what action a displayed role appears to permit in the synthetic example. A recognizable role name can still leave the difference between viewing, editing and administration unclear.",
      "optional": true
    },
    {
      "question": 3,
      "format": "Short open text",
      "reason": "Find which consequence the user expects before a role change. Compare that expectation with the approved behavior of the demonstration; a survey response cannot establish the actual authorization state.",
      "optional": true
    }
  ],
  "respondent_instruction": "If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.",
  "field_protocol": {
    "send_when": "Show product users a synthetic direct-and-inherited permission example before they change any real account access. Include only fictional names and resources.",
    "decision_owner": "The access-management product owner with the permission-model maintainer.",
    "followup": "With the revised source label, ask the user to identify where the fictional access comes from and which approved control could change it. Capture remaining confusion between inherited and directly assigned roles; validate actual behavior separately with access-control tests.",
    "response_handling": "Do not collect access lists, tokens, real member identities or confidential workspace names. Store only the interpretation of the fictional example."
  },
  "editorial_sections": [
    {
      "id": "guide-ownership-map",
      "kind": "ownership-map",
      "heading": "Explain the source of fictional access",
      "intro": "This conceptual map is a synthetic comprehension aid, not a claim about SurveyTeams permission behavior.",
      "rows": [
        [
          "Direct assignment",
          "The fictional user receives the displayed role directly.",
          "The reader identifies a user-level assignment as the source."
        ],
        [
          "Group membership",
          "The fictional resource grants a role through the displayed group.",
          "The reader separates membership from a direct assignment."
        ],
        [
          "Parent inheritance",
          "The fictional child shows a role inherited from its parent.",
          "The reader identifies the parent source; actual editable controls require separate product verification."
        ]
      ]
    }
  ],
  "note": "Examples to adapt. Not a validated instrument; manual editorial data, not a product import payload."
}