File Packages
Packages enable you to work with conceptual groups of files that represent milestones, releases, and shared scopes of information.
A Solution to File Duplication
If you want to add a specific file version from one folder to another, you have to copy the file over. This can lead to confusion with multiple copies of the same file version existing in different folders.
When you add files to a package, they become associated to the package and do not copy over. This means that files can be associated with multiple packages without standalone copies being made.
Flexible Package Types
Fixed version packages
You can group specific versions of files into a fixed version package and these versions will remain fixed even when newer versions exist. Fixed versions packages can hold historical records which remain stable over time, any of which may need to be referenced at any time. This is useful when file versions increase as a project grows, and at certain times a 'snapshot' of a specific version is needed. For example, incoming releases, documents, or addenda, or outgoing documents that may be needed for bidding, estimation, permitting, or handover.
Current version packages
You can group files into a current version package where the files will automatically update to their current version.
Controlled and Flexible Permissions
Packages have their own permission system. Project administrators can grant package manager permission to other project members as a user, role, or company as required. Package managers can then view and create packages along with many package actions detailed in the Package Permissions help topic.
Manage Packages and Files
You can view and manage the whole package including:
- Delete packages
- Lock packages
- Unlock packages
- Share packages
- Edit packages
Integrates with Key Workflows
You can consume files in a package using the following key workflows:
- Publish to Sheets
- Download source files
- Share
- Export
- Submit for review
- Create transmittals