Loading tutorials…
Loading tutorials…
Monday.com is easy to spin up and easy to scatter. Three weeks in, most teams have 14 boards across 4 workspaces with no naming convention and no governance. This walks the setup sequence that keeps Monday useful past month three.
Who this is forFounders and ops leads opening a brand-new Monday.com account, or anyone who created a workspace months ago and is about to invite the rest of the team. If you already have 10+ boards and you cannot tell a teammate which workspace to look in, this tutorial is for you.
What you'll need
Step 1
Monday goes Account → Workspaces → Boards → Groups → Items → Subitems → Updates. Picking the wrong level for each layer is what causes sprawl.
Account = your company. One account, one billing seat pool.
Workspace = a team or business unit (Sales, Marketing, Ops, Product). Use workspaces to scope who-sees-what at a high level. 5-8 workspaces is typical for a 20-person team.
Board = one stream of work (e.g., "2026 Campaigns," "Sales Pipeline — North America," "Q2 Launches"). Boards are where data lives. Most teams overshoot here.
Group = a row category inside a board (e.g., "In Progress," "Done," "Backlog"). Use groups for status buckets or quarters, NOT for sub-projects.
Item = one row. A deal, a campaign, a task, a ticket. This is your atomic unit of work.
Subitem = a row nested inside an item. Use for sub-tasks of a parent task (campaign → assets), NOT for unrelated work.
Rule of thumb: if two pieces of work are tracked differently or owned by different people, they belong on different boards. If they share the same fields, they belong as items on one board.
Step 2
Time zone, week start, date format, working days. Changing these after 30 boards exist breaks every recurring automation and report.
Open Monday → Avatar (top-right) → Administration → General.
Set Account Name, Company Logo, Primary Timezone, Week Start Day, Date Format.
Administration → Working hours. Set the working days and hours that drive automation timing (e.g., "Notify me Monday 9am" uses this).
Administration → Default permissions. This sets what new members can do by default. Tighten this — default is more permissive than most teams realize.
Administration → Customization → Items. Rename "items" to something domain-specific if helpful ("Deals" on a CRM board, "Tickets" on a support board) — done per board, but you can set the account default tone here.
Step 3
Start with 4-6 workspaces, one per team. Resist the urge to make a workspace for every project.
Monday → Sidebar → "+" next to Workspaces → Add new workspace.
Name workspaces after teams or business units: "Sales," "Marketing," "Operations," "Product," "Client Services."
Add a 1-line description on each workspace explaining what lives there. This becomes the team's anchor when they wonder "where does X go?"
Set workspace permissions: Open (everyone in the account sees it) vs Closed (only invited members). Sales pipelines + financials usually want Closed. Marketing calendars usually want Open.
Decide on a "Personal" workspace policy. Each user gets one by default for private boards. If you want them to keep work in shared workspaces, document this in your team handbook.
Step 4
The first board sets the convention. Naming, column structure, group structure, view defaults — everything else copies this.
Inside a workspace → "+ Add new board" → choose: From scratch, From template, Duplicate, Import. Start "From template" for common use cases — Monday has solid CRM, marketing, and project templates.
Name the board descriptively: "2026 Q2 Campaigns" beats "Campaigns." Future-you will thank you.
Set the board owner (1 person — not "the team"). Owners are accountable for board health.
Build column structure intentionally. Common columns: Status (the kanban driver), Person (owner), Date (deadline), Numbers (budget/score), Dropdown (category), Text (notes), Files (attachments), Connect Boards (link to other boards).
Set up 3-5 default views: Main Table, Kanban (by Status), Calendar (by Date), Timeline / Gantt (by Date range), Dashboard (later). Each view is a way for the team to see the same data through different lenses.
Step 5
Items = work units. Subitems = sub-tasks of a work unit. Updates = the conversation thread on an item. Mixing these is the #1 source of confusion.
Click an item to open the Item Card. Notice the tabs: Updates (conversation), Activity (audit log), Files (attachments), Subitems (children).
Enable subitems on the board: Board settings → Subitems → Enable. Set subitem columns (usually a subset of parent columns: Status, Person, Date).
Rule for Subitems: use for atomic sub-tasks of a parent item (e.g., a "Launch new landing page" item has subitems for "Write copy," "Design," "Build," "QA"). Do NOT use subitems for unrelated work.
Rule for Updates: use for conversation about the item (decisions, blockers, status notes). @mention teammates to notify them. Updates are the audit trail for "why did we change the status?"
Train the team explicitly on Items vs Subitems vs Updates in week one. Drift here is irrecoverable later.
Step 6
Monday has 4 user types: Admin, Member, Viewer, Guest. Each has different cost implications and access scope.
Administration → Users → Invite users.
Admin = full account control including billing. Keep this to 1-2 people max.
Member = full board create / edit access on workspaces they belong to. This is your default for paid teammates. Each Member consumes a paid seat.
Viewer = read-only. Cheaper than Member (counts as half a seat on most plans). Good for execs or stakeholders who watch but do not edit.
Guest = external collaborators (clients, vendors). Cannot see other guests. Limited to specific boards. Free up to a cap, then billable on Pro+.
Audit who actually needs Member vs Viewer. Most teams overbuy Member seats — execs and "I just want to see status" stakeholders are usually Viewers.
Step 7
Before the team starts creating boards, write a 1-page naming and ownership convention. This is what prevents sprawl.
Create a "Monday Conventions" doc (Monday Doc inside a "Team Handbook" workspace works well).
Document: workspace naming (always team name), board naming (e.g., "[Year Q#] [Stream Name]"), column conventions (Status column is always first, Person column always exists, Date column is always due-date not start-date), view conventions (Main Table always exists, Kanban always exists for status-driven boards).
Document who can create workspaces (admins only, typically) and who can create boards (any Member).
Document the "Board Owner" expectation: every board has one named owner accountable for health.
Revisit quarterly. As the account grows, the conventions need to evolve.
Common mistakes
Creating a workspace for every project
What goes wrong: Six months in, you have 40 workspaces and search no longer works. Onboarding new hires takes 3 hours instead of 30 minutes because nothing is where it should be. ~$3K/yr in lost productivity per 10-person team.
How to avoid: Workspaces are teams, not projects. Cap at 5-8 workspaces for accounts under 50 users. Boards = projects, not workspaces.
Inviting everyone as Member instead of Viewer
What goes wrong: Eight stakeholders who only watch dashboards consume Member seats at $24/user/mo (Pro). That is $2,300/yr you didn't need to spend — Viewers see the same boards.
How to avoid: Default execs and read-only stakeholders to Viewer. Reserve Member for people who actually edit items, run automations, or own boards.
Using Subitems for unrelated work
What goes wrong: Reports break because subitems do not roll up like items. Cross-board automations skip subitems by default. You end up with parallel data the team forgets to update — and stale data costs decisions worth $5-10K per quarter.
How to avoid: Subitems are sub-tasks of a parent item. If two pieces of work do not share a parent context, they are separate items, not subitem siblings.
No naming convention, no board ownership
What goes wrong: 30+ boards exist with names like 'Campaign Board,' 'New Campaign Board,' 'Real Campaign Board (USE THIS).' Nobody knows the source of truth. The team duplicates work across 3 boards. ~$4K/yr in lost productivity for a 10-person marketing team.
How to avoid: Document naming conventions (e.g., "[Year Q#] [Stream]") and assign a single owner to every board. Audit quarterly.
Building automations before the structure stabilizes
What goes wrong: You wire up 20 automations across boards. Then you restructure the boards in month two and half the automations silently break (status names changed, columns renamed). Tasks stop getting assigned and a deal falls through worth $8K+.
How to avoid: Stabilize the board structure for 2-3 weeks before adding non-trivial automations. Document every automation in a central registry.
Defaulting to Personal workspaces for shared work
What goes wrong: Reps and PMs create boards in their Personal workspace 'just to test,' then start running real work there. When they leave, the boards become unrecoverable. You lose an entire sales pipeline worth $50K+ in tracked opportunities.
How to avoid: Workspace policy: all real work lives in shared workspaces. Personal is for drafts only. Audit Personal workspaces monthly for anything that should be moved.
Recap
Done — what's next
How to set up Monday Sales CRM without rebuilding it in month three
Read the next tutorial
Hand it off
A clean Monday.com setup pays compounding dividends for years. A messy one creates a Saturday-cleanup job every quarter and quietly costs $4K-10K/yr in lost productivity. A vetted Monday specialist will run the entire setup — workspaces, boards, naming conventions, permissions, integrations — typically as a one-shot $300-600 engagement, or ongoing ops support at $400-1,200/mo at $14-16/hr.
See specialist rates
Start with 3-5 workspaces matching your real teams (Sales, Marketing, Ops, Product, Client Services). Resist creating a workspace per project — workspaces are organizational units, not project containers. You can always add more later; you cannot easily merge them.
Subitems = atomic sub-tasks of a parent item (a 'Launch landing page' item has subitems for copy, design, build, QA). Separate items = work tracked the same way on the same board (10 campaigns on a Campaigns board). Separate boards = work tracked differently, owned by different teams, or with different field structures (Sales Pipeline vs Marketing Campaigns).
Free works for teams of 2 with simple needs. Basic ($9-12/user/mo) unlocks unlimited items and basic dashboards. Standard ($12-15/user/mo) adds automations, integrations, and timeline view — this is where most teams start. Pro ($24-28/user/mo) adds time tracking, formula columns, private boards, and dependency columns. Start on Standard unless you specifically need Pro features.
Yes — per board. Open the board → Board name dropdown → Customize item name → enter the domain-specific name (Deal, Ticket, Campaign, Task). This makes the UI feel native to the use case and reduces team confusion.
Updates are the conversation thread on an item — anyone can post, @mention teammates, attach files, and the thread is the audit trail. Notes (the Notes column) are a single text field on the item. Use Updates for back-and-forth conversation; use a Notes or Text column for static metadata.
Monday.com
Monday Sales CRM is fast to spin up and easy to wire wrong. Pipeline stages drift, contact data fragments across boards, and reports stop making sense within 90 days. This walks the configuration that holds up past the first quarter.
Monday.com
Monday automations are powerful and easy to over-wire. Most accounts past 100 active automations have 30-40% redundant or broken ones nobody notices. This walks the patterns that hold up at scale.
Monday.com
Most Monday dashboards rot within 60 days because they were built to look impressive instead of answer questions. This walks the dashboard patterns leadership actually uses every Monday morning.
Monday.com
DIY Monday.com is a great idea — until you have 30+ boards with no governance and the team has stopped trusting the data. This is the honest framework: when the cost of self-managing exceeds the cost of hiring.