+34
Committed

Agree to terms and conditions upon dowload

Joris Wynendaele [Aprimo] 11 months ago in Digital Asset Management updated by petra.tant 3 weeks ago 12

As a user I need to accept terms an conditions when downloading an asset. That info is then captured and logged for auditing reasons later on.

Committed

To all people who have voted we would like your input on the following, please only answer out of your own concrete needs:
1) is the fact you have to accept a EULA as user, something you switch on for the whole environment, so it will come up on any type of download your user does or would you only have it on for certain content for the same user?
2) would you have one terms & conditions for all users, or would terms & conditions actually be depending on the content itself, depend on the user group, the type of content, the brand, other?

Hi Petra, 

Related but not exactly the same, are there any plans to allow for agreement to terms and conditions upon upload?  ie. if a user goes to the new UI and wants to upload content, we can provide them a waiver guaranteeing rights to the shared content. 

Thanks, 

~Rachel

Rachel, would you mind logging the upload one as a separate voice request?

This would be a valuable feature to help with our governance model as our staff sometimes overlook rights restrictions when using assets. We'd like to be able to enable this functionality for asset types with certain sensitive rights restrictions so that we can be assured that our users have read and understood those restrictions before using the asset.

To all people who have voted we would like your input on the following, please only answer out of your own concrete needs:
1) is the fact you have to accept a EULA as user, something you switch on for the whole environment, so it will come up on any type of download your user does?
2) would you have one terms & conditions for all users, or would terms & conditions actually be different by user group, by type of content, or by brand or other? 

We have generally created a singular terms and conditions to cover the entire site and user base.  That would be our initial ask.  

what should be a use case when EULA is changed? do we need to support versions of terms and conditions?

We have this on the DAM roadmap this year. I will be able to be more specific on provisioned timing in Q2-19.

Hi Petra, Are there an updates to the timing of this feature?  Additionally is this feature being created as an always/never dichotomy or something more flexible (ie. if a user has accepted terms and conditions once, they will not be asked again)

Hello Petra, any update on this?