You can set the user to be an administrator or choose the permissions individually. + If you select "Administrator", all of the other options will be automatically checked. + The management of users remains a privilege of an administrator.
+ +Administrator
+Create new files and directories
+Edit, rename and delete files or directories.
+Execute commands
+ +A space separated list with the available commands for this user. Example: git svn hg.
+ + + +Here you can define a set of allow and disallow rules for this specific user. The blocked files won't + show up in the listings and they won't be accessible to the user. We support regex and paths relative to + the user's scope.
+ +Each rule goes in one different line and must start with the keyword allow or disallow.
+ Then you should write regex if you are using a regular expression and then the expression or the path.
Examples
+ +disallow regex \\/\\..+ - prevents the access to any dot file (such as .git, .gitignore) in every folder.disallow /Caddyfile - blocks the access to the file named Caddyfile on the root of the scopeCostum user CSS
+ + +