Organize content with Projects
Projects help you organize chats and content in Glean so related work is easier to group, revisit, and share. You can think of a project as a workspace where you keep relevant chats, documents, and artifacts together in one place.
With projects, you can:
- Plan a product launch: Group the planning doc, Jira epic, design folder, and related Glean chats in a single project so your cross-functional team stays aligned.
- Onboard a new teammate: Organize all the onboarding resources, chats, and documents a new employee needs into a project and share it with them on day one.
- Research a topic across multiple tools: Keep your research chats, source documents, and generated artifacts in one project so you can pick up where you left off.
Create a project
Here's how to create a project:
- Open Library from the navigation bar.
- Select the arrow next to Create Artifact, then select Project.
- Give the project a title and an optional description.
Projects are private by default. You can share a project with specific people or groups when you're ready.
Add content to a project
You can add the following types of content to a project:
- Chats — keep related Glean Assistant conversations together.
- Documents — add documents from any connected workplace app.
- Interactive content — include generated content like canvases, slide decks, and spreadsheets.
- Files — upload files directly to the project.
- URLs — add links to external content that isn't indexed in Glean.
Share a project
Select the Share button on any project to manage who can view or edit it. You can share with individual users or groups, and adjust permissions at any time.
Any chats and artifacts you create in a project are visible to all project members by default.
Migration from Collections
Existing Collections automatically migrate to Projects. All content and permissions are preserved during the migration, so you don't need to recreate anything.
If you previously used Collections, your existing Collections appear as projects with the same content, structure, and access controls.
For more details on how Collections worked before the migration, see How Collections work.