Blocking watching+discussion

My guess. No. But more work on sets and settings will enable this ;-)

Ha! Wait, so are you seeing a scenario where people *can* view a card but *can't* watch it? If I'm not mistaken, it would currently not work to watch a card you can't see (even if you were on the list you wouldn't get updates)

  --Ethan McCutchen.....Wed Feb 24 10:47:28 -0800 2010

from bolcking to bocking :) baby steps.

  --Ethan McCutchen.....Wed Feb 24 10:47:52 -0800 2010

Whew. I made it. ;-]

  --Peter Kindfield.....Thu Feb 25 05:07:19 -0800 2010

So is there really a scenario where you want people to be able to view a card but not able to watch it?

  --Ethan McCutchen.....Sun Feb 28 16:42:00 -0800 2010

No. Being able to block specified users from viewing and watching together would be fine.

  --Peter Kindfield.....Mon Mar 01 04:30:33 -0800 2010

Then you can, in that individual card's Options tab), change the menu so that only Administrator ...can read this card.

  --John Abbe.....Sat May 01 16:07:11 -0700 2010

Hey John, Won't that block all users, other than the creator and administrator from viewing that card? What I really want to be able to do is define a set of users that can (or can't) view and watch.

  --Peter Kindfield.....Sat May 01 16:16:01 -0700 2010

You can specify any one Role a user must have to view. It doesn't have to be Administrator. (And users can have multiple roles.) There's no way to specify a role as not being allowed to view a given card.

Note that users of a given role can have permission to create cards of a given type even if they can't view the cards created (create permission is in the Options tab of the cardtype card, e.g. User, Image, or your custom cardtypes). In that case, you can control what they see after creating cards of that type with thank you messages.

  --John Abbe.....Sat May 01 17:29:24 -0700 2010

Hey John, I'm not sure if you remember that we have authors and editors associated with a "content" cards (resources, activities and topics). It would be great for us if a cards author (originally the card's creator) could allow other people to be authors and editors and if write permission could be associated with people in either list. The general idea is to be able to set permissions for a list specific people (in addition to being able to set permissions for roles). I guess what I am proposing is roles per card. That is: this list of users can do these things with this card.

  --Peter Kindfield.....Sat May 01 19:02:16 -0700 2010

That, alas, will have to wait for a major overhaul of our permissions system. I'm guessing not this year.

  --John Abbe.....Sat May 01 22:07:12 -0700 2010

Oh, geez, I hope we get that done this year. It's the only piece that really has to happen to complete the conversion over to sets/settings. Lew and I have already done a lot of the planning work down to a fairly low level. I suspect we'll start working on it in June, but progress is likely to be fairly slow, as there are other competing priorities.

Peter, the new permissions system will allow you to set create, read, update, delete, and comment permissions for any set of cards. Each permission can point to an individual user or group of users. You can do this pretty dynamically, and we'll be moving away from the rigid, monolithic Roles.

It's definitely, as John says, a major overhaul. But it's important that we make this structural change before introducing modules, so it's pretty high priority.

  --Ethan McCutchen.....Tue May 18 22:42:33 -0700 2010

Sounds like an excellent plan Ethan. Several questions. Who sets permissions? The card creator and folks in the admin group? Will groups be any set of users for any set of cards? Will it be possible to set a permission so that sets of users can read the code under a card but not edit that code (not that important to me but...)?

  --Peter Kindfield.....Wed May 19 05:32:46 -0700 2010