1 03/06/85  forum_add_participant, fapt
 2 
 3 Syntax as a command:  fapt meeting_name Person_id {-control_args}
 4 
 5 
 6 Function:  makes the person identified by Person_id eligible to attend
 7 the meeting_name meeting.  You can use this request if you have either
 8 modify permision on the containing directory or chairman access to the
 9 meeting.
10 
11 
12 Arguments:
13 meeting_name
14    is the pathname or entryname of the meeting to be adjusted.
15    Pathnames contain greater-than (>) or less-than (<) characters.  If
16    a pathname is specified, it identifies the meeting to be adjusted.
17    Otherwise, fapt searches for the meeting_name by using the forum
18    search list.
19 Person_id
20    is the Person_id of the participant to be added.
21 
22 
23 Control arguments:
24 -chairman, -cm
25    gives chairman access to the added participant.  This control
26    argument is not valid for meetings created with pre-MR11 software.
27 -read_only, -ro
28    allows the added participant to read transactions but not enter
29    them.
30 
31 
32 Notes:  The -read_only and -chairman control arguments cannot both be
33 specified.
34 
35 To change the access of a participant to read only, use the fapt
36 command with the -read_only control argument to add the participant
37 again.  This will change the original access of the participant to read
38 only.
39 
40 The  meeting  chairman  can  use  the convert_forum command to convert
41 meetings  created  with pre-MR11 software to current version meetings.
42 The  old version meeting is left untouched and should be deleted using
43 the  forum_delete  command.   To  avoid  deleting  the current version
44 meeting,  you  must  include  the  ".control" suffix at the end of the
45 meeting_name.