Workspace data controls

A conversation, a project, and a saved memory serve different purposes. Decide where information belongs before bringing it into your work. Project instructions and attached files give related conversations a shared foundation; memory supports continuity across your work.

• Keep task-specific background with the relevant conversation or project.
• Review project instructions and reference files when the purpose of a project changes.
• Use the project-only memory setting when you want retrieved memory context scoped to that project.

Memory settings let you review and manage saved memories and whether memory is enabled. Personal instructions are another source of context: keep them aligned with the way you want Relam to respond.

Review saved context when your role, preferences, or ongoing work changes. Removing a saved memory and deleting the conversation it came from are separate actions.

Project membership determines who can participate in shared work. Review the people and roles attached to a project before adding sensitive reference material or moving a conversation into it.

• Invite the people who need access and choose the appropriate role.
• Review members when a collaborator changes responsibilities or leaves a project.
• Revoke unused invitations and join links.
• Check the audience again before moving an existing conversation into a shared project.

A shared conversation snapshot creates a separate view for recipients. Review the material included before creating a link, and use the sharing controls to revoke access when the link is no longer needed.

Revoking a link stops future access through that link. Treat material that a recipient has already copied or downloaded as information you have shared.

• Connected apps and permissions
• Working with AI output
• Enterprise evaluation

Return to the Trust Center