monday.com Auto-Populate Team Rosters on New Boards

monday.com doesn’t auto-populate team rosters from a master list to new project boards out of the box. Here’s what you can build natively, and how a small API integration loads the roster for you.

You just created a new project board for client XYZ. Now you need to add your team members so you can track confirmations, assignments, and availability.

You open your master Team Roster board. Scroll through 25 names. Click the first one, copy it, switch back to the project board, click “Add Item”, paste. Repeat 24 more times.

15 minutes later, your roster is loaded.

Now imagine you’re running 60 projects per year. That’s 1,500 manual copy-pastes of team member names and 15 hours a year spent copying names from one board to another.

There has to be a better way.

Team Members Should Auto-Populate on New Project Boards

Here’s what teams need:

When a new project board is created, team members from a master roster should automatically appear as items on the project’s confirmation, assignment, or availability tracking board:

• Master roster (25 team members) → Project board (25 items created automatically)
• Each member as a separate row ready for status tracking
• No manual item creation
• Works for any roster type: team members, vendors, contractors, band members, crew, suppliers

What Users Have Run Into

Two workarounds come up again and again. The first chains a duplicate-item automation with a move-item automation. Users report the catch: the item that gets moved is the original, and the duplicate stays on the roster. Duplicated items also don’t retain ongoing updates from the source roster, which breaks the roster-as-source-of-truth model.

The second is a template board with the roster already filled in. It saves the copy-paste once, but pre-populated template boards don’t update when roster data changes: add a new team member to your master roster and the template doesn’t reflect it.

Native Ways to Get Roster Members onto New Boards

1. Keep the Roster on the Template Board

If the same people join every project, add them as items on the template board. Duplicating with Structure & items, or creating the board from a template, brings them along: templates carry over all column values, including people assigned in the People column (they aren’t notified). Update the template when the roster changes. See what else templates keep and drop in template settings lost on duplication.

A template holds up to 500 items on Standard, 1,000 on Pro and 2,500 on Enterprise, so very large rosters belong on a separate board.

2. Link the Roster With Connect Boards

Instead of copying people, add a Connect Boards column on the project board that points at the roster board, and link the members each project needs; Mirror columns can show their role, phone or email. A board can hold 10,000 connected items (100,000 on Enterprise) and 750 per cell. Duplicating a board doesn’t carry Connect Boards and Mirror column settings over, so check them on each new board.

3. Copy the Roster With a Workflow Loop (Pro and Enterprise)

In the workflow builder, a Get all step fetches the items in a board or group, and the Loop block runs the same actions on each one in a single workflow run. Put a Create item action inside the loop to copy each roster member onto the confirmations board when a deal reaches Won. Steps after the Exit loop block run once all items are processed, so a notification there tells the PM the roster is in.

The same builder has Duplicate board and Create from template blocks. monday.com’s article doesn’t say whether a Create item step can target a board made earlier in the same run, so test that before relying on it.

4. Copy Items by Hand With Batch Actions

For a small, one-off roster, select the people on the roster board, duplicate them with Batch Actions, then use Move to board on the copies and map the columns when prompted.

Duplicating Through the API

The API’s duplicate_board mutation can copy a board’s structure and items, but monday.com warns that “an asynchronous duplication process may take some time to complete, so the query may initially return partial data.” A script should wait for the items before relying on them.

Wondering whether BoardBridge fits your project setup? Ask us.

Native Options Compared

How to Auto-Populate a Roster on a New Board

No setting does this, but there are two ways to build it.

A native workflow. The AI workflow builder can read the roster with a Get all step, loop through it with a Loop block and add each name with Create item. It works best when the target board already exists: monday.com doesn’t document whether the target can be a board created earlier in the same workflow, and each workflow counts against your plan’s active-workflow cap.

A custom API integration. For boards created from templates, a small integration on the monday.com API is the dependable route. It runs right after the project boards are created (see auto-creating a project folder from a CRM trigger for that step):

Step 1: Configure Roster Mapping

You define which roster boards feed which project boards. For example:

You can configure as many roster-to-board mappings as needed. Each project type can have different roster sources.

Step 2: Fetch All Roster Items

