Project types

AVS distinguishes between cloud and local project modes.

Cloud projects

Use cloud projects when you need:

Shared collaboration
Workspace-backed organization
Remote synchronization
Standard editor access from /editor/[projectId]

Cloud projects require connectivity when opened in the beta editor.

Local projects

Use local projects when you need:

Better offline resilience on the current machine
Local storage of binaries and caches
Recovery through the offline editor flow

Local projects are intentionally constrained compared with workspace-backed cloud projects.

Project dashboard workflows

From /app you can:

Create projects
Search them
Sort them
Switch between grid and list modes
Duplicate projects
Delete projects
Select multiple projects
Open workspaces or personal project scopes

Prompt-based project creation is built into the dashboard and can pre-seed a project from a stored prompt-to-project intent.

Workspaces

Workspaces are the multi-user organizational unit in AVS.

What a workspace gives you

A shared project scope
Member and invite management
Optional workspace-specific storage settings
Workspace studio configuration
Shared collaboration context for projects opened with workspaceId

Membership flows

The settings surface currently supports:

Viewing workspaces you belong to
Creating a workspace
Inviting users
Accepting invites
Leaving a workspace
Deleting a workspace if permitted
Reviewing members and pending invites
Removing members
Revoking invites

Storage model

Default behavior

Workspaces use managed cloud storage by default.

External storage

The beta settings UI also supports external object storage configuration on a per-workspace basis. The current shape supports:

S3-compatible credentials
Custom endpoint
Region
Bucket
Force-path-style option

This is intended for setups like S3-compatible vendors, R2-style endpoints, or self-managed compatible storage.

Misconfigured state

The storage settings UI explicitly handles a misconfigured state so admins can see when BYO storage settings were saved in an invalid form.

Branching inside projects

Branches are project-local, not workspace-global abstractions.

The editor surface supports:

Creating feature branches
Switching branches
Comparing branches
Merging into main

This gives AVS a more non-destructive review loop than a simple linear undo stack.

Local/offline behavior

The app includes an explicit offline editor route and local project restore machinery.

Important expectations:

Cloud projects are blocked while offline.
Local projects can restore binaries and continue from local state.
The top bar exposes sync and restore status for local projects.

If you need offline flexibility, choose local mode early instead of trying to retrofit it after collaboration begins.

Shared links vs workspaces

Workspaces are for internal collaboration. Shared links are for exported-video distribution.

Use a workspace when you need:

Co-editing
shared projects
member roles
storage administration

Use a shared link when you need:

a reviewable export
public or org-scoped playback
an embeddable player URL

See Rendering & Sharing for the delivery layer.