Settings and activity
1 result found
-
213 votes
We have two use cases here.
1. Making is super easy to work with clients. Clients can see only Discussion and Tasks which specifically marked as visible to them. Rest is not visible to them
2. Allowing true privacy – concept described by Caroline. Once this mode is enabled users can create private tasks and decide who they want to share it with.
@Caroline – I assume project and project group administrators should be able to see private tasks. Right?
NEW UPDATEProbably we should move Private Tasks and Private Discussions into a separate add-on which is not available by default.
We have requests for private tasks and we have requests for disabling privacy – when a teacher in a school does not want students to create private tasks at all.
I assume functionality similar to Private Discussions we already have in Freedcamp is what you are after.
OLD UPDATE…
An error occurred while saving the comment An error occurred while saving the comment Caroline commented
Hi Igor,
We emailed about this a while back, and you asked me to contribute here, as you thought this was a similar request for features. My coworkers are not co-workers, they are course participants. We use freedcamp to discuss progress, but everyone works on their own creative project. I'd like to use tasks like "homework". Everyone gets a copy, but everyone completes their own individual homework. People don't share their completed homework with me, they do it for themselves, but may like to share it with (selected) others to discuss it.
An error occurred while saving the comment Caroline commented
Hi Igor,
If I understand correctly, if you created this, this would mean that only the admin can control who sees which tasks? In my project, the aim would be for each person to be able to create their own tasks, and be able to keep them private or share them with other people in the project.
Using your client setup, I think this would be possible to make us of with a work around. As an admin, I could create a task per client team, and make each single person into a client team, so they would all be able to keep their task private. It would be confusing though.
I am not a developer and have no idea what would be possible but I was thinking along the lines of, that every person is able to add public info to a task, but also private. That way, they control what they share, with whom. The admin creates the overal structure of tasks, but people can use those tasks both as a way to keep each other in the loop on progress, but also for their own notes on their work in the project. I think this would make sense for teams too. That way, someone in a team could let their coworkers know that a task is completed for example, but keep all the notes about that to themselves, so as not to overwhelm others with unneeded info. That way, they can still keep all their notes about their task in one place. Just a thought!
Caroline supported this idea ·
Re @Igor - In my case, administrators do not need to see other people's private tasks. I could see both possibilities working: for admins not to see private tasks, or for admins to see private tasks but I think users would probably prefer it if admins don't see their private tasks.