What Collections are
- Separate, alternative libraries, distinct from your main team Library.
- Independent stores: items in different Collections are distinct copies.
- Typical uses: project or client specific content, manufacturer packs, legacy content, WIP.
Scope and relationship to the Library
- Collections are not the Library. Library-specific features such as the Pending approval section or Lists are not supported within a Collection.
- The same family can exist in the Library and in one or more Collections as separate copies.
Supported content types
- Same as the Library. See Supported content types.
Visibility modes
- Team Collection: visible to all members.
- Restricted Collection: visible only to admins/security admins and explicitly permitted users.
- Optional setting to hide a Collection’s items from Revit searches while keeping them available on the web.
Contribution settings
- Default: add and modify limited to Collection managers and admins.
- Optional: allow all members to add and modify content.
Project assignment and search priority
- Assign a Collection to one or more projects.
- Assigned Collections surface above general Library results for those projects in search.
Sharing
- Internal sharing: grant view or edit access to specific users or groups.
- Cross-organization sharing: collaborate with partner firms (view or edit).
- External read-only link: share a web link for browse and download without Kinship accounts.
Permissions and access control
- Per-Collection permissions determine who can view or edit.
- For confidential work, combine Restricted Collections with restricted projects.
UI cues
- Revit add-in: Unassigned Collection items have no special icon and appear below Library results. If a Collection is assigned to the open project, its items are promoted as Project content at the very top of results and display a blue icon. Collection filters are available during search and loading.