mahara-contributors team mailing list archive

[Kristina Hoeppner <1212644@xxxxxxxxxxxxxxxxxx>]

Hello Gordon,

I see two streams here:

1. Have "groups" (or let's call them cohorts for easier distinction in
terminology) like "Friends" who you can add as a bunch of people to give
them access to view pages and collections. That would take care of your
requirement "for disseminating information resources meant to be shared
with student year cohorts. Admin users are assigned who can upload
content, create pages, etc and if users wanted to participate using
forums the group could have request membership if it was necessary to
restrict access."

These cohorts would be people who then only can view pages based on
being in that cohort, but they could not participate in a group
discussion or upload files because they are actually not members of the
group.

2. Allow cohorts to be enrolled in a group so that they can be full-
fledged members of a group and participate in forum discussions for
example.

As far as your other questions / comments go:

If you do not want your group members to get notified when someone
shared a page with the group, you can turn off "Shared page
notifications" in the group edit screen.

As far as "if a group A page is shared with group B, do the users in
group B have rights to post to forums in group A?" goes: No. That is not
possible at the moment unless you make all group B members also members
of group A. And yes, this would tie in with the other wishlist item.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1212644

Title:
  Share group with other groups - not just pages

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Enhancement request.
  I've recently developed a number of resource groups with multiple pages/collections to be shared with staff and students across several years and programmes. Auto enrol all users isn't an option as we need to restrict access to the content and our Mahara is accessed university wide. Adding staff and students to year cohorts and sharing the resource groups with those would allow the necessary level of access filtering, but in order to share the content of the resource groups with the 'cohort group' you need to share access at the page or collection level rather than at group level. If it was possible to 'share with group' at the group (rather than page) level and effectively give any member of group A the right to access the content in group B that would make the process much easier - making sharing 1 click instead of 6 to 10 page/collection shares per group.
  Regards, Gordon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1212644/+subscriptions