[Building Sakai] Displaying Course Tool only to Administrators in Sakai

[Steve Swinsburg]

There is a test, but it needs to be done in the tool code so the tool will still show in the list. If you want to hide a tool then it needs to hook into a permission, AFAIK. This raises an interesting point, what role does an admin user have in a site of which they are not a member? 

cheers,
s

On 10/04/2011, at 10:29 AM, Nate Angell wrote:

> I thought the issue is that what identifies an admin is membership in the admin workspace, not a role. Seems like there is a test for that, or maybe it is easier to hook it to some other admin privilege as suggested earlier. 
> 
> - Nate
> 
> On Apr 9, 2011, at 4:22 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> 
>> I think the issue here might be that roles can be customised per site, and many tools actually allow this customisation to occur within the site, so role_1 in site_a might not necessarily be the same as role_2 in site_b.
>> 
>> Maybe we need some more permissions that identify admin people.
>> 
>> cheers,
>> Steve
>> 
>> 
>> On 09/04/2011, at 5:17 AM, Zhen Qian wrote:
>> 
>>> Seth:
>>> 
>>> I think the transition from role.required to function.required is actually documented inside SAK-4120 that Kara referred to: 
>>> 
>>> Nuno originally proposed the ticket for "roles.allow" and "roles.deny" configuration. However, Chuck eventually implemented it based on permission: 
>>> 
>>> "This solution is different than proposed in the patches because it is based on Sakai security functions rather than roles. The patches also proposed an allow/deny pattern. The use of functions instead of roles aligns much better with the Sakai security model and does not require the allow/deny."
>>> 
>>> Thanks,
>>> - Zhen
>>> 
>>> On Fri, Apr 8, 2011 at 2:23 PM, Seth Theriault <slt at columbia.edu> wrote:
>>> Zhen Qian wrote:
>>> 
>>> Maybe besides function, we can request a feature to restrict tool display based on roles, e.g. role.require?
>>> 
>>> I distinctly remember this coming up a few years back. It's a hazy memory, but I think that approach may have been abandoned in favor on the current "functions.require" one.
>>> 
>>> Of course, I haven't found  the corresponding Jira. Yet.
>>> 
>>> Seth
>>> 
>>> 
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>> 
>>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110410/18eab554/attachment.html