Data lifecycle

Files move through upload, validation and processing before becoming ready or failed. Uploading a file does not automatically make it available in every Knowledge store.

Use only files you are authorized to process. Index cleanup and retention may continue after a deletion request; do not assume immediate erasure from backups.

Knowledge connects answers to authorized source documents. RAG retrieves relevant material within the current workspace scope and uses it as context for an answer.

If a source is missing, check its processing state, workspace binding and your role. A citation supports a specific passage, not every statement in the response.

Memory stores selected preferences or context when policy allows it. It can have personal, Group or organization scope and differs from a source-backed Knowledge store.

A missing memory control can reflect workspace policy. Personal context must not be treated as shared team knowledge without an authorized sharing path.

Workspace roles, processing modes and policy govern access and data handling. Generated output must be reviewed before it is trusted or used to change external systems.

Private/Local keeps work within the configured private boundary; Hybrid and External require permitted external processing. Export, retention and deletion follow workspace policy and applicable requirements.