Issuers (Contracting Authorities)
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.
- Catalogue id
- issuers
Description
What it is
A lightweight CRM-style register of the external counterparties a firm
cares about: buyers, contracting authorities, customers. Each issuer is a
profile record (legal name, display name, ISO-3 country, homepage) that
becomes the spine for everything tracked about that organisation: a
chronological timeline of meeting/call/decision/signal/risk notes,
points-of-contact, and every workspace run against that buyer.
Architecturally an issuer is not a bespoke table: it is a row in the
unified public.organizations table with is_tenant = false (the firm's own
org is is_tenant = true). "Issuer" is a deliberate lens over
organizations WHERE is_tenant = false. This is the canonical "buyer"
identity the rest of the platform points at.
Any org member reads any issuer (no per-issuer gating beyond org membership): this is reference data, NOT an issuer login or account. Do not confuse it with the Issuer Procurement module, which is the buy-side cockpit an issuer org operates for itself.
What it helps users do
Build a buyer book; keep institutional memory in one place (a timeline that outlives any one bid); see the whole relationship at a glance (rolled-up workspaces, people, and a per-stage engagement scoreboard); promote durable lessons to the knowledge base; and give the AI agent grounded buyer context.
Capabilities
Overview tab
Generally availableIdentity card, aggregate stats and the engagement rail. Pure CRUD and aggregation, powered by the same single backend read the workspace header uses.
Timeline tab
Generally availableA 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.
People tab
Generally availableLoginless contact rows held in members scoped to the issuer organization, managed by hand.
Linked workspaces tab
Generally availableAn org-scoped relational join listing every workspace run against this buyer. The bridge to the Workspaces module.
Agent-written issuer note
Generally availableThe 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.
Keywords
issuer, crm, buyer, notes, timeline, contacts, organizations
Provenance
This page renders a published artifact. Read the same records as JSON if you would rather check the source than the page.