The Deployer documentation
Getting started

Working with your team

Your workspace is everything in your account: its projects, deployments, servers, services and the connections they use. On the Pro and Team plans you can invite people to work in it with you.

The Team page

Open Team in the sidebar. Owners and admins see these tabs:

  • Members: you and everyone who has joined, with a search box and a role filter. Click a person to set their access.
  • Invitations: invites that haven't been accepted yet.
  • Activity: invites, joins and access changes, with who made them and when.
  • Handovers: projects you've handed to a teammate, or that are waiting for you. See handing projects to a teammate.
  • Workspaces you're in: other people's workspaces you've joined.

Inviting someone

  1. On the Team page, click Invite people.
  2. Under Email addresses, paste one address or many, separated by commas, spaces or new lines.
  3. Choose Member or Admin.
  4. To give a member access straight away, open Give access now and pick their projects and what they can do there, and, if you like, their servers, services, connections and workspace permissions. This is optional: you can do it any time from the member list.
  5. Click Send invite. They get an email with a link. They sign in, or create an account, with that same address and click Join.

Your email address must be verified before you can invite anyone. A new member sees nothing until you give them access, either in the invite or later.

The link works for 14 days. If it runs out, click Send again next to their address on the Invitations tab.

Every seat counts, yours included: Pro has two (you and one teammate) and Team has ten. A pending invite holds a seat until it's accepted or cancelled. The Team page shows how many seats are used.

Roles

  • Admin: sees every project and every value, and can change who has access to what. Only you, the owner, can change someone's role.
  • Member: sees only what you give them, and does only what you allow.

Setting a member's access

Click the person on the Members tab. The Access for drawer has these sections:

  • Role: Member or Admin.
  • Projects: each project, with what they can do there. Copy from… gives them exactly the access another member has. A row at the top sets the same access on every project in the list.
  • Servers: which servers they may use, and how far. See Servers.
  • Services: which databases, caches, queues, buckets and email services they may see, use or manage.
  • Connections: which cloud accounts, Git accounts and package repositories they may choose for new work. For services and connections, see sharing services and connections.
  • New projects: what they get on projects created from now on.
  • Across the workspace: extra things they can do without being an admin.

The footer counts your unsaved changes. Click Save changes, or Discard. After saving, an Undo appears for a moment.

What they can do on a project

Pick a preset in one click:

  • View: the dashboard, deployments and logs.
  • Deploy: also redeploy, pull and restart, start and stop servers, and the retry and health-check settings.
  • Manage: also change the project's setup, domains, scaling, connected services, builds, add-ons, code changes and who can reach the app.

Or choose No access, or click Customize permissions and choose permission by permission:

  • Deploying: Deploy; Start and stop; Retries and health checks.
  • Changing the project: Change setup (analysis, services, architecture, workflow); Domains; Scaling; Connected services.
  • Building and extras: Build and packages; Add-ons; Code review.
  • Who can reach the app: App access (see who can open your app).
  • On the servers: SSH terminal; Project Copilot; Service logins.
  • Automation: AI guide; Env from Git.

Environment variables are set separately, per project:

  • Hidden: no environment variables at all.
  • Names: which variables are set, never their values.
  • Values: the values too.
  • Edit: change values and restore older versions (this also needs Deploy, because saving redeploys the app).

Some permissions only work together with others. The SSH terminal, Copilot and service logins can read the values on the server, so they need env Values. The AI guide and Env from Git save settings and redeploy, so they need Deploy and env Edit (the guide also needs Change setup). When you tick one of these, what it needs is turned on with it, and the picker says so.

Workspace permissions

These aren't tied to one project:

  • Across the workspace: Create projects (including a repository's other services as projects of their own), Adopt existing apps (bring in apps already running in a cloud account; see bring in apps already running in your cloud) and Cloud services (create and manage databases, caches, queues, buckets and email, and attach them to projects they can change).
  • Servers: See servers, Operate servers, Manage servers and Delete servers. Only the owner can give Delete servers.
  • Services: See, Use or Manage, plus Can reveal passwords, for chosen services or all of them.
  • Connections: See or Use, for chosen connections or all of them.

What stays with the owner

Some things only you, the workspace owner, can do, even when a teammate is an admin:

  • deleting projects and services
  • adding, verifying, replacing, revealing or deleting connections and their credentials
  • granting control over, or releasing, infrastructure that already existed in your cloud account
  • handing projects over to someone
  • giving the Delete servers permission
  • your plan and billing, which are always personal

Teammates who joined before access could be set per project kept what they had (every project, with deploy and environment values). A note on the Team page asks you to check it once; click Looks right when you have.

Switching workspaces

When you're a member of someone else's workspace, a Workspace switcher appears at the top of the sidebar. You can also click Open on the Workspaces you're in tab. While you work in another workspace, a bar across the top of the app says whose it is, with a button to go back to your own.

Removing someone

Open the person on the Members tab and click Remove from workspace. They lose access straight away. To cancel an invite, open it and click Cancel invite. Members can leave a workspace themselves with Leave on the Workspaces you're in tab.

If your plan changes to one with fewer seats, the teammates you already have keep their access. You just can't invite anyone new until a seat is free.