Provide informational hierarchy using subcollections

Nest Collections inside a parent Collection when a single Collection grows too long to browse. Also called SubCollections, these nested Collections keep related items together while preserving a clear hierarchy.

note

Projects are replacing Collections. Existing Collections automatically migrate to Projects with all content and permissions preserved.

Prerequisites

• Access to Collections in Glean
• Permission to edit the parent Collection

When to use nested Collections

Create a nested Collection when you need structure beyond headers, for example:

• Subteams, subtopics, or subprojects under a team or product Collection
• Different audiences under the same umbrella topic, such as sales development and account executives under an Onboarding header
• More than about five documents or links under the same topic
• A parent Collection that has grown past about 20 documents and links

How to create a nested Collection

1. Open the parent Collection.
2. Click Add in the upper right, then select New collection.
3. To insert a nested Collection between existing items, click the + control between items, or use Add… at the bottom of the page.

Move a Collection under another Collection

1. On the Collections dashboard, open the three-dot menu for the Collection.
2. Select Move to.
3. Choose the parent Collection.

Each Collection can have only one parent.

Limits

• Up to 20 Collections under a single parent
• Nesting up to three levels deep under a top-level Collection (four Collections in the chain at most)

How nested Collections appear

• Nested Collections can appear in search results based on relevance.
• When a document belongs to a nested Collection, that Collection can appear on the search result.
• On the unfiltered Collections dashboard, only top-level Collections are listed, so nested Collections stay out of the main list.

See also

• How Collections work
• How Projects work