​
Organizations & Projects

Organizations are your team workspace - think of them like your company account that handles billing and team members. Projects group related functions together - like “Website API” or “Payment System”.
Structure Example
Acme Corp (Organization)
├── Website API (Project)
│   ├── User Login Function
│   ├── Payment Function
│   └── Email Function
└── Mobile App (Project)
    ├── Push Notifications
    └── File Upload

​
Team Roles & Permissions

​
Roles

Owner

Company founder, CTO, or whoever manages billing and organization

Admin

Team leads, senior developers who manage projects and team members

Member

Developers who build and deploy functions in assigned projects

​
Permissions

Each team member gets a role that controls what they can access and modify:
PermissionOwnerAdminMember
Organization Management
Delete organization✅❌❌
Manage billing✅❌❌
Change organization settings✅❌❌
Team Management
Invite team members✅✅❌
Remove team members✅✅❌
Change member roles✅✅❌
Project Management
Create projects✅✅❌
Delete projects✅✅❌
Modify project settings✅✅❌
Function Management
Create functions✅✅✅
Edit function code✅✅✅
Delete functions✅✅✅
Deploy functions✅✅✅
Monitoring & Logs
View function logs✅✅✅
View usage metrics✅✅✅
View billing details✅❌❌
Important: Only owners can delete the organization or manage billing. Choose your owner carefully.

​
Setting Up Your Team

Create Organization

Set up your team workspace with a clear name and description

Invite Team Members

Add your team and assign appropriate roles based on their responsibilities

Create Projects

Organize your functions into logical groups for better management

Control Access

Manage which team members can access specific projects

​
Team Invitations

Invite team members by email and assign them Admin or Member roles. New members can sign up using Google, GitHub, or email authentication - they must use the same email address that received the invitation.

​
Team Management Best Practices

Start with Minimal Access

Give team members only the permissions they need initially - you can always add more later

Regular Access Reviews

Review team permissions monthly and remove access for members who no longer need it

Clear Role Communication

Explain project access and role responsibilities when inviting new team members

Organize by Function

Group related functions into projects that match your team’s workflow

​
Project Organization

Use clear, descriptive project names that explain what the functions do: ✅ Good Names
  • user-authentication - Clear and specific
  • payment-processing - Describes the purpose
  • email-notifications - Easy to understand
❌ Avoid These
  • project1 - Not descriptive
  • misc-functions - Too vague
  • everything - Not organized

​
Single Sign-On (SSO)

Google SSO

Sign up with Google accounts

GitHub SSO

Use GitHub authentication

Magic Links

Email-based authentication with secure login links
Important: New members must use the same email address that received the invitation to automatically join with the correct role and project access.

​
Billing & Cost Management

Organization Billing

All costs roll up to the organization owner for centralized management

Project Breakdown

See which projects consume the most resources and optimize accordingly

Usage Transparency

Admins see organization usage, members see their own function metrics