USE CASES
What teams use ContentCamel for
These pages describe specific jobs that ContentCamel handles, written in terms of what the application does at each step. Each starts from a situation, such as collecting files from clients, tracking licence expiry or replacing email attachments, and lists the features involved with a link to the product page. They are organised by task rather than by industry, so choose the one closest to the problem you are trying to solve.
-
Collect files back from clients through a share link
Let clients upload through the share link and review each file before it enters the library.
Read the use case: Collect files back from clients through a share link -
Keep brand assets and their licences in one place
Hold logos, colours, fonts and guidelines together with the licence details of each asset.
Read the use case: Keep brand assets and their licences in one place -
Keep a version history for files clients rely on
Replace files without losing the earlier ones, and restore a version when needed.
Read the use case: Keep a version history for files clients rely on -
Run each client as a project with its own access
Give each client or campaign its own project, roles and message board.
Read the use case: Run each client as a project with its own access -
Bring email attachments into the library
Forward attachments to the organisation's address and import the ones worth keeping.
Read the use case: Bring email attachments into the library -
See what happened to a file you shared
See who opened, downloaded or uploaded through each share link.
Read the use case: See what happened to a file you shared -
Share approved assets with partners and press
Share approved material with partners and press through limited, revocable links.
Read the use case: Share approved assets with partners and press -
Replace email attachments with one link
Send one link in place of attachments and one-off file transfers.
Read the use case: Replace email attachments with one link -
Track licence and rights expiry on the asset itself
Record rights on the asset, get warnings ahead of expiry and block sharing once it passes.
Read the use case: Track licence and rights expiry on the asset itself -
Keep a list of media people have asked for
Log requests for missing media and close them with the asset that fulfils them.
Read the use case: Keep a list of media people have asked for -
Receive revisions from external designers in one place
Receive each round of freelance work through one link and keep revisions as versions.
Read the use case: Receive revisions from external designers in one place -
Store brand files in the EU, separate from other clients
Keep files in Germany on a separate instance for each organisation.
Read the use case: Store brand files in the EU, separate from other clients
Not sure which one fits?
The product tour shows every feature in context, or you can write to us with the job you need done.