...
Working
...
Plan for a shared folder hierarchy on a suitable server
Server: a pc- and mac-compatible file-sharing environment, with group and individual permissions. It needs to not be AFS, as security accidents are relatively easy there and the impact is usually to inadvertently share sensitive data files to the world. The existing sparkler server, a windows server that exports to Macs and PC's natively, has evidently met the security test since it has all of IS&T's confidential information on it now.
Filespace: assuming we a server like sparkler, we would have a directory on that server that mounts as a drive letter on Windows and a desktop folder on the Mac. Let's call it "CSS-managers" We'd have essentially unlimited room inside the folder to store what we will, and the ability to carve off sections of it to have more restrictive permissions as needed.
Access: the set of individuals who can attach the CSS-managers folder are on the list of people who would be invited to our Quarterly Offsites -- Director, Managers, Team Leaders, FBC, HQ Support.
Structure: We need a nested hierarchy of progressively more restricted folders, in order to preserve the security of salary data. Team Leaders need to be able to see the salary data for their people, but not for those of any other team leader. Managers need to be able to see all their TLs data, but may need to have data over their own that the TLs cannot see. The FBC and the Director need to be able to see all.
The overall design is intended to provide the most public access to group documents at the outermost level. Documents that show more specific detail about a single manager's area would be in a subfolder dedicated to that area. Within that manager-specific folder would be more private areas for data that should be visible only to the director, manager, and a specific team leader. Finally there is a most private area accessible only to the director and manager. (The FBC is able to see into all areas and is understood to hold a position of trust.)
Overall then, we'd have this scheme:
folder | likely contents |
|
|---|---|---|
css-managers/ |
|
|
|
|
|
|
|
|
|
|
|
The precise file structure might look something like this:
Folder | Subfolder | (more folders)" |
| Likely Contents | Permissions |
|
|---|---|---|---|---|---|---|
css-managers/ |
|
|
|
|
|
|
| ditr/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| team/ * |
|
| chuckk, pepsikid, ndpope, jfw, abdenna |
|
|
| mgr/ |
|
| ndpope, jfw, abdenna |
|
| help/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| callcenter/ |
|
| fbaars, goguen, othomas, jfw, abdenna |
|
|
| n42service/ |
|
| legand, goguen, othomas, jfw, abdenna |
|
|
| mgr/ |
|
| goguen, othomas, jfw, abdenna |
|
| dcad/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| mgr/ |
|
| jlreed, jfw, abdenna |
|
| tcp/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| pubs/ |
|
| cwood, jfw, abdenna |
|
|
| training/ |
|
| kkibbee, jfw, abdenna |
|
|
| atic/ |
|
| maryz, jfw, abdenna |
|
|
| mgr/ |
|
| jfw, abdenna |
|
| security/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| mgr/ |
|
| tjm, jfw, abdenna |
|
| hq/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| mgr/ |
|
| jfw, abdenna |
|
| homepage/ |
|
|
| css-managers, css-tl, css-hq |
|
|
| mgr/ |
|
| lisanti, jfw, abdenna |
|
* NOTE: the folder names are suggestions only; managers should have naming control within their folders within reason. We suggest not using individual names instead of teams or roles.