Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Site-wide groups.

Obsolete:Site-wide groups

From MoodleDocs
Revision as of 10:56, 21 January 2009 by Helen Foster (talk | contribs) (groups category)

Requirements

Please add concise descriptions of why you need site-wide groups here. There are quite a few different use cases around.

  1. We want to put a whole class of people into a group so that we can easily enrol and unenrol them together from numerous courses. (If people leave that group, should they be unenrolled from the courses?)
  2. We want to present a different theme to each group (with a common login page only). Useful for cases where one site is used by different companies. When combining this with the use of My Moodle then everyone sees just what they want to see, with customised branding etc. Is also useful for giving students a different view from teachers in more places.
  3. What else?

Terms

It might be confusing to think of these as part of the groups systems we have already .... perhaps it's a different complementary system?


Possible plans for discussion

Design 1

  1. Let's call them cohorts and keep this separate from existing groups system.
  2. Admin can use an admin interface to define cohorts (with name, icon, description, forced theme etc)
  3. Admin can use the admin interface to add users to one or more cohorts (one person could be in Students, First Year Students, and CM3004)
  4. Cohorts are visible in role assignment pages just like people, you can enrol a cohort in a course all with a particular role. A checkbox would allow you to choose whether cohort changes are mirrored as changed enrolments in future.
  5. The cohort theme beats site theme, but is beaten by user or course themes.

We could do more, but is this simple idea enough for 99% of requirements?

Design 2?

See also

The main tracker bug is MDL-11826