Skip to main content
Teams enable collaboration by allowing multiple users to share resources, billing, and access to Delino services. Teams provide the structure needed for effective collaboration.

Team Features

Teams created by individual users for their projects:
  • Creator is automatically the owner
  • Individual billing account
  • Shared resources and billing among members

Team Roles

Teams use role-based access control (RBAC) to manage permissions:
Full Control: Complete administrative accessPermissions:
  • All Admin permissions
  • Delete team
  • Transfer ownership
  • Change billing settings
  • Remove other owners
Limits: Each team must have at least one owner
Team Management: Administrative tasks without destructive actionsPermissions:
  • All Member permissions
  • Invite and remove members
  • Update team settings
  • Manage team API keys
  • View billing information
  • Change member roles (except Owner)
Limits: Cannot delete team or modify owners
Standard Access: Use team resourcesPermissions:
  • Access team resources
  • View team information
  • Use team services
  • View own membership details
Limits: Cannot manage team or members

Team Features

Shared Resources

  • Unified Billing: All team members share the same billing account
  • API Keys: Team-level API keys accessible to all members
  • Services: Shared access to Delino services
  • Usage Tracking: Consolidated usage across all team activities

Collaboration

  • Member Invitations: Email-based invitation system
  • Role Management: Flexible permission assignment
  • Team Dashboard: Centralized view of team activity
  • Usage Reports: Track team resource consumption

Security

  • Role-Based Access: Granular permission control
  • Audit Logging: Track team management actions
  • Secure Invitations: Token-based invitation system with expiration

Team Structure

Every user has a personal account (slug: ~) that serves as their individual workspace:
  • Personal billing account
  • Personal API keys
  • Individual usage tracking
Users can create and join multiple teams, each with its own billing and resources.

Team Slugs

Each team has a globally unique slug used for URL routing:
slug
string
required
URL-friendly team identifierRequirements:
  • 4-20 characters
  • Lowercase letters only
  • Hyphens allowed
  • Numbers allowed
  • Must be globally unique
Examples:
  • engineering
  • data-team
  • team-42
  • Team ❌ (uppercase)
  • ai ❌ (too short)
  • Engineering ❌ (uppercase)
The slug ~ is reserved for personal accounts

Team Billing

Subscription Requirements

All teams require a Pro subscription ($10/month) with a configured payment method.
Teams:
  • Require Pro subscription
  • No free trial for teams (trial only for personal account)
  • Payment method required at creation

Billing Structure

Team
├── Billing Account (team)
├── Pro Subscription ($10/month)
├── Included Credits ($10)
└── Usage Charges (pay-as-you-go)

Team Invitations

Invitation Flow

1

Send Invitation

Admin or Owner invites a member by email through the team members page
2

Email Delivered

Invitation email sent with:
  • Team name and inviter information
  • Assigned role
  • Secure invitation link
  • 24-hour expiration notice
3

Accept Invitation

Recipient clicks link and accepts
  • Email must match invitation
  • Token must be valid and not expired
  • User added to team with specified role

Team Limits

Members
number
No hard limit on team size
Teams can have unlimited members
Pending Invitations
number
Maximum 50 pending invitations per team
Rate limit to prevent spam and abuse
Slug Length
string
4-20 characters
Must be globally unique across all teams

Best Practices

Clear Naming

Use descriptive team names and slugs that identify the team’s purpose

Appropriate Roles

Assign roles based on principle of least privilege

Regular Audits

Review team members and permissions quarterly

Onboarding Process

Establish clear onboarding process for new members

Offboarding Process

Remove departing members promptly and rotate shared keys

Monitor Usage

Track team usage to optimize costs and resources

Next Steps