Skip to main content

Auto-Provision a New Team's Workspace

By the end of this recipe, standing up a new team takes a single prompt — Copera AI creates their channels, builds the boards they run on with the right tables and columns, seeds a shared runbook, and stands up the automation that welcomes and rosters every new hire — so a new team lands in a workspace that's ready to work instead of an empty one. Provisioning is the unglamorous work that decides how fast a team gets going: the channels, the trackers, the runbook, the routine automations. Because all of it lives in one workspace, you can describe the team once and have the structure built for you — not clicked together tab by tab.

Readiness: Available now — Ask Copera AI builds the scaffold and the on-hire automation runs today. The version where a named Provisioning Concierge teammate stands up new teams on its own is rolling out in early access.

What it does​

Provisioning a new team is two jobs, and Copera handles both.

First, the one-time build: a new team needs a place to talk, boards to track their work, a document that says how they operate, and a few automations to run the routine. Second, the ongoing wiring: as people join that team, each one has to be slotted into place — added to the roster, announced to the group, handed the runbook.

The old way is a checklist someone works through by hand every time a team spins up or grows. Here, you describe the team once and Copera AI creates the structure — channels, boards, tables, columns, seed rows, and documents — then builds an automation that repeats the per-person wiring on its own.

What lands when you provision a team:

  • Channels for the team to work and coordinate in.
  • Boards with the exact tables and columns they track, plus a few seed rows so day one isn't a blank slate.
  • A shared runbook document — how the team operates and who owns what.
  • An on-hire automation that adds every new member to the roster, welcomes them in the team channel, and notifies their manager — automatically, for every hire.

Build it yourself​

Provisioning has a build half and an automation half, and it's worth being precise about which is which — it's the difference that keeps this accurate. Creating channels and boards is a build action; keeping the roster current as people join is an automation.

Part 1 — Stand up the team's scaffold​

Create the team's space and channels

Decide where the team lives and how they'll talk. A new team usually needs a main channel for day-to-day work and a second for stand-ups or announcements. Creating a team and its channels is a build action — Ask Copera AI can create them from your description, or you can add them by hand.

Create the team's boards, tables, and columns

This is the heart of provisioning: the trackers the team runs on. Create a Work board with a table for the team's items — columns for Title, Status (e.g. New, In progress, Waiting, Done), Priority, Assignee, and Due date — and a Team Roster board with Member, Role, Start date, and Onboarding status. Ask Copera AI can build every board, table, and column from a sentence; see What Copera AI Can Do and Creating a Board.

Seed starter rows and a shared runbook

Fill in enough that day one isn't empty: a handful of seed rows on the Work board (the team's first known tasks) and a runbook document — "How this team works," owners, cadences, and links. Ask Copera AI can create the rows in a batch and draft the document, or you can write them yourself.

note

Creating channels, teams, and boards is a build action — done by Ask Copera AI or by hand. Automations don't create channels or boards; they populate and connect what's already built — creating rows, posting messages, sending notifications, and creating documents. That's why the scaffold above is a one-time build, and the per-hire wiring below is the automation.

Part 2 — Wire in every new hire​

Trigger: Workspace member joined

In Automations, start a flow with the Workspace member joined trigger so it runs the moment anyone new is added to the workspace.

Condition: Only this team (optional)

Because the trigger fires for every new member, add a condition on the new person's team or role so only the right hires get slotted into this team's structure. Skip it if this whole workspace is the team.

Action: Add them to the Team Roster

Add a Create row action on the Team Roster board, mapping the new member into the Member column and stamping their Start date with Set date to now (or Set date relative for a future start). Set Onboarding status → Onboarding.

Action: Announce them in the team channel

Add a Post channel message action to the team's main channel — a warm "Welcome to the team!" naming the new member, so the group knows who just joined.

Action: Notify the lead and hand over the runbook

Add a Send notification (or Send direct message) to the team's lead so they know to reach out, and either a Send direct message to the new hire linking the runbook or a Create document action for a personal "Getting started" page.

