Free skill · October 14, 2026

Deal Collaborator and Shared Access Map

Keep participation in a deal separate from user or team access grants.

Keep participation in a deal separate from user or team access grants. Preparation only, not an account action.

Download the free skill

One complete Markdown file. No subscription or fabricated setup files.

Download SKILL.md

What to provide

Deal ID, Collaborators card, Shared users/teams fields, access policy and permission evidence.

How it works

  1. Record collaborators and shared-access fields as separate lists.
  2. Use HubSpot definition that collaborators are updated through the Collaborators card.
  3. Do not infer permission from collaboration or collaboration from shared access.
  4. Return role and permission gaps without adding people or changing access.

The output

deal | collaborator | shared_user | shared_team | permission_evidence | participation_evidence | hold

Worked fictional example

Fictional U 1 is a collaborator but shared-user evidence is absent; teamT 2 is shared but collaborator list lacks its members. Neither list proves the other role. Actual access remains unverified without permissions evidence.

Checks and limits

Keep source versions and original values. Unknowns stay unknown. Use qualified review for regulated, legal or hiring decisions. No live account compatibility test, send, share, schedule, ledger change or payment is authorized.

More sales workflows · How-to guides

Method: reviewed source. Demand lead: Oct14 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia107, cashflowforecasting13. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured. Checked October 14, 2026.