Skip to main content
Describe your task and name the project. The assistant selects from these 62 tools. See Projects and permissions for access levels.

Projects and knowledge

Reading requires Read access. See Knowledge and citations for search and retrieval behavior.

Project tools

Choose the project by name or ID. The assistant’s access must meet the level shown below. Changes to lesson configuration require Admin, and comment editing follows Sovara’s normal ownership permissions.

Runs and annotations

Automations

Lessons and workspaces

Proposals

Issues and conversations

Lesson proposal workflow

Lesson edits are saved in proposals. Proposal saved means a draft is ready for review; Proposal applied means its changes are published.
  1. Ask the assistant to propose a change.
  2. Open the proposal link and review or revise it.
  3. Apply it in Sovara or ask the assistant to apply it.
If published lessons have changed, resolve conflicts before applying. Lesson configuration changes require Admin access.

Organize runs with tags

Tag colors: #0969da (default blue), #1a7f37, #cf222e, #bf8700, #8250df, #e85aad, #0598d5, #d1570a, #5e60ce, and #1b8a72. Assigning tags replaces a run’s full tag list. Include existing tags you want to keep; an empty list clears them. Deleting a tag removes it from every run using it.

Automations

Describe the schedule, timezone, and task. Automations are enabled by default; ask for a paused automation if you want to review it first. Automations continue after the chat ends or the MCP connection is disconnected. Pause or delete them to stop future scheduled work. Executions use your configured models and consume model usage.