Hi Neil.
I don't run multiple users on my computer so I'm not an expert on
this. You might find that OS X doesn't provide quite as much as the
functionality as you'd like. If this is the case I'm sure you could
find some software to fill the gap from versiontracker by typing a
search for permissions.
I've tried to answer your questions below.
1) More folders like the shared folder that everyone can access and
read/write to so that besides the overall shared I can have shared
category
folders.
I believe all users can access folders stored directly on the hard
drive and on all non-user & non-system folders for that matter. If
you want folders in a specific location that would normally be
inaccessible you could make multiple aliases of a folder stored
directly on the hard drive.
2) Folders fully available to some users but not others (as we did
in the
old days of file sharing where we created groups of users and gave
access to
the relevant groups.) OSX seems to work on this principle but how
do I set
up a group comprising, say, 3 users so that I can set folder access
to allow
any of these three users full access but not the other (say, two)
so not
just give access to "Others".
You can configure folder permissions by using get info on a folder
from the File menu in the finder. You will probably have to click on
the triangle tabs for "Ownership and Permissions" and "Details". I'm
not sure whether you can assign varying permissions to different
users in this way but you can certainly have specific permissions for
one user different to all other users.
3) I also seem to remember being able to set folder privileges to
allow
certain users to be able to read/write files in the folder but not
be able
to move/rename or delete the actual folder. How does one go about
this in
OSX.
I'm not sure if this is possible using get info. You can certainly
configure users to only be able to read items in the folder but I
don't think you can allow read and write without giving the user the
option to delete the folder or the contents.
Hope this helps
Ruben A. Franke
