Hi Jon, The UI does not rely on logged in users being able to see other users' contacts, memberships and content. However, the feeds that deliver this information are currently not access controlled, which is why they need to be tied to the overall user account permissions. At this point, it seems necessary to make these feeds (at least memberships, and courses more specifically) access controlled during the upcoming architectural sprint, so it is at least possible for people to opt out of this behavior.
Hope that helps, Nicolaas On 17 Apr 2012, at 22:03, Jon Hays wrote: > Nico, > > Thanks for clarifying. Does the UI rely on logged in users being > able to see other users' Contacts, Memberships, and Libraries? > Currently, permissions on those parts of the personal space seem to > be tied to basic information. This would be problem for us because > course memberships are not something that can be shared widely. Is > there any reason Memberships, Contacts, & Libraries can't be treated > like the non-basic information parts of the profile? > > It would also be nice to expand the "Can be seen by" options to > include the people who are in groups with me. > > Jon Hays > 510-672-5493 > CalCentral Team > Educational Technology Services > University of California, Berkeley > > > On 4/17/12 4:09 AM, Nicolaas Matthijs wrote: >> Hi everyone, >> >> Sorry for the late response on this. >> >> It is correct to say that profile area privacy controls and global >> user account privacy settings are separate capabilities. In the >> current system, the user's basic information lives on the >> authorizable, the other profile areas live under the user's home >> node. >> If we wanted to apply the area privacy options to a user's basic >> information, we'd need to set ACLs on the authorizable. >> >> This in itself is possible, but the real problems comes when trying >> to >> make a user account fully private. Currently, the UI relies on logged >> in users being able to see other users, so it would cause certain >> features in the UI to break. For example, you wouldn't be able to >> share content with a private user or add a private user to a group, >> as >> that user wouldn't show up in any searches, type-aheads or lists, >> which seems especially problematic when running a course through OAE. >> I think the URG will try to come up with a solution for this in the >> next few weeks. >> >> Coming back to Madan's original question, anonymous users will never >> be able to see the name and profile picture of users that have set >> their account to "Logged in only". They will either not show up at >> all >> (search, participants list, etc.) or a fake non-clickable name will >> be >> used (comments). >> >> Hope that helps, >> Nicolaas >> >> >> On 12 Apr 2012, at 19:42, Nate Angell wrote: >> >>> My understanding is that the profile area privacy controls (on each >>> profile area except Basic Info) and the global user account privacy >>> settings are actually separate capabilities. >>> >>> I believe it's possible to enable profile privacy controls on any >>> area, including basic info via config in config.js. >>> >>> = nate >>> >>> On Apr 12, 2012, at 11:55 AM, Clay Fenlason<[email protected] >>>> wrote: >>>> Based on the testing with Nate's account, I think the UX may just >>>> be >>>> misleading here. >>>> >>>> It's true that there is no apparent way to hide the 'Basic Info' >>>> area >>>> of the profile directly, through the permissions settings that each >>>> of >>>> the other profile areas have. >>>> >>>> However, instead of trying to set visibility on each profile area >>>> in >>>> the dashboard separately, if you change the 'Privacy Settings' >>>> under >>>> 'My Account,' AFAICT your name/profile, etc. just never show up in >>>> public contexts. So you really can disappear to everyone who isn't >>>> logged in. >>>> >>>> ~Clay >>>> >>>> On Thu, Apr 12, 2012 at 1:43 PM, Madan Kumar Dorairaj<[email protected] >>>>> wrote: >>>>> Nate, yes, that is what I was hoping to see, but it is not there. >>>>> >>>>> Those permissions are available for About Me, Publications, but >>>>> not for >>>>> Basic Info. The Parent folder - My Profile do not have any >>>>> permissions >>>>> associated to that either. >>>>> >>>>> Regards, >>>>> Madan >>>> _______________________________________________ >>>> oae-dev mailing list >>>> [email protected] >>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >>> _______________________________________________ >>> oae-dev mailing list >>> [email protected] >>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> _______________________________________________ >> oae-dev mailing list >> [email protected] >> http://collab.sakaiproject.org/mailman/listinfo/oae-dev _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
