Published: 09.10.2026
Subaccounts let you give each person, server or project its own login and its own folder on Cloud Drive. Instead of sharing one login, you decide which data each login can reach and whether it can change anything. Cloud Drive allows up to 100 subaccounts, and each can be limited to its own folder and set to read-only. This article explains a practical structure, the access levels to choose and the habits that keep shared storage manageable.
Why separate logins matter
A shared login hides who did what and gives everyone the same power. If its password leaks, every person and every script has to change it. Separate subaccounts limit the damage from one leak to one folder, make activity easier to trace and simplify removing access when someone leaves. They also let you grant reading rights without writing rights.
A simple folder structure
Plan the folders before you create the subaccounts. One folder per server, per project or per person works well, and a clear naming pattern helps later. An example structure could include:
- One folder for the backups of each server, named after the server.
- One folder for each client project that needs file exchange.
- One folder for each team member who needs personal storage.
- An archive folder for old data that is rarely touched.
Choosing the access level
- Read-write for the account that writes backups or uploads files.
- Read-only for people or systems that only need to see or download files, such as a reporting tool or an auditor.
- Limited to its own folder for every subaccount where possible, so that no login can see another project.
Connection limits and parallel jobs
Cloud Drive allows up to 10 concurrent connections. Plan parallel jobs so that backups, syncs and manual transfers do not compete for the same slots. A schedule that starts several large jobs at the same moment may cause failures, so stagger the start times. Check the logs after each change to the schedule.
Onboarding and offboarding
- Create the subaccount with a clear name that shows its purpose and its owner.
- Set the folder limit and the access level before you share the login details.
- Send the connection details through a secure channel, not in a plain e-mail or chat message.
- When a person or project ends, disable or remove the subaccount and review what its folder contains.
- Record the change with the date in your notes.
Good practice
- Use a separate key or a unique password for each subaccount.
- Do not reuse the same login on several servers.
- Review the list of subaccounts every quarter.
- Write down the owner of each subaccount.
Frequently asked questions
Can a subaccount see other folders? If you limit it to its own folder, it should not. Check the setting in the customer area after you create the subaccount, and test that its login cannot reach other folders.
What is the difference between read-only and read-write? A read-only subaccount can download files but cannot change them. Give read-write access only to accounts that must upload or delete.
Should several people share one subaccount? It is better to give each person a separate login, so that actions can be traced to the right person.
