|
|
re: Questions about locking, default tags, and group memberships
 a reply to Questions about locking, default tags, and group membershipsby Laura Carrillo on Mar 31, 2008 - 08:18 AM read 92 times |
Thanks so much for your input Scott! I have a question/comment about the below comment and response:
"Right.lt just adds one more step to the process, manually removing the lock tag. I know most of us will remember to do that but I have trouble believing that others on the team would when they reply or start their own conversations."
Replies have the same security as the originating conversation. Put another way: the visibility of a reply cannot be increased or decreased. Also, I'm glad folks are feeling increasingly comfortable with knowing when to add or remove a secure tag.
My original thought was that those of us who manage or administer research projects as a major part of our job will remember to manually take the lock off, since we do a good portion of the hub posting. However, most research teams are made up of 6-12 contributors including BSG research staff, consultants, executives and external gurus, who may or may not post a great deal. Are we going to have to constantly remind them to take off the BSGLock everytime they want to start a thread for the project? or keep reviewing conversations to make sure that the entire team can see them? I know that the peoploe posting will remember to add the team tag so that only team members can see a post, however taking off the BSGlock as an added step creates some added complexity. Any ideas on how to make it easier?
-
re: Questions about locking, default tags, and group memberships
a reply to re: Questions about locking, default tags, and group memberships
in a conversation thread started here
by Brittain on Mar 31, 2008 - 01:13 PM read 86 timesExcellent questions, a few thoughts:
- This default "BSGLock" behavior only applies to BSG Employees. So for your external individuals this behavior isn't a factor.
- As an fyi, we could enable this behavior for any group using any tag (e.g. anyone in Apps Team has "Tuna Fish" as a default tag), we've simply chosen this policy.
- As mentioned above, any individual can opt out of this behavior from their Preferences page. If you've people who feel comfortable with the tagging, then advising them to change their preference would eliminate the extra step.
- This default "BSGLock" behavior only applies to BSG Employees. So for your external individuals this behavior isn't a factor.
-
re: re: Questions about locking, default tags, and group memberships
a reply to re: Questions about locking, default tags, and group memberships
in a conversation thread started here
by Laura Carrillo on Mar 31, 2008 - 01:40 PM read 83 timesThanks Scott. I know that it won't be an issue for the 1 or 2 external gurus that might start a post as part of a research project. My concern is for the 6-10 other people on the team(all BSGers) that may not remember to unlock the tag. I wouldn't ask them to change their preferences unless they were comfortable doing so. I guess my thought is that I will have to monitor the team pages to make sure that all conversations are tagged so that the appropriate people can see them.(all team members regardless of bsg or concours email) Seems like a bunch of extra work, no? I can be working on 3-4 research projects at one time, right now Projects PBG, TAD and REC have hubs set up...more projects launching soon.
I appreciate your thoughts and just ask that these issues be addressed during the next tagging/security discussions.
Laura
-
Featured
Author Profile
Subscribe
Feed for nGenera Community:
Public
Secure
Why subscribe? What is RSS?