Be careful with using directories under your current WORK location. This location is transient and will vanish completely once the SAS process shuts down (most often, the workspace server). And SAS usually restricts access to the root work directory for a given process to the user of the process, so others can't look there.   So, the first thing you have to do is create a suitable directory in a location in the server's filesystem where all users you want to include have at least read/execute permissions. Then create a library reference that is somehow "permanent". This may be in the SAS metadata, or in  the autoexec_usermods.sas file of your workspace server, or in the autoexec_usermods.sas of your SASApp. You can create the library defintion in the SAS Enterprise Guide Explorer. If you want to share files other than SAS datasets in the Files section of the EG server list, this will become trickier. By default, Files (in EG) is located in the home directory of the user (on the UNIX level, you find this in the environment variable $HOME). This is an attribute of the workspace server definition in the metadata, and I would not change that for several reasons. My workaround for this is that I create a symbolic link in all user's home directories that points to the shared location. They can then see the files in Files. Keep in mind that in the code, access to locations is only restricted by file system permissions, so basically users can "see" the whole system, starting at the root. ... View more