Assistant Knowledge Guide

Assistant settings keep approved preferences, company knowledge, and glossary terms available to Topline. Use them for durable guidance, not temporary task instructions or secrets.

Access

Open Account > Assistant and choose:

• Preferences for explicit guidance about how Topline should respond or operate;
• Knowledge for reviewed company facts and operating policy; or
• Glossary for approved terms, abbreviations, and definitions.

The active tenant and capability determine which panels and actions appear. Reading preferences requires memory.read, proposing company knowledge requires company_knowledge.propose, and glossary access requires glossary.read; write and review controls may require additional permission.

Add durable guidance

1. Choose the narrowest destination: preference, knowledge, or glossary.
2. Search for an existing entry before creating another.
3. Write one concise, testable statement with enough scope to avoid ambiguity.
4. For company knowledge, submit the proposal and wait for the required review.
5. Confirm the saved or published entry appears in the correct tenant.

Use chat for temporary requests. Use project instructions for project-specific constraints.

States and controls

Entries may be proposed, under review, published, superseded, or removed. Review conflicts instead of silently creating competing rules. When editing an entry, preserve its ownership and intended scope.

Security and tenant boundary

Knowledge is tenant-bound and permission-filtered. Do not store passwords, tokens, private keys, authentication URLs, raw customer rows, unnecessary personal information, or short-lived task data. A Workspace MCP connection never broadens the signed-in user's access.

Workspace MCP

Workspace MCP can read accessible preferences, glossary terms, documentation, conversations, and workspace context. Company-knowledge changes follow the reviewed proposal flow; the client cannot bypass review or tenant authorization. Use the Workspace MCP guide for OAuth scopes, pagination, and troubleshooting.

Errors and recovery

• Panel or entry missing: confirm tenant, capability, resource visibility, and filters.
• Proposal denied: read the reviewer reason, correct the content or scope, and resubmit only when the conflict is resolved.
• Conflicting guidance: identify the authoritative entry and supersede or remove the obsolete one.
• Stale answer: verify the current published entry, then start a new chat or refresh the context after the update.
• MCP access denied: reconnect with the required OAuth scope; never substitute a token from another tenant.

Enablement, smoke check, and rollback

After enabling access, create or update a harmless test entry, confirm it is visible only in the intended tenant, and verify Topline can retrieve it. Roll back by restoring the previous entry or removing the new one through the reviewed UI; audit history remains available to authorized administrators.

Limitations

Published knowledge guides future answers but does not retroactively rewrite previous chats or artifacts. Retrieval is permission-filtered and may be summarized to fit the active task context.