> ## Documentation Index
> Fetch the complete documentation index at: https://vlyai-1c28d863.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Real-time collaboration

> Multiple people in the same project at the same time. Cursors, presence, and how conflicts are handled.

vly projects support **multi-user editing**. Multiple people can be in the same project simultaneously — prompting, hand-editing, browsing version history — and see each other's actions live.

## What you see

<CardGroup cols={2}>
  <Card title="Presence indicators" icon="users">
    Avatars in the top-right show who's currently in the project. Hover to see what they're viewing.
  </Card>

  <Card title="Live cursors" icon="mouse-pointer">
    In Code mode, see other editors' cursors and selections in real time.
  </Card>

  <Card title="Live prompts" icon="message-square">
    See "Alice is prompting…" indicators in the chat sidebar; their prompt and result stream in as it happens.
  </Card>

  <Card title="Build status" icon="loader">
    Shared build status — when one person triggers a build, everyone sees it.
  </Card>
</CardGroup>

## Conflict handling

Three rules:

<Steps>
  <Step title="Hand-edits use last-write-wins per file">
    If two people edit the same file at the same time, the later save wins. The earlier edit is preserved as a draft (recoverable from version history).
  </Step>

  <Step title="Prompts queue">
    Prompts run sequentially, not in parallel. If two people submit at once, the second waits for the first to complete. The "currently running" indicator shows who's blocking.
  </Step>

  <Step title="Schema changes lock briefly">
    A prompt that modifies the schema acquires a brief lock to prevent two simultaneous schema migrations. Other prompts queue.
  </Step>
</Steps>

For high-contention workflows (multiple developers parallelizing), use [branching](/building/branching) — each person works on their own branch, merges when done.

## Presence permissions

Members of your workspace can join any project they have access to. To restrict:

* **Project visibility**: set per-project (workspace / specific members / specific roles).
* **Read-only viewers**: members with the "viewer" role can join and see, but not edit.

See [Roles & permissions](/features/auth/roles-and-permissions).

## Tips

<Tip>
  **For multi-developer features, branch.** Working in parallel on the same main timeline causes conflicts and confusion. Branches isolate cleanly.
</Tip>

<Tip>
  **Use [comments and reviews](/building/comments-and-reviews) for async coordination.** When you don't want to interrupt your teammate, drop a comment instead.
</Tip>

## Related

<CardGroup cols={3}>
  <Card title="Branching" icon="git-branch" href="/building/branching">
    Parallel work without conflicts.
  </Card>

  <Card title="Comments and reviews" icon="message-square" href="/building/comments-and-reviews">
    Async feedback and review.
  </Card>

  <Card title="Workspaces" icon="building" href="/features/workspace/workspaces">
    The team-level container.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.