Update to dataroomHQ

{
  "description": "Use when giving someone access to a data room or to particular documents in it, changing or removing access they already have, or explaining what a role or member can currently see. Covers which tools to combine for each kind of grant, and how roles, overrides, hidden folders and links interact.",
  "included_files": [],
  "name": "sharing-a-dataroom",
  "skill_md_contents": "---\nname: sharing-a-dataroom\ndescription: Use when giving someone access to a data room or to particular documents in it, changing or removing access they already have, or explaining what a role or member can currently see. Covers which tools to combine for each kind of grant, and how roles, overrides, hidden folders and links interact.\n---\n\n# Sharing a data room\n\nGrant the narrowest access that satisfies the request. The tools' own\ndescriptions cover each call; this covers how they combine.\n\n## CHOOSING THE GRANT\n\n- Specific files -> a document share; the recipient sees only those files.\n  - One file: `share_document`.\n  - Several files, one link: `create_role(hidden=True)` -> one\n    `set_document_override` per file -> `create_share_link(role_id=...,\n    email=...)`. One link, not several. Leave `keep_watermark` at its\n    default on each override; it matches `share_document`'s.\n- The whole room -> `invite_member` (a participant) or `create_share_link`\n  (an email invite carrying a role).\n- A role with nobody to send it to -> `create_role`, plus an override per\n  file if it should reach only some. Leave `hidden` off: it belongs in the\n  role picker. `hidden=True` is only for the throwaway role behind a\n  document share.\n- Changing what someone has -> `assign_role`, or a new role shaped with\n  `create_role` + overrides.\n\n## BEFORE CREATING ANYTHING\n\n- `list_members` first. If they already have access, say so rather than\n  creating a duplicate; if they are a member, ask before changing their role.\n- If they already hold a document share (`list_document_shares`), add the new\n  file to that share's role with `set_document_override`. It appears on the\n  link they already have.\n\n## HOW THE PIECES INTERACT\n\n- A document share works because `create_role` starts with `doc_view` off\n  and each override then opens one file. Turning `doc_view` on to share a\n  few files hands over the whole room, including documents added later.\n- Claiming several document links MERGES their grants, and a full-access\n  role always beats a hidden one. A smaller link cannot narrow access - to\n  reduce it, change the role.\n- A role grants nothing until a link or a member points at it.\n- To withhold one document from a role that sees everything, set an override\n  with `can_view=False`. Removing an override is a different act: it\n  restores the role's blanket rule for that file.\n\n## REPORTING WHAT SOMEONE CAN SEE\n\nRead it from the role's flags, its overrides (`get_role`) and its hidden\nfolders together. Any one alone gives the wrong answer: an override changes\nthe blanket rule per file, and a hidden folder beats both.\n\n## DON'T\n\n- Don't send a second, smaller link to reduce access.\n- Sharing emails the recipient by default. Say so when reporting back; pass\n  `notify=False` only when asked to share quietly.\n"
}