Small team setup

Start with one shared project

Use this after Server Manager is running and native access works. Keep the first rollout narrow enough to inspect.

Goal

Prove one shared project

Finish with a small group that can use one project folder, plus admin visibility into users, permissions, quota, and backup state if enabled.

Before

Before you start

  • Two or three users.
  • One shared project folder.
  • Clear read/write permissions.
  • Quota checks, plus backup checks if you enabled an optional backup target.

1. Add only the first users

Use the WebUI admin area to add the people who need the first project folder, or have them create their own accounts after admin setup. Keep the group small until permissions are clear.

2. Set quotas where useful

Use quotas to keep a test setup from becoming an uncontrolled storage dump. Leave room for version history and backup staging.

3. Share one project folder

Create one project folder and share it with named users. Use read-only access for people who should only review files.

4. Connect team devices

Use native apps for daily work. Use the WebUI for admin and browser checks. Use WebDAV/rclone only for tools that need a standard endpoint.

5. Check access and optional backup

  • Upload one small project file.
  • Confirm another user can access it with the intended permission.
  • If backup is enabled, confirm backup status has handled it.
  • Restore or download the file and open it.

Success check

Users, permissions, quota expectations, and any backup state are clear before the team adds more folders.

Continue

Keep the rollout narrow