Creating and configuring projects
A project contains a group of assets you can work on yourself or with a team. For example, a project may contain all assets for a specific game.
Perform the following steps to set up projects for your team.
Assets in Helix DAM are stored on a Helix Core Server, which tracks and manages changes to all of your assets in a single, version-controlled location. During initial Helix DAM setup, the company administrator must decide how to store assets in Helix Core Server and modify the company settings accordingly. The company settings impact the structure used to store assets and how they are added to Helix DAM. To learn more, see Choosing how to store Helix DAM assets in Helix Core.
Step 1: Create a project
Create a project to store a group of assets related to a specific effort, such a new game.
To learn more, see Creating projects.
Step 2: Add collections and assets to the project
After creating a project, add assets to it. You are prompted to either link to a Helix Core depot or create a collection depending on the Helix DAM settings.
Create a collection
If Automatic depot creation is turned on in the company settings and you selected Automatically create Helix Core depot when creating the project, you must add a new collection in the project and add assets to it. A collection contains a set of related assets in a project. A project can have more than one collection. For example, if your project is a game, you might have three collections of assets named Vehicles, Buildings, and Characters. To learn more, see Creating collections. After you create a collection, you can upload assets to it. To learn more, see Adding assets to collections.
Link to a depot
If Automatic depot creation is turned off in the company settings or if you cleared Automatically create Helix Core depot when creating the project, you must link to Helix Core depots to display assets in the project. You can link Helix Core streams, Helix Core classic depots, or both to the project.
After you link to a stream, the mainline stream is displayed in the project as a repository. The individual streams are displayed in the repository as collections, which contain assets. To learn more, see Linking projects to Helix Core Server streams.
After you link to a classic depot, the depot is displayed in the project as a repository. The individual branches are displayed in the repository as collections, which contain assets. To learn more, see Linking projects to Helix Core Server classic depots.
Step 3: Add people to the project
To give team members access to work with assets in a Helix DAM project, add them as members of the project. To learn more, see Inviting people to projects.
The user who creates the project is the project administrator. Only project admins can perform advanced tasks in projects, such as changing the workflow. If a project requires more than one admin, a project admin can make a team member an admin. To learn more, see Making a team member a project administrator.
Step 4: Configure additional project settings
You can configure additional settings to customize the project for your team's needs.
Change the workflow
Each Helix DAM project uses a workflow. The workflow defines the statuses, or states, that assets can have, which are used on the project Kanban board. A default workflow is set for all projects in a Helix DAM company, but you can use a different workflow if your project requires it.
To learn more, see Changing project workflows.
Add default reviewers
Reviewers check assets before they are released and request changes if required. Add default reviewers to the project to ensure that, when an asset review is started, a specific set of team members is always added to the review.
To learn more, see Managing default project reviewers.
Show or hide metadata fields
Metadata fields capture additional information on assets. For example, you may have a Priority metadata field with Low, Medium, and High values. Metadata field values can be used as search criteria when searching for assets.
Metadata fields are automatically displayed for all projects in a Helix DAM company, but a project admin can decide which metadata fields to show or hide in the project.
To learn more, see Managing project metadata fields.
