Design Folder and Permission Groups Structure

WF Permissions Groups

Name	Membership	Contains Groups
Ed Web WF Users	All authors of WF site	ED Wev WF Coordinators,ED Web WF Admin,ED Web WF Dreamweaver,ED Web WF Frontpage, Ed Webs WF Designer,Ed Webs WF Cool Site,Ed Webs WF Copy Editor
ED Web WF Coordinators	All members of Webmaster Forum Coordinating Group
ED Web WF Admin	Administrators
ED Web WF Dreamweaver	Authors of Dreamweaver interest group
ED Web WF Frontpage	Authors of Frontpage interest group
Ed Webs WF Copy Editor	Copy editors

WF site folder structure

folder	description	read permissions	write permissions
/	site root folder	Ed Webs WF Users	Ed Webs WF Admin, Ed Webs WF Coordinators
/library	css, javascript, etc	Ed Webs WF Users
/images	site wide images	Ed Webs WF Users
/membership	content on webmaster membership	Ed Webs WF Users
/listserve	content on listserve	Ed Webs WF Users
/brownbags	content on brownbag series	Ed Webs WF Users
/coolsites	content on cool sites awards	Ed Webs WF Users
/forum	content on annual webmaster forum conference	Ed Webs WF Users
/dreamweaver	content on dreamweaver intereset group	Ed Webs WF Users	Ed Webs WF Dreamweaver
/frontpage	content on frontpage intereset group	Ed Webs WF Users	Ed Webs WF Frontpage
/templates	Dreamweaver templates folder	Ed Webs WF Users
/_mm	contribute and dreamweaver configuration	Ed Webs WF Users
/_baks	backup/rollback files (may be present within all folders on site)	Ed Webs WF Users
/_notes	notes files  (may be present within all folders on site)	Ed Webs WF Users

 

Consider the following in folder/permissions structure

• Contribute roles will not allow limiting editing to specific files within a folder.
• Contribute roles are overridden by file system permissions. 
• Contribute authors must have read access to the entire site
• Contribute does not let you overlap connection paths.  Two contribute editable sites cannot share the same folder. This is known as "overlapped connection paths"
  • The following example shows overlapped connection paths:
    • connection1: www.mysite.com/intranet/
    • connection2: www.mysite.com/intranet/marketing
      
  • In the following example, the paths do not overlap:
    • connection1: www.mysite.com/intranet/marketing
    • connection2: www.mysite.com/intranet/finance

Whooa

Everyone using contribute will have a connection key with an associated connection.  The connection encompasses a protocal, path to edit the web site, and a user role.  We will talk about connection keys more later.  The important thing to note about connection keys when setting up folders is that when a Contribute user first tries a connection key, Contribute writes a temporary file to the server in the users root folder for the connection.  It then tests if it can get it over http, and deletes it.   It does this to test if the URL for the site maps to the file, ftp, etc path and to make sure the user has write permissions to their folder. For this reason, the user must have write and delete permissions to the root folder of the sites they can edit.  Thus,

• This makes it useful to have few or no files in the root folder of the site
• If there are files in the root folder of the site, explicitly deny edit and delete to all but administrators and specific groups that can edit these files.
• Give the following rights to users who need a connection key that points to the root of the site, but are not admins: create and delete files within the root folder, can't create subfolders.  This will allow Contribute to create and delete the temporary file without giving the user the ability to work in the root directory.