Choose Agent Memory scope
Scope controls where an active memory can be used. Pick the smallest scope that matches the policy. The memory type says what the guidance means; scope says which work can see it.
Global scope
Choose Global when the guidance is true across the company or for every vendor handled by that agent. Examples include a company-wide coding convention or a consistent email-classification rule. Global memories are available to the relevant agent wherever the same situation appears.
Global scope is a poor fit for a correction that only makes sense for one vendor. A vendor name in the sentence does not make a Global memory safe.
Vendor scope
Choose Vendor when the rule belongs to one vendor. The invoice-processing agent then retrieves it only when the invoice context matches that vendor. A vendor memory is useful for a recurring layout, account mapping, or exception that should not affect another supplier.
Vendor scope is available for invoice-processing memories when your company schema exposes the vendor anchor. Email-processing memories are global in this release.
Set or check scope
When you create a memory, choose Vendor from Memory scope and select the vendor. To inspect existing rows:
- Open Agents and choose the relevant agent.
- Open Memories.
- Use the Global or Vendor view, or use the scope filter when it is available in your workspace.
- Read the anchor shown on each row before editing it.
If you edit a memory so that its reach changes, check the new scope against the source evidence. A proposal grounded in one invoice may be a vendor rule even when the proposed wording sounds like a general preference.
ERP-history scope
ERP-history seeding can produce both vendor-specific and cross-vendor candidates when the evidence supports them. The source label Seeded from ERP history does not mean the row is active or universally applicable. Review the proposed anchor and citations in Tasks, then approve only the scope that the evidence supports.
See Approve proposed memories for the review decision and Memory audit log for later verification.
Available anchors, vendor search fields, agent names, and permissions are schema-driven. If Vendor scope is not offered, keep the rule Global only when it is genuinely company-wide; otherwise ask an administrator to review the company schema.