Release Notes
Flexible Query Organization
Choose where to save your query to better organize projects and share work across your team.
What's New
We’ve added the ability to move queries between projects or into your private history, giving you more control over where your work lives. Whether you’re organizing research or cleaning up shared projects, this update makes it easier to keep queries aligned with your workflow.
- Move queries from Assistant into projects: Threads created in Assistant can now be added to a relevant Vault project for better organization and visibility.
- Move or remove queries from projects: Take queries out of a project to make them private, or move them into another project.
- Access-based visibility: When you move a query, access automatically updates to match its new project’s permissions.
- Support for multiple query types: Move queries made in Assistant, over Vault projects, or from workflow runs (excluding knowledge base or review table queries).
Why it Matters
Previously, queries were stuck where they were created—making it hard to manage research or reassign work. Now, you can relocate queries as projects evolve, avoid cluttering shared spaces with private drafts, and keep related work consolidated for easier tracking and collaboration.
How to Use
- For any thread created from Assistant, move the thread into a project. Users with access to the project can now view your thread.
- For any query created in a Vault project, you can now:
- Remove the thread. You should see the thread in your History and removed from the Vault project.
- Move it to a different Vault project. Those with access to the recipient Vault project will have access to the thread.
From a thread that is not yet associated with a project, you can select Add to project. Once added to a project, you can click into a thread and choose to remove or move it from the project.
Use Case | Example |
|---|---|
Store queries (without files) relevant to a project | When performing case law research, I create a query via Assistant + a case law knowledge source. I move these queries into the Vault project for my existing case, so my legal research is located in the same project. |
Move queries using files from an existing project into a new relevant project | When drafting a motion, I want to reference queries I made from a past Vault project. I can now move these past queries into a different project for a new case. |
Remove private queries from a shared project | I make several queries in a Vault project for my own research / scratch work. I move these queries out of the project into my private history of queries, so I can still view them without cluttering up my team’s shared Vault project. |
Query view-only projects | I have view-only access to a project. I can query it (privately), using the files as a knowledge source but I CANNOT add the query to the project until I am granted edit access to that project. |
Notes and Limitations:
- You need edit permissions in both the source and destination projects to move a query.
- Users with view-only access can run queries against a project, but can’t add or move them into that project.
- Moving a query resets its retention timer to match the new location’s policy.
- This feature does not apply to queries on knowledge bases or queries that create review tables.
FAQs
Q: Can I query a project if I only have view access?
Yes. Queries can now be run against a project without edit access. These queries will be stored in the user’s private history.
Q: Can I keep my queries private when working in a shared project?
Yes. You can move a query out of a shared project, and it will appear as a standalone thread in your History page.
Q: How is access impacted by a query moving in or out of a project?
A query’s view permissions are the same as the view permissions as its host project. If a query is moved from Project A to Project B, users who do not have access to Project B will no longer see the query, and users who do have access to Project B will now have access to seeing the query. Individual users who were initially shared the query will lose access unless they have access to Project B.
Q: What types of queries can be moved in/out of projects?
This applies to:
• Queries made on Assistant
• Queries made over Vault projects
• Queries on Assistant over review tables
• Workflow runs
You cannot move queries on knowledge bases or queries that create review tables.
Q: Who can I share a moved query with?
If the query is not attached to a project, it can be shared with anyone in your workspace. If the query is attached to a project, it can only be shared with users that have access to that project.
Q: If I create a query using a file from a single Vault project in Assistant, where will the query be saved?
The query will be saved to that Vault project only if you have edit access. You can move the query to a different Vault project or your private history after it’s been created. If you only have view access to that project, it will be saved in your private history.
Q: What permissions are required to move a query between projects?
You will need edit permissions for both the project you are removing the query from and the project you are adding the query to. You cannot move the query with only view permissions on either project.
Q: Can users share queries based on files in a KB?
No, not yet, but this is something we’re considering for the future.
Q: How does retention policy change when I move my query?
When you move a query, its retention timer resets to match the new location's policy.
Example: If Assistant retention is 3 days and project retention is 8 days:
• Day 1: Create query in Assistant (will expire Day 4)
• Day 3: Move to project → timer resets, query now expires Day 11 (Day 3 + 8 days)
• Day 10: Move out of project → timer resets, query now expires Day 13