When a new project is created, the integration queries each source roster board via monday.com’s API:

query {
  boards(ids: [123456]) {
    items_page(limit: 500) {
      cursor
      items { id name }
    }
  }
}

items_page returns up to 500 items per call; for a longer roster, pass the cursor to next_items_page.

Result: A list of all team member names (or vendor names, band member names, etc.) from the roster board.

Step 3: Create Items on Target Project Boards

For each roster item, create a corresponding item on the target project board:

mutation {
  create_item(board_id: 789012, item_name: "Alex Johnson") {
    id
  }
}

Repeat for every roster member. If your Team Roster has 25 members, 25 items are created on the Team Confirmations board.

The items are created sequentially via API. For 25 items, this takes a few seconds; the pace is set by monday.com’s API rate limits. Source: monday.com API rate limits

Step 4: Items Appear on the Project Board

By the time you open the new project’s Team Confirmations board, all 25 team members are already there, ready for status tracking:

• Alex Johnson
• Maria Garcia
• James Chen
• Sofia Rodriguez
• … (21 more)

Each row is ready for you to mark “Confirmed”, “Pending”, “Declined”, or whatever statuses your workflow uses.

Zero manual item creation.

Example: Event Management

When a new event project is created:

1. All template boards duplicated (Event Overview, Band Confirmations, Team Confirmations, Travel, Production)
2. On Band Confirmations board: 12 items created (one per band member)
3. On Team Confirmations board: 8 items created (one per team member)

Result: Both confirmation boards are pre-populated with the full roster as soon as the boards exist.

The event coordinator opens the Band Confirmations board and sees all 12 band members ready for outreach. No setup required.

Different Rosters for Different Boards

You can configure multiple roster sources that feed different target boards within the same project.

Example configuration:

Different project types can use completely different roster configurations.

Option 1: Duplicate a Roster Board with Its Content

Keep one roster board per board type, laid out with the columns that board type needs. When you duplicate a board, you can copy the structure only, the structure and content, or the structure, content and updates (monday.com Help Center), so a duplicate with content starts with the whole roster on it. The workflow builder’s Duplicate board block offers the same choice of structure only or content too (monday.com Help Center).

Option 2: A Workflow That Loops Over Each Roster

The Get all step fetches the items you want to process, such as all items in a group, and the Loop block runs the same actions on each one in a single workflow run (monday.com Help Center). For an event management project:

Example: Event Management Project

• Board Type: Band Confirmations → Roster Source: Band Roster (20 members)
• Board Type: Team Confirmations → Roster Source: Team Roster (35 members)
• Board Type: Vendor Coordination → Roster Source: Vendors Roster (12 vendors)

When the CRM deal closes and the workflow runs:

• Band Confirmations board gets 20 items (one per band member)
• Team Confirmations board gets 35 items (one per team member)
• Vendor Coordination board gets 12 items (one per vendor)

Each roster is independent. Adding a new vendor to the Vendors Roster doesn’t affect the Band Roster. Updating team member names on the Team Roster doesn’t touch the band members. For one-off copies between boards, see monday.com data transfer between boards.

Plan Your Roster Mappings

Before you build, write down each pairing:

Which Option Fits

How to Set Up a Roster Workflow

Roster Changes Reflected in Future Projects Only

Important: Roster loading is a one-time snapshot at project creation time.

If your Team Roster has 25 members today and you create a project, those 25 members appear on the project board. If you add a 26th member to the Team Roster next week, existing projects are unaffected — they still have 25 members.

New projects created after the roster change will have 26 members.

This is by design: each project is an independent snapshot. You don’t want past projects changing when you update your current team roster.

If you need to add a new team member to all active projects, you’d do that manually or via a separate workflow rule (not part of the roster load).

Column Values Aren’t Copied by Default

A basic roster load creates items (rows) on the target board using the item name from the source roster. It doesn’t copy column values unless you add that mapping.

Example:

If your Team Roster board has columns like:

• Name
• Email
• Phone
• Department
• Availability Status

Only the Name transfers to the project board. The email, phone, department, and status do not automatically populate.

