Team · StartupBuilder

Most stay asleep until their Trigger wakes them.

Properties

Property	Type	Required	Description
`mission`	`text`	required	What the Team is for, in one sentence.
`status`	`string`	required	One of `asleep` or `awake`: whether any of its Processes is on.

JSON

{
  "$id": "https://api.sb/routewise.dev/teams/team_1",
  "$type": "Team",
  "mission": "Example mission",
  "status": "asleep"
}

A Team groups many Roles: a Team groups the Roles that do one kind of work under one owner. groups, inverse team.
A Team serves many Startups: a Team does its one kind of work for every Startup it serves; a Startup wakes a Team when its trigger Event happens. serves, inverse teams.

State	Meaning	Moves to
`asleep` (first)	None of its Processes is on, so its Roles hold no work.	`awake` on `Process.enabled` when the Process belongs to this Team; `awake` on `Startup.built` when the Startup’s Templates turn on one of this Team’s Processes
`awake`	At least one of its Processes is on, and its Roles do that work.	`asleep` on `Process.paused` when no other Process of this Team is on

createCreates a Team.
POST /{namespace}/teamsdoTeam.created
getReturns one Team by id.
GET /{namespace}/teams/{id}readNo Event
listReturns Teams, newest first, one page at a time.
GET /{namespace}/teamsreadNo Event
updateChanges the given properties of a Team.
PATCH /{namespace}/teams/{id}doTeam.updated
deleteDeletes a Team; its history is kept.
DELETE /{namespace}/teams/{id}doTeam.deleted

Which Access level may call each Verb. One-way Verbs wait their delay window.

Operation	`owner`	`admin`	`member`	`viewer`
`Team.create`	Yes	Yes	Yes	No
`Team.get`	Yes	Yes	Yes	Yes
`Team.list`	Yes	Yes	Yes	Yes
`Team.update`	Yes	Yes	Yes	No
`Team.delete`	Yes	Yes	Yes	No

Text

Add a team to LedgerLark.

The Customer Team of a tutoring marketplace wakes when the first parent accepts an Offer. It groups the Customer Lead, Onboarding Specialist and Success Manager Roles under one owner.