This article contains all terms and expressions used in Cohero, and explains their meaning along with references to specific articles in this knowledge base.
Term | Definition | Related article |
Action menu | A side menu, available for many items in Cohero - marked with an ellipsis (...) |
|
Asset | Assets are defined as the output of a creation process. They can be customer-facing assets (brochure layouts, leaflets, posters), but also internal-facing assets (newsletters, presentations, guidelines) or even rough mock-ups (eg: web page layouts). |
|
Asset id | Each asset has a unique identifier (id) in Cohero. This enables users to have absolute certainty that they're sharing the right asset. Asset id's are a string of 12 unique alphanumeric characters (like: zWSJYDwXp97X). |
|
Asset info | A combination of General and (optional) Custom info fields, forming the asset's data model. Each field describes a unique aspect of an asset (for instance: its purpose, or the target audiences). | 'Editing asset info': link |
Asset type | This general asset info field lists out the types of assets you create in your workspace. As each organization will work on different types of assets, this list will be custom, but some examples would be: brochure, leaflet, newsletter template, video, blog post, and so forth. |
|
'Assets' page | The 'Assets' page in the workspace-level navigation, is where you can see and navigate all assets (that you have permission to see) from across the workspace.
The 'Assets' page on space-level, is where you can see all assets within that particular space. |
|
Asset lifecycle | The time period between an assets initial creation, and its cancellation, expiry or withdrawal. In other words: the time during which it requires active care and review. |
|
Asset manager | The person responsible for the successful execution of an asset's creation and approval process, within time and budget. The Asset manager manages this process. |
|
Asset owner | The 'Asset owner' is the person or team accountable for the asset during its lifecycle. (s)He, or they, decide on key lifecycle moments whether to extend, update, withdraw or replace an asset. |
|
Asset page | The asset page is the page where you can view an asset version in its entirety: the actual asset, its info, attachments, comments, earlier versions, etc. |
|
Assignee | An assignee is a person or a team, who is requested to perform a certain task. |
|
Attachments | Documents or hyperlinks, leveraged to support the creation / management process, or leveraged to evidence/underpin claims made in the asset. Attachments are avaible both on asset-level and on project-level. | 'Using Attachments': link |
Due Date | Due dates are leveraged in 2 different contexts:
| 'Working with tasks': link |
Expiry date | The expiry date of an asset expresses the date beyond which the asset should no longer be available or used. On their expiry date, assets will automatically change their status into 'Expired' | 'Expired asset versions': link |
Final approval | The last step in the approval workflow is called 'Final Approval'. It is a mandatory approval step in order to complete the approval workflow, and to release the asset |
|
Project | Projects are a way to group the creation (or revision) of a number of asset versions at the same time. In that context, projects play a temporary role (their reason | 'Working in projects': link |
Project dates | The timespan for a project to start and finish. |
|
Project manager | The person responsible to manage a project |
|
'Projects' page | The 'Projects' page on workspace-'level, is where you can see all projects (to which you have at least viewing permission) from across the workspace. |
|
Release date | The Release date is the date on which the asset is released. While the asset is in draft, it communicates the aspired release date (to inform reviewers and approvers). |
|
Space | Spaces are virtual sections of a workspace, where teams work together on content of a similar nature, or with a similar purpose. The way how spaces are set up, and differentiated, varies per workspace.
|
|
Task | A task is a concrete request one person makes to another (or to multiple others). In case of multiple assignees, any of the assignees is capable to close the task. | 'Working with tasks': link |
Team | A group of Cohero users, available to be assigned to tasks, mentioned in comments, invited to approve, and assigned as Project Manager, Asset Manager and Asset Owner. | 'Group management': link |
Version (number) | Cohero's 3-digit version syntax (Eg: V1.2.3), that expresses the asset version's predecessors and corrections made. The first two digits of the version are currently visible in the version menus. The third digit is only visible in the URL. | 'Versioning Logic': link |
View | A view is a customizeable rendering of resources (eg: of assets, or projects) by specific parameters. A view is customizable to the extent that a user can: (1) name the view, (2) choose a preferred layout, and (3) set it to public or private. | 'Views': link |
Workspace | All work happens inside one workspace. You can see the name of your workspace in the top left corner of your interface. A workspace is subdivided into one or multiple spaces. |
|