Workspaces & Projects
Organize and manage your BuildGreenfield projects
Understanding Workspaces
Workspaces are containers for organizing related projects. Think of them as folders for your generated applications.
Personal Workspace
Every account comes with a default personal workspace. This is perfect for:
- Side projects
- Learning and experimentation
- Solo development
Team Workspaces
Team plan subscribers can create shared workspaces for:
- Company projects
- Collaborative development
- Shared resources and billing
Projects
Each project represents a single generated application with its own:
- Source code repository
- Database instance
- File storage
- Preview deployments
- Version history
Project Settings
General
- Name: Display name for your project
- Description: What the project does
- Tech Stack: Frameworks and libraries used
- Visibility: Private (default) or Team-accessible
Environment Variables
Store API keys, database URLs, and other secrets securely. Variables are encrypted and only accessible to your project.
# Example environment variables
DATABASE_URL=postgresql://...
STRIPE_SECRET_KEY=sk_test_...
SMTP_HOST=smtp.sendgrid.net
Deployment
- Preview URL: Auto-generated preview domain
- Custom Domain: Configure your own domain (Pro/Team)
- Auto-Deploy: Enable continuous deployment on changes
Managing Projects
Creating Projects
- Navigate to your workspace
- Click “New Project”
- Provide description and preferences
- Click “Generate”
Archiving Projects
Archive inactive projects to declutter your workspace:
- Go to Project Settings
- Scroll to Danger Zone
- Click “Archive Project”
Archived projects are read-only and don’t count toward usage limits.
Deleting Projects
⚠️ Warning: Deletion is permanent after 90 days.
- Go to Project Settings → Danger Zone
- Click “Delete Project”
- Confirm by typing the project name
- Project enters a 90-day recovery period
During recovery, you can restore the project from your account dashboard.
Team Collaboration
Inviting Team Members
Team workspace owners can invite members:
- Go to Workspace Settings → Members
- Click “Invite Member”
- Enter email address
- Select role (Admin, Developer, Viewer)
Roles & Permissions
| Action | Viewer | Developer | Admin |
|---|---|---|---|
| View projects | ✅ | ✅ | ✅ |
| Edit code | ❌ | ✅ | ✅ |
| Deploy | ❌ | ✅ | ✅ |
| Manage settings | ❌ | ❌ | ✅ |
| Invite members | ❌ | ❌ | ✅ |
| Billing | ❌ | ❌ | ✅ |
Best Practices
Organization
- Naming: Use descriptive project names (e.g., “Customer Portal” vs “Project 1”)
- Tagging: Add tags for easy filtering (e.g.,
production,staging,experiment) - Workspaces: Separate personal and client work into different workspaces
Security
- Environment Variables: Never commit secrets to code; use environment variables
- Team Access: Grant minimum required permissions
- API Keys: Rotate keys regularly; use read-only keys when possible
Resource Management
- Archive Unused Projects: Keep your workspace clean and reduce clutter
- Export Critical Code: Maintain local backups of production projects
- Monitor Usage: Track generation credits and storage on your dashboard
Limits by Plan
| Feature | Free | Pro | Team |
|---|---|---|---|
| Projects | 1 | Unlimited | Unlimited |
| Workspaces | 1 | 1 | 5 |
| Team Members | 1 | 1 | 5+ |
| Storage | 500 MB | 10 GB | 50 GB |
| Preview Retention | 7 days | 30 days | 90 days |
Next Steps
- Learn about Isolation & Security
- Understand Rollback & Versions
- Check our FAQ for common questions