Skip to main content
Library Lists help you shape the Library into clear, recommended sets without copying files or splitting content across places. Use this page to learn when Lists are useful and how they can help your users find the right content faster.

​
The role of Lists inside the Library

Lists are a tagging system for content within the Kinship Library. It groups existing Library items into meaningful sets so your team can find and load the right things quickly.
  • No duplication: items stay where they are in the Library. A List is a label, not a container.
  • Safe to reorganize: add or remove items freely. Deleting a List never deletes content.

​
Lists have two main functions

  • Your users can filter their search results down to a specific List when searching content in Revit, making it easier to find what they are looking for.
  • You can also load entire lists in to Revit using Kinship.

​
Lists vs Collections (the short version)

  • Lists keep everything inside the Library. Use Lists to curate and filter approved content for common needs, while keeping a single source of truth.
  • Collections are alternative libraries. Use Collections to isolate specialized sets (client, project, manufacturer, legacy, WIP) or to share with partners.
For a full comparison and trade-offs, see Library vs Collections: How to choose.

​
Where Lists shine

Use Lists when you want to recommend, group, or highlight content that already belongs in the Library:
  • Starter packs: Architectural or MEP kits for new projects.
  • Discipline or sector bundles: Healthcare, education, residential, interiors.
  • Phase or theme sets: Early design, documentation, detailing.

​
Anti-patterns to avoid

  • Using a List as a gate: Lists do not control access. If you need restricted visibility or separation, consider a Collection.
  • Expecting Lists to change ranking: Lists do not raise results in search. They are used as a filter.
  • List for WIP content: If content is not ready, keep it in the Pending Approval section of the Library, or use a Collection set to not display results in Revit searches.
  • Duplicating Revit’s built-in organization: The Library already organizes content by category and discipline, so there’s no need to recreate that structure with Lists. Many firms coming from folder-based setups are used to organizing content by Revit category — but in Kinship, that organization is already built in. Instead, use Lists to group content in more meaningful ways, like by project type, design system, or team workflow.

​
Short scenarios

“We have a standard set of content needed on most models from day one.”
Instead of keeping in in your Revit model templatem, Create a List with essential title blocks, details, tags, and templates. “We need a sector starter pack.”
Create sector Lists (for example, Healthcare, Education). Add the approved Library items that teams typically load on day one. Teams filter by the List and batch-load what they need. “We need to group high-usage door families.”
Create a “Doors — Recommended” List. Add the approved door families that analytics show are used most and modified least. This highlights proven choices while leaving the Library structure unchanged. “We need a quick way to load related elements for a design.”
Create a List that brings together related content, like all the elements needed for a concrete structural system — walls, floors, roofs, and associated details. This makes it easy for users to find and load all the relevant components for a specific design approach.

​
Learn more