Skip to content
LogchefLogchef

Collections & Saved Queries

Your Library holds saved queries; collections are shared playlists for organizing them. Members run queries, editors change the shared query, and owners manage the collection, but a collection never grants access to log data.

Open the Library from the sidebar. Collections sit in the left rail; selecting one shows its queries, members, and shared teams on the right.

Saved queries

Section titled “Saved queries”

A saved query is a named, reusable query bound to a single source. It stores the query text (LogchefQL or SQL), and optionally the time range, limit, and variables.

Save one from the explorer with Save. The dialog asks for a name and lets you pick a collection in the same step (defaulting to your personal collection), so saving and organizing happen in one action.

Visibility follows source access: anyone who can reach the query’s source (through any team they belong to) can see and run it. Editing is more restricted; see Who can edit.

Collections

Section titled “Collections”

A collection is a curated list of saved queries with its own members.

  • Personal collection: every user has one, created automatically. It’s private and can’t be shared, renamed, or deleted. Think of it as your bookmarks.
  • Shared collections: anyone can create one. You become its owner and can invite teammates or share it with whole teams. Use them for on-call runbooks, incident playbooks, or a team’s go-to queries.

Create a collection with New in the Library rail, then Invite teammates or Share with team, and pin queries to it.

Roles

Section titled “Roles”

Shared collections have three roles:

Role Read & run Add/remove items Edit the queries Manage members and teams Delete collection
Member ✓ ✓ — — —
Editor ✓ ✓ ✓ — —
Owner ✓ ✓ ✓ ✓ ✓

Running, pinning, and editing always also require source access: a role in a collection never grants access to the underlying logs. A query you can’t run shows with a lock icon. Removing an item from a collection needs no source access, so participants can unpin a locked query.

Share with a team

Section titled “Share with a team”

Owners can share a collection with a whole team instead of inviting people one by one. Open the collection and choose Share with team.

  • Every current member of the team sees the collection with the Member role. This includes team admins and editors: a team share never grants Editor or Owner rights. To give someone more, invite them directly; a direct role always takes precedence.
  • Membership is live. People who join the team see the collection on their next request. People who leave the team lose it, unless they are direct members or belong to another shared team.
  • No source access is granted. A team share controls who sees the collection, not who can read logs. Each person runs only the queries whose sources their own teams can reach; the other items show with a lock icon, and the server rejects any attempt to run them.
  • Which teams you can pick: owners can share with teams they belong to. Global admins can share their own collections with any team. Being a global admin does not let you manage someone else’s collection. OAuth tokens are read-only and cannot change shares. The global admin role does not apply through OAuth, so only collection owners can read the member and team lists with those tokens.
  • Removing a share affects only that team. Direct members and other shared teams keep access. Owners can remove a share even after they leave the team. Deleting a team removes its shares automatically.
  • Personal collections can’t be shared with teams.

The member count shows direct members only (owners included); shared teams are listed and counted separately. Only owners see the member and team lists. A global admin sees them only when they also participate in the collection, directly or through a shared team, and still needs to be an owner to change them. Other members and editors don’t see either list. Leaving a collection removes your direct membership only; you keep access through a shared team until you leave that team or the owner removes the share.

Who can edit a query

Section titled “Who can edit a query”

A saved query can be edited by:

  1. its creator,
  2. a global admin, or
  3. an owner or editor of a shared collection that contains it (still requiring source access).

Because a saved query is a single shared row, editing it changes it everywhere it appears, in every collection and for every viewer. To make a variant instead of changing the shared one, save a new query rather than editing.

Deleting a query is more restricted than editing: only the creator or a global admin can delete it, since deletion removes it from every collection at once.

Common workflows

Section titled “Common workflows”

Share a team’s go-to queries

  1. New → name the collection (e.g. “Payments on-call”).
  2. Share with team to give the whole team read & run access, or Invite individuals as Members (read & run) or Editors (can also refine the queries).
  3. Open each query in the explorer and Save it into the collection.

Hand a query to a teammate to maintain

Add them to a shared collection containing the query as an Editor. They can now open it, change it, and re-save without needing global-admin rights.

Next steps

Section titled “Next steps”