tip

This automation wires each hire into the team's structure. To give the person a full welcome — an assigned checklist with due dates and check-ins over their first weeks — pair it with the AI Onboarding Buddy recipe, which runs from the same Workspace member joined trigger.

Or just ask Copera AI​

You don't have to click through all of that. Open Ask Copera AI, describe the team you're standing up, and it builds the scaffold and the automation for you:

"We're standing up a new Support team. Create a Support team with channels for #support and #support-standup. Build a Support Work board with a tickets table — columns Title, Status (New, In progress, Waiting, Resolved), Priority, Assignee, and Due date — and a Team Roster board with Member, Role, Start date, and Onboarding status. Add a shared 'How the Support team works' document. Then create an automation: when someone new joins the workspace, add them to the Team Roster, post a welcome in #support, and notify me."

Ask Copera AI creates the team and channels, builds every board with its tables and columns, drafts the runbook, and assembles the automation — the full build layer in one pass. With the default Ask before acting permission mode, it shows a review card before each change, so you approve each channel, board, and the automation before any of it exists. It only ever creates what your own account is allowed to create. See What Copera AI Can Do for the complete build layer.

Make it a standing teammate​

Creating boards, tables, columns, and channels is on the teammate tool list — which makes provisioning a natural job for a standing AI teammate.

Early access

AI teammates are rolling out gradually. When one reaches your workspace, a named Provisioning Concierge can own this end to end — standing up a new team's channels, boards, and documents, then keeping the roster current as people join, all under its own identity. A teammate never deletes data and never sends outside your workspace, so anything that leaves Copera (like a welcome email) stays with an Automation and its connectors. Until teammates reach you, everything in this guide can be built today — see AI Teammates.

Tips​

tip

Scope the on-hire automation with a condition. The Workspace member joined trigger fires for everyone who joins the workspace. Add a condition on the new member's team or role so only the people who belong to this team get slotted into its roster and channel — one automation, the right team for each hire.

tip

Describe the shape once, reuse it. Save the plain-English prompt you used to stand up the first team. Next time you launch one, tweak the names and hand the same description back to Ask Copera AI — provisioning becomes a copy-paste, not a project.

tip

Keep the build behind a review, keep sends behind approval. Provision with Ask before acting so you approve each channel and board as it's created, and if your on-hire automation emails anyone, use draft or approval delivery so a person signs off before it leaves the workspace.

Frequently Asked Questions​

Can Copera AI set up a whole team's workspace at once?​

Yes. Ask Copera AI can create the team and its channels, build the boards a team runs on — tables, columns and all — seed starter rows, draft a shared runbook document, and assemble the automations the team relies on, all from one plain-English description. By default it shows a review card before each change so you approve the scaffold before it exists.

Can an automation create a channel or board when someone joins?​

No — and the distinction matters. Creating channels, teams, and boards is a build action, done by Ask Copera AI or by hand. An automation's actions populate and connect what's already built: it creates rows, posts channel messages, sends notifications and direct messages, and creates documents. So standing up the scaffold is a one-time build, and the recurring per-hire wiring is the automation.

How does Copera slot each new hire into the right team automatically?​

An automation on the Workspace member joined trigger runs the moment someone new is added. It adds them to the Team Roster board, announces them in the team channel, notifies their manager, and hands over the runbook — every time, without anyone remembering to do it. Add a condition on team or role so only the right hires are wired into each team.

Does Copera AI create roles for the new team?​

No. Ask Copera AI can take you to your Roles settings, but it doesn't create or change roles and permissions itself — that stays in your hands, on purpose. Provisioning covers the team's channels, boards, documents, and automations; role and permission changes remain a human decision.

Do I have to build all of this by hand?​

No. Describe the team you're standing up and Ask Copera AI builds the scaffold and the automation for you to review — or build the pieces yourself on the canvas and with the board tools. Both paths reach the same result; the AI just does it in one pass.