Interviews - Locking Content ๐Ÿ”

ร‰pinglรฉe En avant

Hello Wrike Community!

I'm Slava, a Product Manager here at Wrike.

We're always looking for ways to improve your experience and make our product more efficient and intuitive (we hope that many of you are enjoying the recent update to the Item view that we released after receiving your feedback on the previous iteration).

One of the areas we're looking to focus on is the ability to lock item content from changes and we want to hear your ideas and use cases for this potential future feature and what challenges you're facing right now ๐Ÿ“Œ

We understand that locking content may be an important part of your workflow, and weโ€™ve seen your feedback related to that in the Community (for example, in this thread).

Iโ€™d like to invite you to participate in user interviews with me and my team.

During these interviews, you'll have the opportunity to:

  • Share your experiences and insightsย 
  • Discuss any challenges you've faced and improvements you'd like to see
  • Preview potential updates and provide early feedback

The interview will take around 30-45 minutes.

If you're interested, please pick a time slot on my calendar here.ย Weโ€™ll disable this link once we have enough participants.

Iโ€™m looking forward to chatting with you, and thanks for your help!ย 

ย 

Slava Kogan Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalitรฉs et les meilleures pratiques grace ร  nos Webinaires online

Slava Kogan Wrike Team member En savoir plus sur les fonctionalitรฉs et les meilleures pratiques grace ร  nos Webinaires online

0
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos
6ย commentaires

Hi, I'm not available for an interview due to differing time zones but I wanted to make a comment regarding locking content.ย  An example of something we have been experiencing is clients making comments on documents and designs before the assets are ready for the client to view.ย  i.e. our design team upload their files and tag various people for review/approval prior to sending onto the client.ย  However if the client is a Wrike user they have been able to go in and view these files before they are ready and make comments/changes.ย  I'm not sure if this is something that would be a part of what you are considering here but it would be great to be able to fully lock down certain parts of a project so only a select number of people can view this section.ย  At the moment as a work around to this we create separate projects where the working design files are uploaded and comments/edits between the design team are made here and the final files are then uploaded into the parent project for the client.ย  It would be great to not have to create a whole separate project.ย  Look forward to seeing what comes from this!

1
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

Thank you for sharing your use case Amy Hunter, it's very useful for Slava and his team ๐Ÿ™Œ

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

hello Slava Kogan, have you had some progress on considering this feature. ย I find myself in a love hate relationship with Wrike. ย Great for flexibility but very time intensive to manage the fields that need constant monitoring. ย having the ability to have Custom Fields visible to some users , while being editable to only certain others is critical for us admin's to be able to fully utilize the benefits of the flexibility built into wrike.ย 

1
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

MW - brought up a good point: visibility and edibility of Custom Fields, which I think is quite a mess currently:

  1. Access Role settings are a jumble of various bits and pieces, but not related to Custom Fields as such
  2. Space-level Custom Fields are available to members of the space, but space editing rights are controlled by Access Roles
  3. Space-level Custom Fields lack the "visible only to specific users" setting available Account-level Custom Fields
  4. Unless users' access to the space has been set to e.g. read-only, visible Custom Fields are editable
  5. Account-level Custom Fields can be set visible to everyone in the account, or only to specific users
  6. Even if the visibility of Account-level Custom Fields can be restricted to specific users, editability can't be restricted to specific users - if it's visible, it's editable

I would appreciate separate settings for the visibility and the editing rights of Custom Fields, and the same settings available to both Account-level and Space-level Custom Fields. I think this is very much a case for Locking Content.

0
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

wow Tuomo Suominen, great recap, thanks for bringing in such clarity to the issues relating to Custom Fields. ย I hope the Wrike development team takes this feedback on board. ย Slava Kogan

0
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

I'm sharing your feedback with Slava now, folks!ย 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
๐Ÿ‘ Spot On ๐Ÿ’ก Innovative Approach ๐Ÿ’ช Stellar Advice โœ… Solved ๐Ÿช„ Remove Kudos

Folllowing List for Post: Interviews - Locking Content ๐Ÿ”
[this list is visible for admins and agents only]

Haut de la page
Didnโ€™t find what you were looking for? Write new post