{"id":"issuers","type":"module","title":"Issuers (Contracting Authorities)","status":"ga","audience":["bid-manager","consultant","partner"],"scope":"supplier","tier_min":"free","aliases":["5","buyers","counterparties"],"summary":"A supplier's CRM register of the buyer counterparties it cares about. An issuer is a lens over organizations where is_tenant is false, and it is the canonical buyer identity the rest of the platform points at.","keywords":["issuer","crm","buyer","notes","timeline","contacts","organizations"],"body":{"what_it_is":"A lightweight CRM-style register of the **external counterparties** a firm\ncares about: buyers, contracting authorities, customers. Each issuer is a\nprofile record (legal name, display name, ISO-3 country, homepage) that\nbecomes the spine for everything tracked about that organisation: a\nchronological timeline of meeting/call/decision/signal/risk notes,\npoints-of-contact, and every workspace run against that buyer.\nArchitecturally an issuer is **not a bespoke table**: it is a row in the\nunified `public.organizations` table with `is_tenant = false` (the firm's own\norg is `is_tenant = true`). \"Issuer\" is a deliberate lens over\n`organizations WHERE is_tenant = false`. This is the canonical \"buyer\"\nidentity the rest of the platform points at.\n\nAny org member reads any issuer (no per-issuer gating beyond org\nmembership): this is **reference data, NOT an issuer login or account**. Do\nnot confuse it with the Issuer Procurement module, which is the buy-side\ncockpit an issuer org operates for itself.\n","what_it_helps_users_do":"Build a buyer book; keep institutional memory in one place (a timeline that\noutlives any one bid); see the whole relationship at a glance (rolled-up\nworkspaces, people, and a per-stage engagement scoreboard); promote durable\nlessons to the knowledge base; and give the AI agent grounded buyer context.\n"},"engines":[],"integrations":[],"capabilities":[{"id":"issuer-overview-tab","type":"capability","title":"Overview tab","summary":"Identity card, aggregate stats and the engagement rail. Pure CRUD and aggregation, powered by the same single backend read the workspace header uses.","status":"ga","scope":null,"keywords":["identity","engagements","scoreboard"],"body":null},{"id":"issuer-timeline-tab","type":"capability","title":"Timeline tab","summary":"A month-grouped issuer_notes feed with source badges (Manual, Agent, Email, Import). This is the module's AI seat: it receives add_issuer_note agent writes.","status":"ga","scope":null,"keywords":["timeline","notes","provenance"],"body":null},{"id":"issuer-people-tab","type":"capability","title":"People tab","summary":"Loginless contact rows held in members scoped to the issuer organization, managed by hand.","status":"ga","scope":null,"keywords":["contacts","people"],"body":null},{"id":"issuer-workspaces-tab","type":"capability","title":"Linked workspaces tab","summary":"An org-scoped relational join listing every workspace run against this buyer. The bridge to the Workspaces module.","status":"ga","scope":null,"keywords":["join","workspaces","relationship"],"body":null},{"id":"agent-written-issuer-note","type":"capability","title":"Agent-written issuer note","summary":"The first write tool the chat agent was given, behind a per-org feature gate, written with source=agent and attributed to the human chat user. The agent cannot choose the issuer.","status":"ga","scope":null,"keywords":["write-tool","gated","audit-attribution"],"body":null}]}