One team. One workspace. Zero chaos.

Workspaces are how teams organize files, manage access, and collaborate on dosya.dev. Think of them as shared drives, with fine-grained permissions built in.

Create a Workspace View Plans

Unlimited Members, on paid plans

Unlimited Workspaces, on paid plans

4 Built-in Roles, plus custom

+ Custom Roles

How a video team uses Workspaces

The producer creates a workspace Sarah creates a workspace called "Brand Campaign 2026" and invites her team: 2 editors, a colorist, a sound designer, and the client.

She assigns roles Editors get Member access so they can upload, organize and share files, and delete their own. The client gets Viewer access so they can download and comment, but can't upload or delete anything.

Everyone works from the same place Editors upload 500 GB of dailies. The colorist pulls graded clips. The client reviews cuts and leaves comments. All from one workspace. No more "which Dropbox folder was it in?"

The project wraps Sarah removes the client from the workspace, which revokes their access immediately. The files stay exactly where they are, for as long as she keeps them - nothing expires, and nothing is reclaimed on a timer. When she no longer needs them she downloads or deletes them herself.

How a healthcare company keeps data in Germany

The CTO creates a workspace with region restrictions A healthcare company handles patient imaging data under GDPR. The CTO creates a workspace called "Patient Scans" and picks eu-central-2 (Frankfurt, Germany) as its location. That choice is made once, at creation, and cannot be changed afterwards. Every file written into the workspace is stored on Cloudflare R2 in the EU jurisdiction, which constrains the stored bytes to EU data centres.

Allowed regions are enforced Every file in this workspace is stored in the EU and stays there: the location is stamped on the workspace at creation and no later upload can land anywhere else. Delivery is a separate question. When an authorised person opens a file, the bytes travel to wherever that person is - so a consultant in London downloading a scan receives it in London. Storage residency is what is guaranteed here, not that the data is never read abroad.

Team members across Europe collaborate safely Radiologists in Berlin, Munich, and Vienna are invited as Member. External consultants in London get Viewer access. The stored copy stays in the EU wherever they connect from; what each of them downloads travels to them.

Audit logs prove compliance Every upload, download, and access event is logged with the user, timestamp, IP, and region, and paid plans keep 400 days of that history. When auditors ask "where is the data stored?", the workspace's location and the audit log provide a clear, verifiable answer.

One storage location per workspace

Each workspace has exactly one storage location, chosen from all 46 when you create it and fixed from then on. Every file written into the workspace is stored there. This is available on every plan, Free included, and is what underpins GDPR, HIPAA and other data residency requirements. Enterprise adds the signed Data Processing Agreement, not a different placement.

Set up in under a minute

Create

Name your workspace, pick a region, and you're live. Takes 5 seconds.

Invite

Add team members by email. Assign roles. They get access instantly, no app to install.

Collaborate

Upload, organize, share, and comment. Everyone sees the same files in real time.

Everything a team workspace needs

Unlimited Members on paid plans

Invite as many people as you need, with no per-seat charges. A Free workspace holds up to 5 members, including you, and a Free account can own 3 workspaces.

Granular Permissions

Control who can upload, download, delete, share, or manage the workspace.

Shared Folders

Organize files in folders with their own permission overrides per member.

Comments

Leave feedback on any file. Threaded conversations keep discussions organized.

Audit Logs

See who uploaded, downloaded, deleted, or shared every file. Full activity history.

File Requests

Send upload links to external people. Files land directly in your workspace.

See how permissions work in practice

Click on a flow to see what happens when different roles try to perform actions.

Member uploads a file

ALLOWED

Alex Member

Upload video.mp4

Permission upload: yes

Result File saved

Viewer tries to delete a file

BLOCKED

Client Viewer

Delete video.mp4

Permission delete: no

Result Denied

Admin invites a member with a custom Uploader role

ALLOWED

Sarah Admin

Invite mike@co.com

Assign Uploader (custom)

Result Invite sent

Custom Uploader role tries to share a file externally

BLOCKED

Mike Uploader (custom)

Share report.pdf

Permission share: no

Result Denied

The right access for the right people

Every workspace member gets one of four built-in roles, each defining exactly what they can and can't do. Need something in between? Create a custom role and pick its permissions one by one - a custom role always ranks below Admin.

Permission	Admin	Member	Viewer
View & download files
Upload files			-
Delete their own files			-
Delete anyone's files		-	-
Share links externally			-
Comment on files
View activity history		-	-
Invite members		-	-
Assign roles		-	-
Change workspace settings		-	-
Manage billing	-	-	-
Delete workspace	-	-	-

Create your own custom roles

The 5 built-in roles cover most teams, but sometimes you need something specific. Custom roles let you mix and match permissions to fit your exact workflow.

Toggle each permission individually

Name roles to match your org

Set per-folder overrides

Reuse across workspaces

Example: Create a Reviewer role that can view, comment, and download, but not upload or delete. Or a Contractor role that can upload to specific folders only.

Workspaces for every team

Production Studios

One workspace per project. Members upload dailies, clients review cuts, producers manage access.

Agencies

Separate workspace per client. Internal team gets Member access, clients get Viewer access. Clean separation between accounts.

Research Labs

Share multi-terabyte datasets across universities. Principal investigators manage access, students upload results.

Engineering Teams

Store build artifacts, design files, and documentation. CI/CD uploads via API, engineers download what they need.