Introduction

Product Overview

Installation & Use

Support & Troubleshooting

Links

 

 


updated: 6/17/98


 

 

 

Related Topic

 

Common Problems Setting Up Folder Privileges


[Advanced]

Volumes are grayed out in the Chooser

When volumes are grayed out in the Chooser, it means that the user does not have any privileges to that volume. You must give your users a minimum of "Read Only" access to any share point if you want them to be able to log in.


"Guest" is grayed out in the Chooser

If the "Guest" option is grayed out in the Chooser, you have not enabled user "Guest" to log in. Double-click on user "Guest" in the Users & Groups list to enable login. And don't forget to give "Everyone," which will include user "Guest," at least read-only access to share points and other folders along the path where information for "Guests" will be stored.


Creating Drop Boxes

Drop boxes are folders that users can drop files and folders into, but they access the files in the folder. A good example of a use for drop box would be a folder that students could drop their homework assignments in.

Drop boxes have the following privileges and requirements:

  • Read &Write privileges for the owner --the person for whom items are being dropped off.

  • "Write Only" privileges for "Everyone."

  • The drop box must be within another folder to which everyone has at least read-only access (so that they can get to the drop box).

  • A drop box cannot be a share point. No one would be able to mount the volume, with "write only" privileges.


New folders not accessible to others in a group

A common problem is that an administrator will set up a folder making an entire group the owner, so that the group can share the information within that folder. The problem with this is that, whenever new folders are created within the folder, no one else in the group will be able to access it.

For example, here's the WRONG way to set up privileges for a group: when an individual creates a folder within this folder, the privileges will default to the owner (the individual who created the folder) having all privileges, and no one else will have access.

 

 

Here's the RIGHT way to set up privileges. The owner can be any individual or an administrator. Enter the Engineering Group in the User/Group field, so that these privileges will be adopted by any new folder created within.

 

 

 

 

 

 

 


Old-Style vs. New-Style access privileges

Since Appleshare IP 5.0, folder access options are "read", "read/write" "write only" and "none". Prior to that, access privileges were described as "See Folder," "See Files," and "Make Changes". In fact, with Mac OS 7.6 and earlier, the older-style options are what users see at their workstations when setting up privileges for folders on the server.

In short, the privileges will translate to the closest counterpart, with the highest scurity. The table below shows some examples of the privileges set from a client using old-style privileges will translate to the newer-style privileges on the server.

As selected on workstation: Translated on Server to: Explanation:
"See Folders, See Files, Make Changes "Read & Write"
"See Folders, See Files" "Read only"
"See Folders" only "None" Allowing "Read" access would allow the user to see files, which is not what was intended, so "None" is the safest alternative.
"See Files" only "None" Allowing "Read" access would allow the user to see folders, which is not what was intended, so "None" is the safest alternative.
"Make Changes" only "Write only"