Currently logged in as wdueber

Edit header "Debate"

The Title (required)

The title is shown in the conference listing. This is a header, so the title should indicate what the conferences inside of it will have in common (i.e., "Project 1", "General Questions", etc.)

The Text Description (optional)

The text description for a header is shown whenever a user looks at the message list for a conference indented underneath this header. You can use it as follows:

If all of the conferences underneath this header will be different, leave it empty. You'll need to set up text descriptions for each individual conference.
If all of the conferences indented underneath this header will be identical (except for the permissions and/or the primary group), you can put the description here and leave the individual conference descriptions blank.
If all of the conferences indented underneath this header will be similar, you might want to put in some introductory text to "set the scene" for the conferences. Again, the advantage to putting it here is that you only have to edit one copy if something needs to be changed or updated.

Permissions

(you may need to create groups if you haven't already, since permissions are set on a group-by-group basis)

Permissions set in a header "carry over" to any conferences (or sub-headers) which are indented underneath it.

The special group EVERYONE contains everyone who is a part of the class. This group is automatically created and maintained by the system.

The special group PRIMARY GROUP grants permissions to whichever group is listed as the "primary group" of an individual conference. If you had the system create a set of conferences for you, one for each selected group, it automatically set the primary group of each of those conferences to the group the conference is named after.

A NOTE ABOUT "Postfirst": Generall, when using the "postfirst" option, instructors like to set only the permissions "Read", "Write", and "Postfirst". If you allow your users to edit, it's possible for them to submit a "dummy" message, read everyone else's messages, and then immediately edit their first message. This gets around the whole point of using "postfirst".

. . Permissions To Add

Group Permissions
carried over
from other headers Read
(R) Write
(W) Edit Own
(Eo) Edit All
(Ea) Post First

EVERYONE -

PRIMARY GROUP -

Group One -

Blue Group -

Choose a Label Set

Much like permissions, labels are "handed down" to any conferences which are indented beneath this header. Again, the reason you would do this is the ability to change the labels used by a whole slew of conferences at once.

If you haven't created a set of labels to be used here, you can create them later and come back here at any time.

Inherited Labels:
[[none]]

Use named category set:

Use the same set as:

Group	Permissions carried over from other headers	Read (R)
.	.	Permissions To Add
EVERYONE	-
PRIMARY GROUP	-
Group One	-
Blue Group	-