Knowledge

What belongs in knowledge

Use knowledge for context that should remain useful after the current conversation ends. Common examples include product specifications, positioning, pricing, customer history, brand guidance, sales playbooks, and operating procedures.

Your AI can create or update knowledge while it works. You can also review and edit it in the Hub. Knowledge is stored as readable content, with version history, so you can see what changed and return to an earlier version.

Your copy and the shared copy

Knowledge is your organization's shared memory, so a new document is offered to the organization as it is written. On an organization that has not turned review on, it is available to everyone straight away. This is the default on purpose: a document kept private helps no teammate and no later task.

Two things are held back automatically. A document marked Personal only never leaves you. So does one that still reads as personal rather than written for the role, until it is rewritten.

You can also turn off automatic sharing for yourself in your personal settings, which is the right setting if you are working inside a client's organization. Your documents then stay on your own line until you choose to share one.

An organization can require review instead, in its settings. Sharing then puts the document in a queue and an administrator decides whether it reaches everyone. Turning that on changes who approves a document, never who offers it.

Once a document is shared, your later edits start in your copy again and apply only to your work. Everyone else keeps the shared version until your change is accepted.

Who can see knowledge

Knowledge can remain personal, be shared with selected collections, or be available across the organization.

Collections control visibility. They do not own the document, control publishing, or create their own version. Everyone who can access the document receives the same published version, unless they have their own changes.

A document always remains owned by its creator. Which version is published is a separate question, and the answer follows the audience: the organization decides while a document is shared across the organization or waiting in review, and the creator decides the rest of the time, including after a document stops being shared organization wide.

A document marked Personal only cannot be shared through a collection or with the organization until that setting is removed.

Where knowledge applies

Your AI can find knowledge when a task needs it. Knowledge can also be attached to a connector or a related group of capabilities so it is included whenever work in that area calls for it.

An attachment controls when knowledge is used. It does not change who can see the document. Visibility is still determined by its sharing settings and collections.