Restrictions docs needed

The signup restriction functionality may need some work. It is in place currently to support the concept of group signups (signing up more than one person for a shift). It works as follows:

On the event node type, a multi-select cck text field is created, with, for example, the following allowed values, labeling this field something like 'Signup restrictions':

field_restriction_example_1|Number of people with blue shoes
field_restriction_example_2|Number of people with green hair

then, on the signup node type, add numeric fields with machine names identical to the key in the above allowed values:

field_restriction_example_1 (and make a sensible lable, like "Number of people with blue shoes").
field_restriction_example_2 (label of 'Number of people with green hair').

Now, when an administrator or privileged user goes to create an event, they will be able to restrict signups to people with green hair by checking the checkbox. What happens when they do this is that on signup if the attendee enters a value other than 0 into the numeric people with green hair field, the cck signup restriction will throw a form error.

For a working example, take a look at the shift_restriction feature here.

For that use-case, you can use the CCK Signup Group module, and not worry about the Restrictions module. The group signup module takes into account the group capacity during signup validation.

Also, regarding the status, there is nothing in place at this time that would automatically change the status, although there is code in place to prevent signups to past events.

Closing for now. Please re-open if you have further questions around this.