Docs

Resources

Learn the shared Workbase model behind search, mentions, previews, relations, favorites, and agent context.

A resource is anything Workbase can treat as a workspace item. Resources are the connective model behind search, mentions, previews, relations, favorites, agent context, and navigation.

Common resource types

Workbase resources can include assistant conversations, custom agents, inbox conversations, files, folders, users, automations, agent runs, apps, lists, list entries, list views, MCP tools, notes, objects, object records, object views, skills, tasks, and boards.

Not every resource supports every action. Some can be opened, previewed, related, favorited, renamed, or shown in the sidebar. Others are read-only or used only in specific workflows.

Why resources matter

Resources let Workbase avoid isolated product areas. A customer conversation can relate to a company record. A record can be added to a list. An agent can read a note or file. A task can preserve follow-up context. Search can find all of them through one model.

Search and read behavior

Workspace search can return matching resources from navigation, records, inbox, library, lists, notes, apps, automations, MCP tools, skills, and the resource index. For AI and agent workflows, a search result can be opened or read with more detail when the workflow needs deeper context.

Mentions and selection

When a product surface asks you to choose workspace context, it often uses the same resource search model. This keeps agent connections, relation pickers, mention pickers, command palette results, and other selectors consistent.

Resource actions

Depending on the resource type, actions can include:

  • Copying a link.
  • Opening the resource.
  • Previewing the resource.
  • Favoriting the resource.
  • Renaming the resource.
  • Editing the icon.
  • Relating it to another resource.
  • Showing it in the sidebar.

Best practices

  • Create resources where the work actually belongs. Do not use notes for records or inbox status for tasks.
  • Use relations when two items should stay connected across workflows.
  • Use favorites for your personal access.
  • Use sidebar visibility for team-level navigation.
  • Connect agents to specific resources instead of asking them to infer context.

Related pages

Last updated