Maintain Vault context
Advanced guidance for people who organize shared sources.
When a source is hard to find or easy to mistake for a current one, improve its description before adding many tags. Say what the document is, whether it is approved or a draft, and the period it covers. For example: "Current investment mandate; sector limits are binding; approved in September 2026."
Use consistent tags for topics your team actually searches. Categories give a broad group; tags identify specifics. You can also exclude a superseded item from agent use while keeping it in your library. Explicitly selecting a document with @ remains the clearest way to use a particular source.
For connected S3 objects, tags from S3 are read-only in Kimpton. Edit them in S3 and wait for the next refresh. Kimpton tags on the same item remain editable. If S3 tags do not appear, ask an admin to check the role's s3:GetObjectTagging permission.
Start with descriptions for binding mandates and stale documents. Add tags only when they help people find the right source. See Using context for the advisor path.