What signing up creates for you
Signing up creates almost everything you need. Knowing exactly what is already there saves you from building a second copy of it by hand.
You signed up (a new organization)
Creating an account creates a new organization with you as its owner, along with everything below. It is all-or-nothing: you will never end up with a half-configured organization.
| Created for you at signup | What it is |
|---|---|
| Your organization | Everything else lives inside it |
| A workspace named Default | Your first workspace |
| A project named Scratchpad | A ready-made place to start a session — no repository attached |
Three environments: sandbox, build, deployment | One per role; sandbox is the default |
Two agent definitions: Default and Default (Codex) | One per coding agent — see the deliberate non-choice below |
| Three platform playbooks | PlatformSmith Work Item · PlatformSmith Knowledge Base · PlatformSmith Land Work |
| You, as organization owner | Full control of everything in it |
What is not created — and it is one thing
| Not created | Why not |
|---|---|
| A coding-agent credential | It is yours, not ours. → Step 1 |
| A controller | It needs a Docker or Kubernetes host that only you can provide. → Step 2 |
| A Git connection | Only needed to import a repository. → Connect GitHub |
The middle one is the real work. Everything else on this page exists so that connecting a controller is the only thing standing between a new account and a running agent.
The three environments
You get one environment per role, all of them Host with Docker:
| Name | Role | Default? | What it is for |
|---|---|---|---|
sandbox | sandbox | yes | Interactive work. This is where your agents run |
build | build | no | Building project images |
deployment | deployment | no | Long-running service pods |
Two consequences worth knowing before you rearrange them:
You can rename an environment, change its type, and change which one is the default. You cannot change its role — there is no request that carries one. Getting a role wrong means deleting the environment and creating a replacement.
That is also why you get three: the set you would have had to build by hand, already built, because a wrong role is expensive to undo.
All three start as Docker. That is not a guess about your infrastructure — build is the one role that must be a Docker host, because building images needs Docker itself. If you are heading for Kubernetes, switch the type in the setup step, before a controller connects; afterwards the switch is refused. → Step 2
The Scratchpad project
Scratchpad is a project with no repository attached — deliberately. A repository-backed project would need a Git connection, a repository and a branch before it could launch anything, which is exactly the setup this is here to spare you.
It exists so your first launch has somewhere to go. Rename it, delete it, or point it at a repository whenever you like — none of that is special-cased.
No default coding agent yet — on purpose
You get two agent definitions, one per coding agent:
| Definition | Coding agent |
|---|---|
Default | Claude Code |
Default (Codex) | Codex |
Neither is flagged as the organization's default, and that is a decision rather than an omission. At signup nobody has configured a credential yet, so choosing a coding agent here would be a guess made with no information — and an organization whose admin later connects Codex would find every unspecified launch failing against Claude.
When you connect a credential in step 1, the setup wizard
flags the matching definition as your organization's default automatically. Connect a Codex
credential and Default (Codex) becomes the default; connect a Claude one and Default does.
You do not have to translate "I connected Codex" into "go and flag the Codex definition" — and until a default exists, a launch that does not name a definition is refused outright rather than falling back to a guess.
company in the APIThe UI calls it an organization. The API calls the same object a company — you will see
company_uuid in responses and company in scope parameters. They are the same thing. It is the
only place in the model where the two vocabularies differ, and worth knowing before your first API
call.
You were invited
If someone invited you, accepting the invitation creates nothing. You join their existing organization and see the workspaces, projects and environments your role gives you access to. There is no "your" workspace waiting for you, and no Scratchpad of your own.
What that means in practice:
- Their setup is probably already done. If a controller is connected, you can launch immediately.
- Whether you can create things depends on your role. A member can read across the organization and create workspaces but cannot launch anything; a workspace-editor works inside one workspace; an owner or admin can do everything. → The five roles
- You can add a personal coding-agent credential of your own, which is used ahead of the organization's shared one for sessions you start. → Personal vs shared
Next
→ The setup checklist — what is left, and it is short.