." ." Copyright (c) 1991 by Sun Microsystems, Inc. ." ." @(#)access_control.4 1.5 92/01/31 SMI ." .TH ACCESS_CONTROL 4 "01 December 1992" .SH NAME access_control \- TeamWare access control file .SH SYNOPSIS .B Codemgr_wsdata/access_control .LP .SH DESCRIPTION The \fBaccess_control\fP file contains information about which users are allowed to run TeamWare commands for a given a workspace. TeamWare was formerly known as CodeManager. Each workspace has an access control file located in the .B Codemgr_wsdata metadata directory. When workspaces are created, a default access control file is also created. .LP The following are the predefined access control operations and their meaning: .sp .nf .TP 30 bringover-from Access to use this workspace as the parent during a bringover operation .TP bringover-to Access to use this workspace as the child during a bringover operation .TP putback-from Access to use this workspace as the child during a putback operation .TP putback-to Access to use this workspace as the parent during a putback operation .TP undo Access to undo a bringover or putback operation in this workspace .TP workspace-delete Access to delete this workspace via the \fBworkspace delete\fP command .TP workspace-move Access to move this workspace via the \fBworkspace move\fP command .TP workspace-reparent Access to reparent this workspace via the \fBworkspace reparent\fP command .TP workspace-reparent-to Access to reparent a child to this workspace via the \fBworkspace reparent\fP command .fi .LP User entries are processed from left to right. If a user's name appears in the user list, or in a netgroup in the list, the user is granted access for that operation. A user's name or netgroup name beginning with "-" is denied access for that operation. A list that consists of only "-" denies everyone access for that operation. If there are no users listed, then all users are granted access. .LP Example file: .sp .nf .in +5 .ta 2.5i bringover-from @engineering bringover-to @corp:-user1:@engineering putback-from \- putback-to undo workspace-delete workspace-move workspace-reparent workspace-reparent_to .in -5 .fi .LP .LP In this example, the first line specifies that only users in netgroup \fBengineering\fP can execute bringovers from the workspace. The second line specifies that anyone in netgroup \fBcorp\fP can execute a bringover into the workspace. Also anyone in the netgroup \fBengineering\fP can do a bringover except \fBuser1\fP unless he is in netgroup \fBcorp\fP. The third line says that no one can do a putback from the workspace. All users have access to the remainder of the commands. .LP The default access control file is (where \fIcreator\fP is the login name of the user who created the workspace): .sp .in +5 .nf .ta 2.5i bringover-from bringover-to putback-from putback-to undo workspace-delete \fIcreator\fP workspace-move \fIcreator\fP workspace-reparent \fIcreator\fP workspace-reparent_to \fIcreator\fP .fi .in -5 .SH "SEE ALSO" .IR "Sun WorkShop TeamWare User's Guide" .LP .sp .nf bringover(1), codemgr(1), def.dir.flp(1), dmake(1), freezept(1), putback(1), rcs2ws(1), resolve(1), teamware(1), twbuild(1), twfreeze(1), twmerge(1), twversion(1), workspace(1), ws_undo(1), args(4), children(4), conflicts(4), description(4), freezepointfile(4), history(4), locks(4), nametable(4), notification(4), parent(4), putback.cmt(4) .LP