Give a teammate access

Say Invite sam@leaseline.app as Engineering Lead with admin access. You approve the invitation, your teammate gets an email, signs in at startups.studio, and holds one Access Level in the app.

Needs Role

What you getCopy Anchor Link

• 1invitation to their email, to sign in at startups.studioHuman
• 1admin access: read everything and make every two-way change, access includedAccess Level
• 1one-way calls, such as dissolving the company, kept with you as ownerAccess Level
• 1seat they share with its agent, so their work has an ownerRole

Your agent doesCopy Anchor Link

# Human.invite
curl -X POST https://api.sb/leaseline.app/humans/invite \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"sam@leaseline.app","role":"engineering-lead","access":"admin"}'

import { $ } from 'startup-builder'

await $.Human.invite({ email: 'sam@leaseline.app', role: 'engineering-lead', access: 'admin' })

npx startup-builder do Human.invite --json '{"email":"sam@leaseline.app","role":"engineering-lead","access":"admin"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Human.invite({ email: 'sam@leaseline.app', role: 'engineering-lead', access: 'admin' })"
  }
}

Change itCopy Anchor Link

• Invite Sam to the Product Lead seat instead.
• Invite my contractor to the Customer Lead seat as a member.
• Let Sam approve deploys instead of me.

Under the hoodCopy Anchor Link

Systems

Workforce

Nouns

Human, Worker, Access Level, Permission, Role

Events

Human.invited

Every invitation also seats the person in a Role, shared with its Agent. The Role says what work is theirs; the Access Level says what they may reach, and never widens what the seat may call. Access levels explains the split.