Skip to main content
Copyparty uses a flexible permission system with single-letter flags to control user access to volumes.

Permission Flags

Read Permissions

read
Full read access
  • Browse folder contents
  • Download individual files
  • Download folders as zip/tar
  • See filekeys and dirkeys
  • View file metadata and properties
get
Get-only access (no browsing)
  • Download files by direct URL only
  • Cannot see folder contents
  • Cannot download as zip/tar
  • Useful for “hotlink” scenarios
Often combined with filekeys to prevent URL guessing.
upget
Upload-get accessSame as g but uploaders can see their own filekeys.
  • Upload files
  • Receive working direct link after upload
  • Cannot see other users’ uploads
  • Cannot browse folder
html
HTML-only accessSame as g except:
  • Folders return their index.html file
  • Filekeys not required for index.html
  • Useful for static website hosting

Write Permissions

write
Upload permission
  • Upload new files
  • Move/copy files into this folder
  • Create new subdirectories
  • Requires r permission to see uploaded files
move
Move permission
  • Move files/folders from this folder to another
  • Rename files within the folder
  • Requires w permission at destination
delete
Delete permission
  • Permanently delete files
  • Permanently delete folders
  • Cannot be undone (unless using unpost feature)

Special Permissions

dots
Dotfiles permissionUser can enable the option to show dotfiles (hidden files) in listings.
  • See files/folders starting with .
  • Toggle visibility in settings
  • Dotfiles still accessible by direct URL regardless
See dotfiles configuration for more details.
admin
Admin permission
  • See upload timestamps
  • See uploader IP addresses
  • Reload configuration
  • Access control panel features
  • View system information
all
All permissions combinedShortcut for rwmda. (read/write/move/delete/admin/dotfiles)

Permission Combinations

Common Patterns

Permission Precedence

User Groups

Permissions can be granted to:
  • Individual users: alice, bob
  • Groups: @team, @admins
  • Everyone: *
  • Logged-in users: @acct

Granting and Revoking

Permissions are additive within a user’s grants. A user with both r and w can read and write.

Volume Inheritance

Permissions do not inherit from parent volumes. Each volume has independent permissions.
Visitors can see that /private exists (from the root volume) but cannot open it unless they have permission.

Authentication Requirements

Password Protection

Volumes require authentication if no * (everyone) permission is granted:

Mixed Access

Advanced Features

Unpost Permission

The --unpost feature allows users to delete their own recent uploads even without d permission.

Append Permission

Control who can append to existing files:

Edit Permission

By default, editing files requires rwd (read+write+delete). The --rw-edit option changes this:

Security Best Practices

Important security considerations:
  1. Write-only folders (w without r) prevent uploaders from seeing what they uploaded
  2. Get-only access (g) should be combined with filekeys to prevent URL guessing
  3. Admin permission (a) reveals uploader IPs - grant carefully
  4. Delete permission (d) is permanent - consider using unpost instead
1

Start with minimal permissions

Begin with read-only (r) and add write permissions as needed
2

Use groups for teams

Create groups instead of listing individual users repeatedly
3

Separate admin volumes

Create dedicated volumes for admin-only content
4

Enable unpost for safety

Use --unpost to allow users to undo accidental uploads
5

Review regularly

Audit permissions periodically, especially for a and d

Troubleshooting

User has w but not r permission. Add r for visibility:
Moving requires m permission at source and w at destination:
Check for * in permissions. Remove to require authentication:
User needs . permission AND must enable in settings:
Then user enables dotfiles option in the [⚙️] settings tab.