{"id":564,"date":"2018-10-11T11:41:03","date_gmt":"2018-10-11T10:41:03","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/csf3\/?page_id=564"},"modified":"2025-11-25T17:02:41","modified_gmt":"2025-11-25T17:02:41","slug":"file-permissions","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/filesystems\/file-permissions\/","title":{"rendered":"Directory Permissions and File Sharing"},"content":{"rendered":"<p>If you are unfamiliar with Linux file permissions you should consider reading sections 5.1 and 5.2 of <a href=\"https:\/\/info-ee.surrey.ac.uk\/Teaching\/Unix\/unix5.html\" target=\"_blank\" rel=\"noopener\">this Intro to Linux course<\/a> (from the University of Surrey) first.<\/p>\n<h2>Home Directory Permissions<\/h2>\n<p>The default permissions on your <em>home<\/em> directory on the CSF allow access to you (the user) only. The directory is private to you.<\/p>\n<p>Every user on the CSF also belongs to a <em>unix group<\/em> on the system. This usually represents your research group, but could represent your school or faculty if your access to the CSF is the result of a school or faculty contribution. For example, users in the Department of MACE are members of the <code>mace01<\/code> <em>unix group<\/em> on the CSF.<\/p>\n<p>It is possible to allow other users in your <em>unix group<\/em> to access your <em>home<\/em> directory (e.g., to share files), but this is <em>not<\/em> the default.<\/p>\n<p>You can run the commands in <code><strong>bold<\/strong><\/code> at the login node prompt below. For example:<\/p>\n<pre>[<em>username<\/em>@login1[csf3] ~]$ <strong>ls -ld $HOME<\/strong>\r\ndrwx------ 37 <em>username<\/em> zz01 4096 Aug 15 09:59 \/mnt\/iusers01\/zz01\/<em>username<\/em>\r\n||_||_||_|              |\r\n| |  |  |               +--- Your <em>unix group<\/em> (based on the CSF contribution you are assigned to)\r\n| |  |  |\r\n| |  |  +-- (---) indicates <em>others<\/em> (all users) CANNOT access your HOME dir\r\n| |  +----- (---) indicates people in your <em>group<\/em> (zz01) CANNOT access your HOME dir\r\n| +-------- (rwx) indicates <em>user<\/em> (you) CAN <strong>r<\/strong>ead, <strong>w<\/strong>rite and e<strong>x<\/strong>ecute (enter) your home directory.\r\n|\r\n+----- <strong>d<\/strong>irectory (will be a dash <strong>-<\/strong> if looking at a file's properties)\r\n\r\n<\/pre>\n<p>If you want colleagues in your group to be able to read and copy some of your files, you can set <em>group<\/em> permissions with the <code>chmod<\/code> command as follows:<\/p>\n<pre>[username@login2[csf3] ~]$ <strong>chmod g+rx $HOME<\/strong>\r\n                                  #\r\n                                  # This adds <strong>g<\/strong>roup <strong>r<\/strong>ead and e<strong>x<\/strong>ecute\r\n                                  # permissions to your home directory.   \r\n<\/pre>\n<p>Let&#8217;s check how it looks now:<\/p>\n<pre>[username@login2[csf3] ~]$ <strong>ls -ld $HOME<\/strong>\r\ndrwxr-x--- 37 username zz01 4096 Aug 15 09:59 \/mnt\/iusers01\/zz01\/<em>username<\/em>\r\n    |_|\r\n     |\r\n     +---- Now members of your <em>group<\/em> (zz01) CAN <strong>r<\/strong>ead and e<strong>x<\/strong>ecute (enter) your\r\n           HOME dir but notice they CANNOT <strong>w<\/strong>rite to it.\r\n\r\n<\/pre>\n<p>The default file permissions\u00a0<strong>within<\/strong> home directories should be sufficient to now allow people from <strong>your group<\/strong> to read the contents of the files and to copy them to their own home directory. If opening the permissions to <em>all members<\/em> your group is too wide-open, then please let us know who you would like to have access, and we will advise further.<\/p>\n<div class=\"warning\">\nIt is highly recommended that you\u00a0<strong>never<\/strong> give anyone else\u00a0<em>write<\/em> (<code>w<\/code>) permission to your directory or files as this allows them to modify or delete them.<\/p>\n<p>Please note that directory permissions override file permissions.<\/p>\n<p>Also be aware that groups can be very large and contain a lot of people with whom you do not directly work.<\/p>\n<p>If you want your colleagues to be able to edit \/ write new \/ delete files in your area please fill in our <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/hpc-help\">help form<\/a> to request advice.\n<\/div>\n<h2>Scratch Directory Permissions<\/h2>\n<p>Default permissions on your <em>scratch<\/em> directory are the same as on your <em>home<\/em> directory &#8211; your <em>scratch<\/em> directory is private to you. As with the <em>home<\/em> directory, it is possible to change the permissions on your scratch directory to allow your colleagues to access your files.<\/p>\n<p>NOTE: When working with scratch permissions you must use the direct path to your scratch directory:<\/p>\n<pre>\/scratch\/<em>username<\/em>\r\n           #\r\n           # Use your own username here\r\n<\/pre>\n<p>NOT the symnlink\/shortcut you have in your <em>home<\/em> directory. Thus the command to check your <em>scratch<\/em> permissions would be:<\/p>\n<pre>ls -ld \/scratch\/<em>username<\/em>\r\n<\/pre>\n<p>If you need to change your scratch permissions then the procedure is the same as for <em>home<\/em> &#8211; see above.<\/p>\n<div class=\"warning\">\n<strong>Remember:<\/strong> the <em>scratch<\/em> filesystem IS NOT backed up. It is highly recommended that you\u00a0<strong>never<\/strong> give anyone else\u00a0<em>write<\/em> (<code>w<\/code>) permission to your directory or files as this allows them to modify or delete them.<\/p>\n<p>Please note that directory permissions override file permissions.<\/p>\n<p>Also be aware that groups can be very large and contain a lot of people with whom you do not directly work.<\/p>\n<p>If you want your colleagues to be able to edit \/ write new \/ delete files in your area please fill in our <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/hpc-help\">help form<\/a> to request advice.<\/div>\n<h2>Group Research Data Storage<\/h2>\n<p>Some groups have an allocation of Research Data Storage (RDS) on the CSF. This is additional storage that can provide a lot more capacity than your group&#8217;s <em>home<\/em> area &#8211; usually several TB&#8217;s worth of storage. RDS storage is backed-up, just like your <em>home<\/em> directory, and is suitable for long-term storage of important files (e.g., data-sets, results).<\/p>\n<p>For example:<\/p>\n<pre>\/mnt\/<em>fac<\/em>01-rds\/smith-project\/\r\n      #                #\r\n      #                # The directory name usually indicates the PI and project name\r\n      #\r\n      # <em>fac<\/em> is usually a short form of your faculty \r\n<\/pre>\n<p>which usually contains a directory for each person authorised to use the space and sometimes shared directories.<\/p>\n<p>The permission in these areas vary depending on the group in question. The information above will still be applicable in some cases. If you need help organising your group area or the permissions for it please please fill in our <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/hpc-help\">help form<\/a> to request advice\u00a0.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you are unfamiliar with Linux file permissions you should consider reading sections 5.1 and 5.2 of this Intro to Linux course (from the University of Surrey) first. Home Directory Permissions The default permissions on your home directory on the CSF allow access to you (the user) only. The directory is private to you. Every user on the CSF also belongs to a unix group on the system. This usually represents your research group, but.. <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/filesystems\/file-permissions\/\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":94,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-564","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/564","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/comments?post=564"}],"version-history":[{"count":20,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/564\/revisions"}],"predecessor-version":[{"id":11433,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/564\/revisions\/11433"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/94"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/media?parent=564"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}