Board operations prompt · Connected to Kanera

Claude prompt to set up a client project workspace

Describe how the client or team works and let Claude propose a workspace structure, then build it for you when you are happy.

Best for: New agency clients, new internal teams, and replacing a messy board with a consistent workspace.

Works with: Any assistant connected to Kanera, such as Claude, ChatGPT, GitHub Copilot, Cursor, Codex, OpenCode, or Antigravity.

PromptFill in the 6 highlighted fields
You are helping me set up a new Kanera workspace. You are connected to Kanera through MCP.

Client or team: [NAME]
Type of work: [E.G. WEBSITE PROJECTS, RETAINER, CAMPAIGNS, PRODUCT DEVELOPMENT]
How work flows today: [STAGES FROM REQUEST TO DONE]
Who works in it: [ROLES AND WHETHER THE CLIENT WILL BE INVITED AS A GUEST]
What we report on: [E.G. HOURS, BUDGET, DEADLINES, APPROVALS]
First boards needed: [BOARD NAMES]

Before proposing:
1. Read the available Kanera workspace templates.
2. Read my existing workspaces so the new one is consistent with how we already work, where that makes sense.

Propose a workspace setup with:
- Recommended template and why.
- Lists in order, marking which are working stages that should count toward time in progress.
- Labels and their meaning.
- Custom fields for what we report on, with field types.
- The first boards to create.
- Two or three automations worth turning on, described in plain language.
- Anything the client should not see if they join as a guest.

Then wait. When I approve, create the workspace and boards from the approved plan. Ask before creating automations. If the organisation does not allow agents to create workspaces, stop and give me a short manual checklist instead.

Worked example output

Example result for a new monthly marketing retainer where the client will join as a guest.

Example result
Workspace proposal: Northwind Marketing Retainer

Recommended template
Marketing and Creative. It already has brief, production, and approval stages and matches our Fernway workspace.

Lists
1. Requests
2. Briefed
3. In Production (working stage)
4. Internal Review
5. Client Approval
6. Scheduled
7. Done

Labels
- Social, Email, Paid, Web, Urgent

Custom fields
- Hours (number): retainer burn-down
- Channel (single select)
- Go-live date (date)

First boards
- September 2026, Always-on social

Suggested automations
- When a card enters Client Approval, assign the account lead and set a due date 3 days out.
- When a card enters Scheduled, post a comment asking for the live link.

Guest considerations
- Guests see every card and field on the boards they join. Keep hours on a separate internal board, or invite the client with "Assigned items only" so they see just their approval cards.

Reply "create" to set this up, or tell me what to change.

Get a more reliable result

  1. Describe how work really flows today, including approvals; lists are hard to change once boards fill up.

  2. Reuse fields from existing workspaces so cross-client reporting lines up.

  3. Decide what guests can see before you invite the client, not after.

Prompt questions

Why does the workspace structure matter?

Boards in a workspace share lists, fields, and labels, so Table view and Global Work can compare them. A good structure up front makes reporting across clients possible later.

Does Claude pick from Kanera templates?

Yes. It reads the available workspace templates and recommends the closest one before suggesting changes.

Can Claude create workspaces on any plan?

Agent access depends on your plan and your organisation's agent access policy. If creation is not allowed, Claude stops after the proposal so you can set it up by hand.

Go from live Kanera work to a finished update.

Connect your AI assistant to Kanera so a new client starts with a consistent, reportable workspace in minutes.

Explore Kanera's AI workflow
Start free

30-day Pro trial. No card required.