Collaboration FAQs
Frequently asked questions about working with teams and collaborators in Juliet.
Written By Samir Patel
Last updated 3 months ago
Adding Collaborators
How do I invite someone to my project?
Open project
Settings β Collaborators
Click "+ Add Collaborator"
Enter their email
Select role (Viewer, Editor, Admin)
Send invitation
They'll receive an email with accept link.
Do collaborators need a Juliet account? Yes. If they don't have one, they can create an account when accepting the invitation.
How many collaborators can I add? Depends on your plan:
Free: 1-2 per project
Pro: 5 per project
Team: Unlimited
Can I add collaborators to multiple projects? Yes! Each project has independent collaborator limits.
What if my collaborator didn't receive the invitation?
Check they provided correct email
Have them check spam folder
Resend invitation from Collaborators settings
Invitations expire after 7 days
Roles and Permissions
What's the difference between roles? Owner: Full control, can delete project, cannot be removed Admin: Manage collaborators, edit project settings and code, cannot delete project Editor: Edit code and files, use AI, view preview/terminal, cannot manage collaborators Viewer: Read-only access, view code and preview, cannot edit anything
Can I change someone's role after inviting them? Yes! In Collaborators settings, find the collaborator, click role dropdown, select new role, and save.
Can Viewers download the project? Typically no. Viewers have read-only access.
Can multiple Editors edit the same file? Yes, but not simultaneously. Changes sync after saving.
Who can use AI to make changes? Owners, Admins, and Editors can chat with AI and request changes. Viewers cannot.
Working Together
How do we coordinate who's editing what? Best practices:
Communicate in project chat
Announce before editing shared files
Assign different files/components to different people
Can we see each other's changes in real-time? Not quite real-time. Changes sync after saving.
How do we avoid overwriting each other's work?
Communicate what you're editing
Work on different files
Save frequently
Refresh before editing
Don't edit same file simultaneously
Managing Access
How do I remove a collaborator?
Settings β Collaborators
Find person to remove
Click Remove button
Confirm removal
Access revoked immediately
Can I remove someone temporarily? Remove them, then re-invite later when needed. Or downgrade to Viewer.
Can an Admin remove the Owner? No! Only the Owner can remove their own ownership.
Can collaborators add other collaborators? Only Admins can add/remove collaborators.
Invitations
How long do invitations last? Typically 7 days. After that, they expire and need to be resent.
Can I cancel an invitation? Yes! In Collaborators settings, find pending invitation and click Cancel.
Project Ownership
Can I transfer ownership of a project? Check settings for ownership transfer feature. If available, go to Settings β Advanced or Ownership.
Can a project have multiple owners? No, one owner per project. Use Admin role for co-leads.
Practical Scenarios
Client wants to review my work. What role? Viewer - Perfect for clients who need to see code and preview but cannot edit.
Hiring a contractor for 2 weeks. What role? Editor - They can code but can't manage team. Remove their access after project completion.
Team of 5 developers building together. Setup?
One person creates project (Owner)
Add 1-2 leads as Admins
Add other developers as Editors
Communicate in project chat
Assign different features to different people
Best Practices
Assign Appropriate Roles
Clients: Viewer
Stakeholders: Viewer
Developers: Editor
Team leads: Admin
Communicate Before Editing In chat: "Working on Header.jsx now"
Regular Access Audits Monthly review who still needs access.
Download Backups Before adding many collaborators, download project backup.
Set Team Guidelines Document expectations for who edits what and how to communicate.
Use External Tools Complement Juliet with Slack/Teams, Zoom, Trello/Jira, and GitHub.
Respect Each Other's Work Don't delete others' code without discussion.