Managing Revit content well is one of the biggest challenges teams face. Two tools handle most of it: the Library and Collections. Projects and Models also show content, but those views are records of what’s currently in the model. The content there can change at any time and isn’t managed directly. When we talk about content management, we mean the Library and Collections. This page explains what each is, what it’s for, and how they work together to support your team’s content workflows.Documentation Index
Fetch the complete documentation index at: https://docs.kinship.io/llms.txt
Use this file to discover all available pages before exploring further.
Managed vs. recorded content
- The Library is your team’s central, approved repository for general-purpose content. This is where most of your content should live.
- Collections are separate libraries for content that’s specific to a project, client, manufacturer, or other context.
- Projects and Models show what’s currently loaded in tracked Revit models. That content isn’t managed the same way, and may change as the model evolves.
Search and prioritization
Search in Revit sorts results by relevance and by content source. Library items appear near the top, marked with a green icon. This prioritization helps your team load the right content — the content Content Managers have approved and maintained. When a Collection is assigned to a project, its items appear even above Library content because they’ve been selected specifically for that project. They’re marked with a blue icon and treated as project content in search results.The Library: your firmwide source of truth
The Library is where you store and manage content that’s approved, maintained, and intended for use across all your team’s projects. It serves as the central source of truth for content you want everyone to use.What it holds
The Library supports a wide range of Revit content: loadable (component) families, system families, views, sheets, view templates, schedules, materials, fill patterns, filled regions, and more. See Supported content types for the complete list.How it’s organized
Content is organized automatically by discipline and category. You can also group items into custom Lists for curated sets, such as sector-specific kits. See Library Lists.Suggested content
If you’re tracking projects, content that appears often in your models but isn’t yet in your Library is suggested to you automatically. Suggested content shows the percentage of tracked projects an item appears in, along with the number of placed instances. Drilling in shows the specific project instances, where you can review the content and add it to the Library.Automated quality checks
Health checks automatically flag common issues, such as missing default types or non-native geometry. See Content health reports.Pending Approval
Content in Pending Approval can’t be searched or placed from Revit. It stays in this section until it’s approved and moved to the Library or a Collection. Content can be in Pending Approval for one of three reasons:- A Team Member uploaded it. Content uploaded by a Team Member always starts in Pending Approval.
- An Administrator uploaded it and chose Add as Pending Approval.
- An Administrator removed it from the Library to resolve an issue before re-approving it.
Collections: separate libraries for specialized needs
Collections are independent libraries for content that isn’t part of your main Library — client-specific standards, manufacturer content, legacy sets, work-in-progress, and more. Each Collection is fully separate from the Library and from other Collections, with its own content, settings, and access controls. Collections sit alongside the Library, not inside it. Use them when content has a specific audience, context, or lifecycle that shouldn’t bleed into your firmwide standards. For a full overview of what Collections can do and when to use them, see Collections.Real-world patterns
Many teams use the Library and Collections side by side to match how they work:- Firmwide baseline: Store your approved standards in the Library.
- Specialized needs: Use Collections for project-specific or client-specific variations.
- Project targeting: Assign a Collection to a project to prioritize its content in search.
- Confidential work: Combine restricted Collections with restricted projects to control access.
- Partner collaboration: Use shared Collections to work with other firms or vendors.