What is the Team feature?

The Team feature in Greta.sh allows project owners to collaborate seamlessly with others while maintaining full control over the project. It enables structured collaboration by defining clear roles, permissions, and contribution ownership — ensuring security, accountability, and smooth teamwork.

With Teams, owners can invite collaborators, control who can actively contribute to the project at any given time, and manage integrations, credits, and deployments centrally.

Team Roles in Greta.sh

1. Owner

The Owner is the ultimate authority of the project. Each project has only one Owner.

• Full control over the project
• Can invite, remove, and manage team members
• Controls integrations, credits, and deployments
• Can transfer contribution access to editors and take it back anytime

2. Editor

Editors are collaborators who can contribute to the project when access is granted by the Owner.

• Can contribute code only when given control
• Cannot invite or manage other team members
• Cannot transfer access to other editors
• Work within the Owner’s project environment and integrations

3. Viewer

Viewers are read-only participants and act as an audience to the project.

• Can view the project
• Cannot make code changes
• Cannot access integrations or settings
• Ideal for demos, reviews, or audits

Contribution Control (Transfer & Take Back)

Greta.sh follows a single-active-contributor model to avoid conflicts and ensure clarity during collaboration.

• By default, the Owner has contribution control
• Owner can transfer control to any Editor
• Only one person can actively contribute at a time
• Owner can instantly take back control from an Editor

Project Locking Behavior

When Owner Has Control

• Editors see the project in a locked (read-only) state
• Editors can view the project but cannot contribute

When an Editor Has Control

• Owner sees the project in a locked state
• Owner cannot contribute at that moment
• Owner can override and reclaim control at any time

The Owner is always the final authority in the project.

Credits & Billing

• All credits are deducted from the Owner’s account
• Credits are deducted even when Editors make code changes
• Editors do not consume their own credits in collaborative projects

This keeps billing centralized and simple.

Integrations & Ownership

GitHub

• Only Owners can connect GitHub repositories
• Only Owners can push or pull code
• Editors cannot link their own GitHub accounts

Supabase

• Supabase is connected only by the Owner
• Editors can use the connected Supabase project in code
• Editors cannot view Supabase credentials or account details

Netlify Deployment

• Editors can deploy the project
• Only Owners can undeploy or cancel deployments

Analytics (Google Analytics)

• Analytics configuration is Owner-only
• Editors cannot add or modify analytics settings

Personal Organization

• All users (Owner, Editor, Viewer) can organize projects in their own folders
• Folder organization is personal and does not affect other team members
• Each user can move projects to different folders independently

Project Permissions Comparison Table

Why Team Feature Matters

• Safe and controlled collaboration
• Clear ownership and accountability
• Conflict-free development
• Centralized billing and integrations
• Enterprise-ready permission handling

The Team feature makes collaboration in Greta.sh powerful yet controlled, giving Owners confidence while enabling Editors to contribute efficiently without stepping on each other's work.