[Using Sakai] Permission to make Resource Public

[Jim Mezzanotte]

Hi Louis,

I've done some additional testing, and I don't see any unintended side
effects for granting the "realm.upd" permission. This permission is
typically enabled when the "site.upd" permission is also enabled. The
"site.upd" permission (enabled for site owners/instructors) gives
users a large set of capabilities, and permissions such as "realm.upd"
are the only way to provide some granularity.

So even if you have "site.upd" enabled, you'll need "realm.upd" to
change user permissions via tool UI. And if you only enable
"realm.upd" (and not also "site.upd"), you'll have no access to
permissions in tools--so it's safe to enable "realm.upd" for students.
Still, I would recommend first enabling "realm.upd" in a test site, so
you can confirm no additional abilities for students.

By the way, there is another approach, if you want to edit the realm
of a particular site: you can edit the realm for a specific Resources
folder, and enable "realm.upd" only in that realm. Then, students will
only be able to change an item to public access if it's in that
folder.

Lastly, there is one potential downside to enabling "edit any
resource" and/or "edit own resources" permission, if you do not also
enable the "read hidden resources" permission: a student could set an
item to be hidden--and then no longer see the item.

Best,
Jim Mezzanotte
rSmart

On Thu, Jan 31, 2013 at 12:45 PM, Algaze, Louis Contractor, eDataTech
<ljalgaze at nps.edu> wrote:
> Jim,
>
> Thank you for your reply.
>
> Does adding this permission for the student role in the realms tool give
> any additional, possibly unwanted, permissions in the site of is this all
> the student will be able to change.
>
>  Thank you,
>
> Louis
>
> On 1/31/13 9:24 AM, "Jim Mezzanotte" <jmezzanotte at rsmart.com> wrote:
>
>>Hi Louis,
>>
>>This behavior is actually related to an additional permission that you
>>can only access via the Realms tool in the Admin workspace (and not
>>via the Resources tool UI):
>>
>>realm.upd
>>
>>With this permission enabled, students can set a Resources item to public.
>>
>>When you change an item to public access, a separate group realm gets
>>created for that item. If you then change an item's access from public
>>back to "this site only" or a section/group, this group realm is
>>deleted. So, you may want to consider also enabling the following
>>permission:
>>
>>realm.del
>>
>>If you only enable "realm.upd" for students, and not also "realm.del,"
>>students will be able to change an item's access to public, but they
>>will not be able to change access back to "site only" or a
>>section/group.
>>
>>>From what I can tell, enabling one or both of these permissions for
>>students shouldn't have an impact on any other behavior (though I
>>would still recommend changing permissions first in a test site before
>>making global changes). These permissions are tied to others (such as
>>"site.upd") that students would typically never have.
>>
>>I agree that a design change would be good here, if possible--the
>>ideal scenario would be that users don't see the "public" setting at
>>all if they don't have these additional permissions.
>>
>>Best,
>>Jim Mezzanotte
>>rSmart
>>
>>
>>On Wed, Jan 30, 2013 at 3:00 PM,
>><sakai-user-request at collab.sakaiproject.org> wrote:
>>> Send sakai-user mailing list submissions to
>>>         sakai-user at collab.sakaiproject.org
>>>
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>         http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>>> or, via email, send a message with subject or body 'help' to
>>>         sakai-user-request at collab.sakaiproject.org
>>>
>>> You can reach the person managing the list at
>>>         sakai-user-owner at collab.sakaiproject.org
>>>
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of sakai-user digest..."
>>>
>>>
>>> Today's Topics:
>>>
>>>    1. Permission to make Resource Public
>>>       (Algaze, Louis Contractor, eDataTech)
>>>
>>>
>>> ----------------------------------------------------------------------
>>>
>>> Message: 1
>>> Date: Tue, 29 Jan 2013 21:58:50 +0000
>>> From: "Algaze, Louis Contractor, eDataTech" <ljalgaze at nps.edu>
>>> Subject: [Using Sakai] Permission to make Resource Public
>>> To: Sakai Server <sakai-user at collab.sakaiproject.org>
>>> Message-ID: <CD2D8619.1E3E9%ljalgaze at nps.edu>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hello,
>>>
>>> We are using rSmart's Sakai version 2.8.4 and I have a permissions
>>>question about making Resources Public with which I'm hoping someone
>>>could assist.
>>>
>>> It seems as if a student, given the Edit Own and/or Edit Any Resource
>>>permission can access the Edit Details page of that resource, but if
>>>that person chooses the option to make the resource Public, no changes
>>>are made.  Is this a bug or by design?
>>>
>>> If by design it would probably be clearer if they did not see the
>>>option to make the resource public.
>>>
>>> Thank you,
>>>
>>> Louis
>>>
>>> -------------- next part --------------
>>> An HTML attachment was scrubbed...
>>> URL:
>>>http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20130129/
>>>dfd61214/attachment-0001.html
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> sakai-user mailing list
>>> sakai-user at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>>>
>>>
>>> End of sakai-user Digest, Vol 47, Issue 15
>>> ******************************************
>>_______________________________________________
>>sakai-user mailing list
>>sakai-user at collab.sakaiproject.org
>>http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>>
>>TO UNSUBSCRIBE: send email to
>>sakai-user-unsubscribe at collab.sakaiproject.org with a subject of
>>"unsubscribe"
>