Why? Because project boards and roster boards typically have different column structures. Your roster might track hiring date and salary; your project board tracks confirmation status and travel needs. The column structures don’t align.

Workaround: If you need roster data (like email addresses or phone numbers) on the project board, you can:

1. Use Connect Boards columns to link project items back to the roster
2. Use Mirror columns to pull roster data into the project board
3. Extend the integration to copy selected column values where both boards have matching columns

For most teams, loading the names is sufficient — the rest gets filled in during project execution.

Why a New Board Can Look Empty at First

Roster members don’t appear immediately after board creation

monday.com’s native automations run asynchronously. When you trigger an automation — like “When status changes to Won, create an item on the Band Confirmations board” — here’s what happens:

During that gap, you might:

• Open the newly created board and see it empty
• Start manually adding items because you think the automation didn’t fire
• Wait, confused, wondering if something broke
• Refresh the page multiple times to see if items appeared yet

For high-volume users or complex automation chains, the delay can grow. If your automation sets off other automations (cross-board updates, status changes, notifications), each step queues separately — compounding the delay.

The “Refresh and Wait” Problem

There’s no progress indicator on the board. No “roster loading…” message. Just an empty board and uncertainty, until someone opens the automation’s Run History to see whether it ran.

Limitations You Should Know

Only the item name is transferred. If you need full column data from the roster on the project board, roster loading alone won’t do it. You’d need Connect Boards + Mirror columns or custom mapping.

Roster changes don’t propagate retroactively. If you remove someone from the Team Roster, they’re not automatically removed from past projects. Each project is a snapshot.

Large rosters take longer. Each item is a separate API call, so a roster of 100+ items takes noticeably longer than 25, and the integration should pace its calls to stay within monday.com’s rate limits.

Duplicate names are allowed. If your roster has two people named “John Smith,” both will be created on the project board. There’s no deduplication unless the integration checks for it.

Subitems need their own step. If your roster board uses subitems (e.g., team members with sub-roles), a basic load copies only the parent items; subitems need separate create_subitem calls.

Roster Loading: Quick Answers

Q: Can you auto-populate People Column when creating items on new boards? A: Automations can map a People column when they create items on another board. For public forms, see monday.com People Column in Forms for details.

Q: Can I use the same roster for multiple board types? A: Yes. You could have both “Vendor Coordination” and “Vendor Confirmations” pull from the same Vendors Roster board: give each its own Get all and Loop.

Q: Can I filter which roster members get loaded? A: Yes, by group. The Get all step can fetch all items in a group, so keep “Active” and “Inactive” groups on the roster board, or keep separate roster boards.

Q: What if a roster board is deleted? A: That roster’s steps have nothing to load. Run history shows which block failed; point the workflow at the replacement board.

Q: Can I add roster members to a project after creation? A: Yes, manually — just create new items on the target board. Or re-run the roster workflow from a button or status trigger.

Q: Does this work with subitem rosters? A: Yes. The Get all step can fetch all sub-items under a given item, so a roster stored as subitems can be looped over too.

Q: Can I map columns beyond just the name? A: Inside the loop, Current result - Loop refers to the roster item being processed, so the create step can carry more than the name. Test the columns you need on a sample project.

Q: How fast does roster loading happen? A: The loop runs every roster item in a single workflow run. Each action it runs counts toward your monthly automation actions (25,000 a month on Pro), so large rosters add up.

Q: Can I re-run roster loading if I realize I used the wrong roster? A: Delete the incorrect items, fix the Get all step, and re-run the workflow, or copy the correct roster by hand.

Q: Can monday.com cross-board automations populate different rosters? A: Not with a classic recipe; none is documented that copies all items of another board. The workflow builder can, with Get all and Loop blocks for each roster-target pair.

Frequently Asked Questions

Eliminate Manual Roster Loading

For teams managing 50+ projects per year with team rosters of 10-50 members each, manual roster population is a serious time sink. At 15 minutes per project for 60 projects/year, that’s 900 minutes (15 hours) of pure busywork annually.

TaskRhino can build the roster load for you — when your new project boards are created, all team members from your master roster appear as items, ready for tracking and confirmation.

Ready to reclaim those 15 hours per year? Book a free 30-minute call.