In this article we'll cover the following topics:
1. Assets' optional association to projects
1. Assets' optional association to projects
An asset's relation to a project is optional. Assets can be created in the context of a project, but they can also be created outside that project's context - just inside the space they sit in.
Use case for creating a version inside a project
An asset's versions can be captured in varying projects within a space. After all, over time, an asset can grow by adding new versions. It is not uncommon in Cohero to see assets with more than 5 or even 10 versions - each created over the course of time, and triggered by different events or needs. Projects are helpful primarily because they offer a context, to help a user understand the 'why' behind an asset version. They help explainining why that was created, or perhaps its role in a wider perspective (eg: a campaign, or a larger effort to update assets broadly) among other assets.
Use case for creating a version outside a project
Just as well, an asset can be created without a bigger plan or strategy. Perhaps a periodical update was due, a mere spelling mistake needed correcting, or the contact details contained a mistake. In any of these cases, there's no bigger business motivation other than merely responding to an emerged issue.
2. Relate an asset to a project
Both new (draft) or existing assets can live without any association to a project. However, there's a use case to be found to want to create that association to a project, for instance if an asset was created outside the project by mistake - or if the project was created, after the asset was started.
To add an existing (or new) asset to a project goes as follows: click on the ellipsis (...) on the top-right corner of an asset card, or next to the asset name on the asset page - and the action menu will appear. In there, choose the option 'Add to project'.
A dialog will appear that shows the available projects you can add this asset to - all within the same space as the asset sits in. Note that you'll only be able to add it to projects you have access to.
3. View / change an asset's related project
a. Seeing the asset in its project
When you open the ellipsis (...) on the top-right corner of an asset card, you can see that an asset actually is related to a project - the menu will ofer 'View in project'. This offers a direct way to go to that project page, to see all the assets (including this one) related to that project.
b. Seeing the project an asset is related to
When an asset is already associated to a project, it is easy to see and change that relation. The associated project is permanently displayed on the asset page, in the Asset info's metadata section - where you can also find the space it sits in. Clicking this will take you directly to the project page.
c. Changing the project an asset is related to
To change an asset's relation from one project to another, just open the ellipsis (...) next to the asset name, on the asset page. A menu will open, offering the option to 'Change project'. Clicking that will trigger a dialog to appear, that shows the currently associated project, offering the option to choose a different project in the same space instead. There's even a search function, to find a project when there's many.
4. Removing an asset from a project
There is also a way to remove an asset from a project. The asset remains in the same space, unharmed, but is no longer referenced in the context of that project.
To remove an asset from a project, open the ellipsis (...) at the top-right corner of an asset card, or next to the asset name, on the asset page. A menu will appear offering the option 'Change project':
This will trigger a dialog, that shows to which project the asset is related at the moment - this related project is presented with a checkmark next to it. To remove it from its current project, simply click the existing project to uncheck it. Then press 'Save' to confirm your choices. The asset will no longer be shown in the context of that project.
