Hello, friends!


Hello, friends!

Just a quick question.

We plan to implement a new type of 'almost read-only' sharing - for those who share lists to get feedback from others but doesn't want them to modify the initial list.

We don't want to create many options, but we want to fit live scenarios of instructions sharing, working with the 'field crew', etc.

The initial idea is to allow only adding notes (something like 'can comment' permissions in Google Docs). Or shall we also support attachments and changing task status?

What would work best in your scenario?

Comments

  1. Leslie P29 July 2018 at 09:27

    So basically there are viewers (who can only see my outlines), editors (who have as much access as I do), and now "contributors" who could comment on existing items and add info.

    I'd say a contributor would be able to add stuff only, not change anything existing. Thus they could add sub items (maybe), add notes/comments to existing items, add attachments to existing items, but not change the original content or status of an item.

    I would want the owner/editor to be the one to have final say over whether something is completed.

    Maybe these contributors add their detail, including a photo of the completed task (which is why they need to be able to add attachments), and they could tag with #CompleteForReview or somesuch, so the owner can review and agree that the item is complete or send back to them for further work.

    I wouldn't want to have a contributor level person be able to complete items on their own, without the owner's verification.

    ReplyDelete
  2. Checkvist30 July 2018 at 05:59

    Leslie P Thanks a lot, understood!

    What do you think about the term 'contributor'? Usually, this type of a role is called 'commenter', but we think just commenting is not enough - and are trying to find a better name.

    ReplyDelete

Post a Comment

Popular posts from this blog

I'm really enjoy using checkvist, you are adding great features very quickly.

I'm really enjoy using checkvist, you are adding great features very quickly.  What I feel is missing is more use cases.  How are people using Checkvist?  What are some recommend workflows?  How many lists do you have? User Stories will not only help those of use already using Checkvist to be more effective, but attract more non-technical customers. I like to keep my lists at a minimum.  I only split out for sharing but I'd prefer not to. Here are my lists: * Inbox:  This is where zapier based integrations go.  I have Jira tickets and emails tagged with "!action" going to list which I process daily. * The List:  This is my primary list.  Everything is here.  I use sub-nodes for different areas. * Honey Do:  This is the list my wife and I share to make sure we know what we both want done around the house. * "Client Project" - I have a few Lists I share with clients (Free lance web developer). I"m looking to write a more detailed blog post. How are your l...
Read more

Hello friends

Hello friends, We are considering to change behaviour of move up/down command using ctrl+arrows for lists with hierarchy. The new approach is available on our beta site, https://beta.checkvist.com . Could you please try it out and tell us what you think? Thanks! https://beta.checkvist.com
Read more

Hello friends!

Hello friends! I'd like to ask for your opinion regarding multi-line text editing. This suggestion comes from one of our Russian-speaking customers Dolina Zamkova so here is a translated abstract of our email conversation. Current problem: When you write multi-line text, you must press 'Shift-Enter' first, then use 'Enter' to start a new line, then 'Ctrl-Enter' to submit the text. Wouldn't it be easier to have a setting that will allow using Enter to always write multi-line texts, and always submit on 'Ctrl-Enter', like you do it in text messengers? So we could add a new account-wide setting, on the Settings page: () Finish editing by pressing 'Ctrl-Enter' (convenient for multi-line text) What do you think? Do you write multi-line texts in Checkvist at all? Other thoughts of how we could make it better? :)
Read more