Keep access intentional.

Start with a project scope

Scopes organize knowledge within a workspace. Access to a parent scope can cover its descendants. A token for one project does not grant access to sibling projects or a broader parent scope.

Copy the actual scope path from Access when configuring a workflow. If you omit the scope when issuing a token, it defaults to the workspace root. Select a narrower scope deliberately.

Separate reading from changing

• Read: retrieve facts, entities, briefs, drafts and campaigns within the permitted scope.
• Write: also ingest notes, link fact sources and approve or reject drafts.
• Admin: a broader permission tier. Routine memory integrations do not need it.

The hosted endpoint derives workspace and agent identity from the bearer token. Passing a different organization in a prompt or request body does not switch workspaces.

Use short lived credentials

A scope administrator issues tokens from Access → Tokens. The default lifetime is seven days; the issuance endpoint caps it at 90 days. Choose a shorter lifetime for temporary work. The raw token is returned once; Willder stores its hash.

Tool execution checks token expiry and revocation. However, the current app has no self service token revocation control or public revocation endpoint. Contact Tri if a token must be disabled before expiry.

Creating a replacement token does not disable the old one. Removing a person’s grant is also separate from revoking an agent token. If a credential is exposed, stop the affected integration and request revocation.

Review decisions in context

Use Audit to inspect access decisions recorded by the permission checks. Look at the actor, action, target scope and outcome when investigating a denied request or an unexpected workflow action.

An access audit does not by itself prove an answer is accurate or capture every step in an external agent’s reasoning. Keep the agent’s task and approval history alongside it.

Understand what changes memory

• Add: uploads and MCP ingestion queue processing. A queued note may not be searchable immediately.
• Correct: use the app’s fact editing controls where available. A correction removes the old fact and queues the revised text; it is not an immediate replacement in search.
• Remove: memory removal is available through authorized app operations. MCP currently has no update or delete tool.
• Track sources: a provenance link records a relationship for staleness checks. It does not automatically refresh the fact when the source changes.

Deleting a fact is not a promise of erasure from uploaded source files, backups or external copies. For a broader data deletion request, contact Tri and review the privacy policy.