Team collaboration

Multiple people building on the same project at the same time, without stepping on each other's work.

Sharing projects

1. Open project settings
2. Click Share
3. Share the link with teammates
4. They claim access with the link

Role	View	Edit	Deploy
Viewer	Yes	-	-
Editor	Yes	Yes	Yes

Parallel development

In Coder mode, team members work on different features simultaneously:

Developer A: session/550e8400-e29b-41d4-a716-446655440000
Developer B: session/7c9e6679-7425-40de-944b-e07fc1f90ae7
Developer C: session/6ba7b810-9dad-11d1-80b4-00c04fd430c8

Session branch names use UUIDs (for example session/550e8400-e29b-41d4-a716-446655440000).

Each session has its own git branch, database, and preview URLs. Conflicts can occur when merging -- use Sync with main to resolve them before creating a PR.

Code review workflow

1. Developer builds feature in a session
2. Creates pull request from Appifex
3. Team reviews on GitHub
4. Merge when approved
5. Use Publish to deploy changes to production

Edit anywhere

Environment	Best for
Appifex	AI-assisted building, visual progress
VS Code / Cursor	Local development, debugging
GitHub	Code review, PR discussions

All changes sync automatically via Git.

Best practices

• Use descriptive session titles in Appifex -- add-stripe-payments not my-changes (branch names remain UUID-based)
• Check for overlapping work before starting on shared code
• Review before merging -- use the diff view in Appifex or GitHub
• Keep main stable -- test in session branches first