Basecamp

Basecamp is a simple project management and team collaboration tool. It provides to-do lists, a message board, a calendar, and file storage, focusing on clear communication and reducing complexity.

Save favorite

Get discount

Compare

Go to Basecamp

Getting Started with Basecamp

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Set up your account basics, then create your first project.
Pick the minimum tools you need, then add more later.
Invite the right people early so work lands in one place.
Use Home + My Stuff daily to stay on top of tasks and notifications.

Purpose / Outcome

This section helps you get from “new account” to a working first project that your team can actually use.

Add your company basics (name/logo) so people recognize the workspace.
Create a first project (or start from a template) to avoid a blank slate.
Choose project access (Invite-only vs All-access) based on who should see it.
Turn on only the project tools you’ll use this week (you can change later).
Invite teammates so the first conversations/tasks happen in the right place.

Who this is for + When to use

Use this when you’re brand new to Basecamp or when you’re spinning up a fresh account for a new team or department.

You’re moving work out of email/spreadsheets and need one shared hub.
You want a simple “one project = one initiative” structure to start.
You need a predictable onboarding path for teammates and clients.
You’re setting up a company HQ project plus a few team/projects.
You want to standardize your “project starter kit” via templates.

Tip: Keep your first week focused on one project, one chat room, one to-do list, and one place for announcements.

Where in navigation + Related tabs

These are the key places you’ll bounce between while onboarding.

Home → for pinned projects, schedule preview, and assignments preview.
Top navigation → Hey! (notifications), Activity (reports), Find (search).
My Stuff → your assignments, schedule, drafts, bookmarks, recent activity.
Projects → where the actual work and tools live.
Teams and HQ → how many companies set up “HQ” and team spaces.

Mental model / Flow

Basecamp works best when each chunk of work has a home: a project. Inside a project, you choose tools for messages, chat, tasks, schedules, files, and more. The goal is that everyone knows where to post the next thing.

Account = your company workspace (people + projects).
Project = one initiative/client/team space.
Tools = the structured places where work lands (messages, to-dos, schedule, chat, etc.).
Home + My Stuff = your personal “control panel” across projects.
Hey! = where notifications collect so nothing gets lost.

Happy path workflow #1 — Create your first project

Follow this when you want a clean, minimal project that your team can start using today.

1Go to Home and click “Make a new project”.
2Name it after the initiative (e.g., “Website Redesign”) and add a short description.
3Pick a start/end date if you want it to show on the Lineup timeline.
4Choose project tools: start with the essentials you’ll actually use this week.
5Choose access: Invite-only for focused teams, or All-access for company-wide visibility.
6Add the right people (or share the All-access project link if applicable).
7Create one announcement (Message Board) explaining goals + who’s involved.
8Create one to-do list with 5–10 next actions and assign owners.

Expected outcome: A working project exists with the right people, the right tools, and a visible first set of tasks.

Happy path workflow #2 — Make Home feel like “your dashboard”

Follow this after you have a few projects so you can find what matters in seconds.

1Pin the projects you’re working on this week so they appear on Home.
2Rearrange pinned projects so the most important ones are top/left.
3Open Your Assignments and move the most important tasks into “Up Next”.
4Check Your Schedule preview; click “See all” if you need the full calendar.
5Use the directory view to confirm you can find active vs archived projects.
6Open Hey! and clear notifications so you start from a clean state daily.

Expected outcome: Home shows your priorities first: pinned projects, upcoming dates, and what you should do next.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
New work: make a Project or use an existing one?	If it’s a distinct initiative/client, create a new Project.	If it’s a new chunk inside the same initiative, add it as a message/to-do/doc in the existing Project.
Visibility: Invite-only or All-access?	Invite-only when work is sensitive or limited to a small group.	All-access when everyone should be able to discover and follow along.
Too many tools vs too few?	Start with fewer tools to avoid confusion.	Add tools later once there’s a real need and clear owner.
Repeatable work type?	Use a template if you do this kind of project often.	Start fresh if the workflow is unusual or one-off.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Turning on every tool — Start minimal; too many empty tools make people unsure where to post.
No project description — Add “what this is + who leads it” so newcomers don’t guess.
Inviting everyone to everything — Use All-access for discoverability, but keep membership focused for attention.
Using chat for decisions — Post decisions in a message/doc so they’re easy to find later.
Skipping assignments — Assign owners and due dates early so work doesn’t become “somebody should…”

Checklist: pre-check + post-check

Pre-check

Company name is correct and recognizable.
At least 1 starter project exists.
Project tools are chosen intentionally (not everything).
Key people are invited (or All-access is set).
First announcement + first to-do list posted.

Post-check

Team knows where to post updates (message vs chat vs to-dos).
You can find the project from Home (pinned if needed).
At least 5 tasks are assigned with owners.
Hey! notifications are understood and used daily.
You know how to search (Find) when something goes missing.

Practice lab (5–15 min)

Goal: Create a simple project your team can use for the next 7 days.

Steps

Create a project named “Weekly Ops”.
Turn on only: a chat room and a to-do tool (minimum).
Post a message: “What this project is for + how to use it.”
Create a to-do list with 6 tasks and assign 3 different people.
Pin the project on Home and move 1 task into your Up Next.

Verify you did it right

Project appears on Home (pinned).
Message exists explaining usage rules.
At least 6 assigned tasks exist, visible in My Assignments.
Your Up Next shows the single task you prioritized.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Getting Started with Basecamp
High-level onboarding path and what to read next.
The Home Screen
Logo, creating projects, directory view, schedule + assignments widgets.
Projects
Project tools, invitations, tool setup, and project settings.
How Basecamp Works
Conceptual walkthrough of the Basecamp way.
Training Your Team
Learning resources and rollout guidance.

How Basecamp Works

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Basecamp’s goal: keep project work in one place (not scattered across tools).
A project is the unit of work; tools are the structured places inside it.
Hey! collects notifications; Find helps you recover anything fast.
Use Home + My Stuff as your personal control panel.

Purpose / Outcome

This section gives you the “why” and the big-picture operating system, so the rest of Basecamp feels obvious instead of random.

Understand why Basecamp replaces scattered emails/files/tasks with a single project hub.
Learn where common items belong (announcements vs chat vs tasks).
Adopt a simple daily rhythm: Home → My Stuff → Project tools → Hey!
Reduce “where is that?” moments with Find and consistent posting habits.

Who is this for + When to use

Use this if your team is brand new, or if Basecamp feels like “a bunch of tools” rather than a coherent system.

Team members keep asking where to post updates.
You’re mixing chat + tasks + docs and decisions disappear.
You want a consistent roll-out story for new hires and clients.
You’re designing templates and want the right default tools.

Where in navigation + Related tabs

This is the conceptual glue across the Getting Started guide topics.

Top Navigation → Hey!, Activity, Find keep you oriented globally.
Home → shows what’s happening across projects (pinned, recent, assignments).
My Stuff → your personal tasks/schedule/bookmarks/drafts.
Projects → where work is executed (tools + activity timeline).

Mental model / Flow

Basecamp is designed to make “the right place” obvious. Keep announcements in one stream, tasks in one tool, files where they relate to work, and conversations attached to the work they’re about.

Project = the container; tools = structured lanes inside the container.
Use message-style tools for durable info; chat for quick coordination.
Prefer “one place per type of thing” over posting the same info in multiple tools.
Hey! is your notification inbox; you don’t need to rely on email to stay current.

Objects & Terms (starter glossary)

If you align on these terms early, team communication becomes simpler.

Account: the company workspace containing people + projects.
Project: a space for one initiative/team/client.
Tool: a feature inside a project (message board, chat, schedule, to-dos, etc.).
Hey!: the notification stack for updates you should read.
Pings: direct messages not tied to a project (1:1 or small group).
Find: global search across the account.
Lineup: a visual timeline of projects (when enabled).

State machine / Lifecycle

Basecamp’s Getting Started docs describe project states (active vs archived/deleted) and how visibility works, but not a single formal state machine for all objects.

Projects: active → archived (view-only) → unarchive (back to active), or delete (removed).
Notifications: new → read/cleared (plus set-aside behavior inside Hey!).
Assignments: assigned → moved to Up Next (personal priority) → completed.

Happy path workflow #1 — Daily operating rhythm

A lightweight routine that keeps you on top of work without living in meetings.

1Start at Home and scan pinned projects and recently visited work.
2Check Your Assignments preview; open full My Assignments if needed.
3Open Hey! and read/clear new notifications.
4Jump into the relevant project and post progress in the right tool.
5Assign next actions in to-dos so work is explicit.
6If something is missing, use Find rather than asking around.

Expected outcome: You know what’s new, what’s next, and where to work—without hunting through tools.

Happy path workflow #2 — “Where should this go?” posting flow

Use this when you’re about to post something and aren’t sure where it belongs.

1Ask: is this durable info people will need later?
2If yes: post it as a message/doc (not chat).
3If it’s a decision: include context + decision + owner + deadline.
4If it’s an action: create/assign a to-do (or card) with next step.
5If it’s a quick coordination note: use chat or ping, but link back to the durable item.
6If it’s a file: attach it to the item (message/doc/to-do) it relates to.

Expected outcome: Information lands in the “right place,” and future-you can find it fast.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Need a long-lived update?	Use a message/doc so it’s easy to reference later.	Use chat/ping only for quick coordination.
Need accountability?	Assign a to-do/card to a specific owner.	If no owner, rewrite until an owner + next step exists.
Team-wide visibility?	Use an HQ or All-access project for announcements.	Use invite-only projects for focused groups.
Lost something?	Use Find with keywords + filters.	If you can’t find it, ask the project lead what tool it was posted in.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Treating Hey! like spam — Hey! is the signal. Use it daily so important updates don’t pile up.
Posting the same update everywhere — Pick one durable home and link to it if needed.
No owners on tasks — Unowned work becomes ignored work.
Using Pings for project work — Pings are great for direct messages, but project work belongs in projects.
Never using Find — Find is faster than asking in chat and helps new teammates self-serve.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

How Basecamp Works
Conceptual walkthrough of the Basecamp way.
Top Navigation
Home, Hey!, Pings, Activity, Find, and more.
The Home Screen
Your dashboard and project directory entry points.
My Stuff
Your assignments, bookmarks, schedule, drafts, recent activity, boosts.

Top Navigation

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Home = your company dashboard and project entry point.
Launchpad lets you switch accounts tied to the same email.
Lineup is a visual timeline of projects (when enabled).
Hey! + Activity + Find are your always-available safety nets.

Purpose / Outcome

Top Navigation is the “always-there” bar that keeps you oriented no matter where you are in Basecamp.

Jump back to Home instantly when you feel lost.
Switch accounts via Launchpad if you belong to multiple workspaces.
Use Hey! as your notification inbox across all projects.
Use Activity for account activity and reports access.
Use Find to search across projects and filter results.

Who is this for + When to use

Use this when you’re learning the interface, juggling multiple projects, or trying to find something fast.

You need to switch between different Basecamp accounts quickly.
You want a single place to see what changed across projects.
You’re looking for a specific item but don’t remember where it lives.
You want to review activity or run reports (via Activity).

Where in navigation + Related tabs

Top Navigation is global, but it points you into the rest of the system.

Home (dashboard) → see The Home Screen tab for details.
Hey! → ties into “Pro Tips” (Don’t Forget, announcements).
Pings → direct conversations, separate from projects.
Activity → recent changes + reporting entry points.
Find → global search with filters.

Mental model / Flow

Think of Top Navigation as your universal remote: it doesn’t do project work itself, but it gets you to the right place instantly.

Home is “where to start.”
Hey! is “what’s new.”
Pings are “direct messages.”
Activity is “what changed + reports.”
Find is “recover anything.”
Lineup is “project timeline view” (optional/enableable).

Objects & Terms

A few Top Navigation-specific terms you’ll hear in teams.

Launchpad: the Basecamp logo top-left; used to switch accounts.
Lineup: a timeline view of projects in play now/next (if enabled).
Hey!: notifications and announcements stack.
Activity: account activity feed + access to reports.
Find: search across the account with filters (by person/project/type).

Core jobs-to-be-done

These are the top things beginners use Top Navigation for (and they work the same everywhere).

Get back to Home when you’re deep inside a project/tool.
Check Hey! for new items that need your attention.
Ping someone for a quick 1:1 question (not project discussion).
Review Activity when you need to understand recent changes.
Find a specific item by keywords, then narrow by project/person/type.

Happy path workflow #1 — Find a missing item fast

Do this when you remember keywords but not the project/tool.

1Click Find in the top nav.
2Type a specific keyword (project name, file name, phrase from the post).
3Narrow results by project if you recognize where it belongs.
4Filter by person if you know who posted it.
5Filter by type (message, to-do, doc, etc.) if results are too broad.
6Open the item and use its context to navigate to the project/tool.

Expected outcome: You locate the correct item without asking in chat or guessing through projects.

Happy path workflow #2 — Keep Hey! under control

Do this once or twice a day so notifications don’t pile up.

1Open Hey! from the top nav (look for the badge).
2Scan items: read what’s new, then decide what needs action.
3If it needs action, open it and create/assign a to-do as the next step.
4If it’s “read later,” set it aside using Hey!/Don’t Forget behavior (when available).
5Return to Hey! and clear what you’ve handled.

Expected outcome: Hey! stays a useful inbox rather than a scary backlog.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Need to talk to one person quickly?	Use Pings for direct messages.	If it’s project work, post in the project tool so everyone can see it.
Need an update everyone should see?	Post it as a message/doc in the relevant project.	Avoid sending it as a Ping unless it’s truly private.
Need to understand what changed?	Use Activity to review updates and reports.	If you just need “what’s new for me,” use Hey!.
Not sure where something is?	Use Find first.	If Find fails, ask the project lead what tool they posted it in.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Using Pings for decisions — Decisions belong in projects so they’re searchable and visible.
Ignoring the Home button — Home is the fastest reset when you feel lost.
Not filtering Find results — Use filters to reduce noise and get to the right item quicker.
Letting Hey! pile up — Treat Hey! like an inbox: process a little every day.
Assuming Lineup is mandatory — Lineup is useful, but optional—enable only if your team needs a timeline.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Top Navigation
What Home, Launchpad, Lineup, Pings, Hey!, Activity, and Find do.
The Home Screen
How pinned projects, directory, schedule and assignments work.
Basecamp Pro Tips
Keyboard shortcuts, jump menu, focus mode, announcements.

The Home Screen

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Home shows pinned + recent projects plus schedule and assignments previews.
Admins can add/change the company logo from Home.
Create projects from Home; rename/archive/delete via project menus.
Use the project directory view to filter active/pinned/archived/etc.

Purpose / Outcome

Home is the starting dashboard for your company account: projects, quick actions, and your personal snapshots live here.

Add/change company logo (admins).
Create a project and choose tools/access/people.
Pin and rearrange projects for your personal dashboard.
Open directory view to browse/filter/search all projects.
Jump into your full schedule or assignments when needed.

Who is this for + When to use

Use this whenever you log in, whenever you need to create a project, or when you want a fast overview of what’s happening.

You’re starting the day and need to pick your top projects.
You want to create, rename, archive, or delete a project.
You need to find a project in the directory (active vs archived).
You want to see “Your Schedule” and “Your Assignments” at a glance.

Where in navigation + Related tabs

Home is accessed from Top Navigation and connects to personal and project spaces.

Top Navigation → Home button always brings you here.
My Stuff → deeper personal views (Assignments, Schedule, Drafts, etc.).
Projects → the work itself; Home is the entry point.
Teams and HQ → many teams pin HQ/team spaces for quick access.

Mental model / Flow

Home is a dashboard made of cards: project stacks, pinned projects, recently visited projects, plus side widgets for schedule and assignments.

Pinned projects are personal (your order reflects your priorities).
Recently visited helps you continue where you left off.
Schedule preview shows upcoming events you’re part of; full view is in My Schedule.
Assignments preview shows what’s due/assigned; full view is in My Assignments.

Objects & Terms

Home-specific concepts that show up a lot in onboarding.

Pinned projects: projects you choose to keep on Home for quick access.
Project directory: “View all in a list” to browse and filter all projects.
Your Schedule: a preview widget; full calendar is My Schedule.
Your Assignments: a preview widget; full task list is My Assignments.

Happy path workflow #1 — Add or change your company logo

Do this early so your account feels like your company (and people trust they’re in the right place).

1From Home, hover over your account/company name area.
2Click the “Replace your logo” option (admins only).
3Drag a PNG/JPG/GIF into the upload area (PNG with transparent background recommended).
4Click Save.
5To change later, hover the current logo, click the small gear icon, and replace it or show company name instead.

Expected outcome: Your Home screen shows the correct company branding (logo or name).

Happy path workflow #2 — Use the project directory to find the right project

Do this when you have many projects or when you’re hunting for an older one.

1On Home, click “View all in a list” to open the project directory.
2Use filters to switch between active, pinned, client projects, all-access projects, and inactive (archived/trashed).
3Use the search bar to search by project title or description.
4Open the correct project from the results.
5If it’s something you’ll use often, pin it when you return to Home.

Expected outcome: You can reliably find any project (active or inactive) without scrolling through the dashboard.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Need quick access every day?	Pin the project and place it near the top.	Leave it unpinned if you only visit occasionally.
Project finished?	Archive it to keep history but prevent edits.	Delete it only when you truly need it removed.
Need to see assignments due soon?	Use Your Assignments preview, then open full My Assignments.	If you don’t need task view, stay on Home and focus on project updates.
Need a new workspace?	Create a new project from Home.	If it’s repeatable work, start from a template instead.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Treating pinned projects as shared order — Pinned/reorder is personal; don’t expect others to see the same arrangement.
Creating too many projects too early — Start with the smallest set that matches how you work this month.
Deleting instead of archiving — Archive preserves history and is reversible; deleting is more destructive.
Not using directory search — Use the directory search instead of scrolling through Home.
Ignoring admin-only logo changes — If you can’t add a logo, ask an admin—Home UI will clarify that.

Checklist: pre-check + post-check

Pre-check

At least 1–3 important projects are pinned.
Pinned projects are arranged by priority.
You know where “View all in a list” is.
You can open full My Assignments and My Schedule from Home.
Admins have set company logo/name.

Post-check

You can find any project via directory filters/search.
You understand archiving vs deleting.
Home feels like a useful dashboard, not a cluttered list.
Your Assignments preview reflects your actual priorities (Up Next).
You can return to Home instantly from anywhere.

Practice lab (5–15 min)

Goal: Make Home useful in under 10 minutes.

Steps

Pin your top 3 projects.
Reorder them so #1 is the project you’re working on today.
Open directory view and filter to inactive projects (archived/trashed) once.
Search the directory for a keyword from a project description.
Open Your Assignments and move one task into Up Next.

Verify you did it right

Home shows your top 3 projects in your chosen order.
You can find projects using directory filters + search.
Your Up Next contains at least one prioritized task.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

The Home Screen
Logo, creating projects, project directory, schedule + assignments widgets.
Projects
Project creation details and project settings (archive/delete/rename).
My Stuff
My Assignments and My Schedule deeper behavior.

My Stuff

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

My Stuff is your personal hub: assignments, bookmarks, schedule, drafts, recent activity, boosts.
Up Next is private to you (your personal priority order).
My Schedule is read-only; events are created from a project schedule.
You can subscribe My Schedule to Google Calendar/iCal/Outlook.

Purpose / Outcome

My Stuff is your personal “control center” across the whole account — the fastest way to see your responsibilities and personal shortcuts.

See everything assigned to you (and reorder with Up Next).
Bookmark important items for quick retrieval later.
Review your schedule and upcoming dated assignments.
Recover drafts you haven’t published yet.
See your recent activity timeline (and even run it for others).

Who is this for + When to use

Use this whenever you want to answer: “What should I do next?” or “Where’s that thing I saved?”

You start the day and want your personal task list.
You’re juggling many projects and want one cross-project view.
You want to prioritize tasks without changing project-level ordering.
You need to find drafts you started but didn’t publish.
You want a “what have I done lately?” report.

Where in navigation + Related tabs

My Stuff lives in the top navigation area and complements Home and Projects.

Home has previews for assignments and schedule; My Stuff has the full views.
Top Navigation provides Find; My Stuff provides personal shortcuts (type “my” in jump menu).
Projects is where tasks/events originate; My Stuff aggregates them for you.

Mental model / Flow

Think of My Stuff as a personal lens on your account: it doesn’t create new project work by itself, but it collects the work that involves you.

Tasks and dates originate in projects; they appear here because you’re assigned or invited.
Up Next is personal ordering — visible only to you.
Bookmarks are personal — your saved list doesn’t affect others.
Schedule subscription bridges Basecamp dates into external calendars.

Objects & Terms

Key elements inside the My Stuff menu.

My Assignments: everything assigned to you; includes Up Next and dated views.
Up Next: your private priority list (reorder via drag-and-drop).
My Bookmarks: items you bookmarked from ••• menus.
My Schedule: events you’re part of + upcoming dated to-dos; created from project schedules.
My Drafts: unpublished messages/docs you can resume or trash.
My Recent Activity: timeline of what you did, broken down by project.
My Boosts: reactions/boost-related area (if used in your account).

Core jobs-to-be-done

Most newbies use My Stuff for these repeatable jobs.

Prioritize today’s tasks without re-editing project plans.
Collect “reference” items (briefs, docs, key threads) via bookmarks.
Sync work dates into Google Calendar/iCal/Outlook via subscription.
Recover and publish drafts safely.
Generate a simple activity report for yourself or someone else.

Happy path workflow #1 — Build your Up Next list

Use this when you have many assignments and need a personal priority order.

1Open My Stuff → My Assignments.
2Scan what’s due soon vs newly assigned.
3Click the ↑ arrow beside an item to move it into Up Next.
4Drag and drop items inside Up Next to set your order.
5If an item no longer matters, click ↓ to move it back.
6Check Home’s “Your Assignments” widget to confirm it reflects Up Next.

Expected outcome: You have a clear, private priority list (Up Next) that you can work from.

Happy path workflow #2 — Subscribe My Schedule to your calendar

Use this if you live in Google Calendar/Outlook and want Basecamp dates there too.

1Open My Stuff → My Schedule.
2Click Subscribe on the My Schedule page.
3Choose Google Calendar or the iCal/Outlook option.
4Follow the subscription steps from the page you’re shown.
5Confirm you see Basecamp events and dated assignments in your calendar.
6Remember: you can’t add events from My Schedule; create them inside a project Schedule.

Expected outcome: Your external calendar shows Basecamp events/dates so you don’t miss deadlines.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Need to prioritize tasks?	Use Up Next (private).	If priorities must be shared, coordinate in the project’s plan/to-do structure instead.
Need a new event?	Create it in a specific project Schedule.	Don’t look for an “add event” button in My Schedule (it’s not there).
Want fast access later?	Bookmark the item from its ••• menu.	Avoid copying links into random docs—bookmarks are designed for this.
Need proof of work?	Use My Recent Activity to review what you did.	If you need team-wide reporting, use Activity/Reports instead.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Thinking Up Next is shared — Up Next is only visible to you; others still see assignments organized by project.
Trying to add events in My Schedule — Events are created from a project Schedule, then appear in My Schedule.
Bookmarking everything — Bookmark only high-value reference items; otherwise it becomes noise.
Leaving drafts to rot — Review My Drafts weekly and publish or trash intentionally.
Ignoring the weekly assignments email — If it’s useful, keep it; if it’s noise, turn it off from the email or the page.

Checklist: pre-check + post-check

Pre-check

You know where My Assignments lives.
You can add at least 3 items to Up Next.
You can open My Bookmarks and understand they’re private.
You can find My Drafts.
You can open My Schedule and see upcoming dates.

Post-check

Home’s assignments widget reflects Up Next priorities.
You can subscribe to My Schedule (optional).
You can explain why events must be created in project schedules.
You can run My Recent Activity when needed.
You aren’t overwhelmed because you review/clean weekly.

Practice lab (5–15 min)

Goal: Turn My Stuff into a daily habit.

Steps

Open My Assignments and move 3 tasks into Up Next.
Reorder Up Next so the first item is the one you’ll do today.
Bookmark one important project doc or message.
Open My Drafts and either publish or trash one old draft (if any).
Open My Recent Activity and scan the last 7 days.

Verify you did it right

Up Next contains 3 tasks in your preferred order.
A new bookmark appears in My Bookmarks.
You can explain what drafts are and where to find them.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

My Stuff
Assignments, bookmarks, schedule, drafts, recent activity, boosts.
The Home Screen
Where schedule/assignments previews link into My Stuff.
Basecamp Pro Tips
Jump menu and keyboard shortcuts to reach My Stuff faster.

Projects

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Projects are the heart of Basecamp — where announcements, chat, tasks, deadlines, and files live.
You can set up tools per project; turning a tool off affects everyone in the project.
You can add multiple instances of tools (multiple chats, message boards, schedules, etc.).
Projects can be Invite-only or All-access; finished projects can be archived.

Purpose / Outcome

Projects are where work actually happens in Basecamp. A good project has clear purpose, the right tools, and the right people.

Create projects for major initiatives, departments, or clients.
Choose project access (Invite-only vs All-access).
Enable only the tools your project needs; rename/organize tools for clarity.
Invite people and control who participates.
Use project settings to keep projects tidy (edit, archive, delete).

Who is this for + When to use

Use this when starting any new initiative or when an existing project feels messy.

Launching a new internal initiative (campaign, release, event).
Managing client work with shared updates and tasks.
Creating a team space for ongoing coordination.
Refactoring an old project: tools, membership, naming, and structure.

Where in navigation + Related tabs

Projects are reachable from Home, Find, and the Jump menu; they connect directly to Teams and HQ and My Stuff aggregation.

Home → create projects + pin projects.
Find → search for content across projects.
My Stuff → your assignments and dates originating from projects.
Teams and HQ → projects used as department/team spaces.

Mental model / Flow

A project is a container with tools. Choose tools based on how you actually communicate and execute work, then keep usage consistent.

Start: define purpose + access + people.
Design: pick tools and name them clearly (e.g., “Announcements”, “Weekly Planning”).
Operate: post updates in durable tools; assign tasks with owners; track dates in schedules.
Close: archive finished projects for view-only history.

Objects & Terms

Project setup includes tools, access modes, and management actions.

Invite-only project: only invited people can access.
All-access project: discoverable; share link so team can join.
Set up tools: toggle tools on/off; changes apply to everyone in the project.
Doors: links to external services (e.g., GitHub, Zoom, Google Drive).
Activity timeline: project-level timeline of updates made in that project.
Multiple tools: you can add more than one chat/message board/schedule/etc.

Core jobs-to-be-done

Common repeatable project work patterns.

Spin up a new project with a consistent toolset (or template).
Remove unused tools to reduce confusion.
Add multiple tools for different streams (e.g., “Bugs Chat” + “General Chat”).
Invite people and adjust participation (team member vs client when relevant).
Clean up and archive when the work is done.

Happy path workflow #1 — Create a minimal, clear project

Use this to avoid the “everything everywhere” problem.

1From Home, create a new project and name it after the initiative.
2Write a description that states purpose + owner/lead + success criteria.
3Choose Invite-only or All-access based on visibility needs.
4Pick the smallest set of tools needed this week (you can add later).
5Create an “Start here” message that explains how to use the project.
6Create a to-do list called “Next actions” and assign 5–10 items.
7Invite the people who will actually do the work.

Expected outcome: A project exists that’s easy to understand, easy to use, and not overloaded with tools.

Happy path workflow #2 — Tune your tools (on/off, rename, add multiples)

Use this when the default tool set doesn’t match how you work.

1Open the project and click the ••• menu.
2Choose “Set up tools”.
3Toggle off tools you don’t need (changes affect everyone).
4If needed, click “+ Add another” to create a second instance of a tool.
5Rename tools to match how the team uses them (e.g., “Release Chat”, “Customer Q&A”).
6Reorder tools so the most-used are at the top.
7Add Doors to external services you use daily (GitHub/Zoom/Drive/etc.).

Expected outcome: Your project tools match real workflows; teammates know where to post and what to ignore.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Should this be All-access?	Choose All-access for company-wide visibility and easy joining.	Choose Invite-only for sensitive work or small groups.
Too many conversations?	Create multiple chat rooms for different streams.	Keep one chat room if the project is small to avoid fragmentation.
Tasks are unrelated?	Add a second to-do tool (separate streams).	Keep one to-do tool and use lists/sections if it’s manageable.
Project completed?	Archive for view-only history.	Delete only if you truly need it removed.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Leaving tools unnamed/generic — Rename tools so new people know what belongs where.
Turning off a tool without warning — Changes affect everyone; announce tool changes in a message first.
Using multiple tools without a rule — If you add multiple chats/schedules, document which is for what.
Not using Doors for external services — Doors reduce context-switching and keep links consistent.
Not archiving old projects — Archive completed projects so active work is easier to navigate.

Checklist: pre-check + post-check

Pre-check

Project name and description clearly state purpose + owner.
Correct access mode chosen (Invite-only/All-access).
Only relevant tools are enabled.
At least one welcome/start-here message exists.
Initial to-do list exists with owners.

Post-check

People know where to post updates vs tasks.
Tools are renamed and ordered logically.
Any extra tool instances have clear purpose.
External services are linked via Doors (if needed).
Project has an archiving plan when done.

Practice lab (5–15 min)

Goal: Refactor a messy project into a clean one.

Steps

Pick one existing project that feels cluttered.
Write/refresh the project description (purpose + lead + how to use).
Open Set up tools and toggle off 1–2 unused tools.
Rename 2 tools to be more specific.
Reorder tools so the top 3 are the ones you use weekly.
Add one Door to an external service you use with the project.

Verify you did it right

Project tools list is shorter and clearer.
Tool names match the team’s vocabulary.
A new teammate could guess where to post without asking.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Projects
Create projects, set up tools, add multiple tools, invite people, project settings.
The Home Screen
Creating, archiving, deleting, renaming projects; directory view.
Teams and HQ
Using projects as team and HQ spaces.
Permissions
User types: employee, outside collaborator, client (account-level).

Teams and HQ

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

You can use projects as company HQ spaces and as team spaces—not just “client projects.”
HQ is often an All-access project for company-wide announcements, files, and events.
Teams are projects customized (tools renamed/removed) for each department.
Keep HQ as the source of truth for company-wide information.

Purpose / Outcome

This section helps you set up Basecamp like an operating system for your company: one HQ plus a set of team spaces and work projects.

Create an HQ project for company-wide announcements and key links.
Create team projects (Support, Sales, Engineering, etc.) for ongoing coordination.
Customize tools per team so each space matches how that team works.
Keep department work out of all-company channels unless it matters to everyone.

Who is this for + When to use

Use this once you have more than a handful of projects, or when you want a tidy place for company operations beyond project work.

You want a “company hub” separate from individual initiatives.
You need a home for announcements, policies, files, and events.
You want each department to have a consistent collaboration space.
You want new hires to know where to look for company-wide info.

Where in navigation + Related tabs

Teams and HQ are implemented as projects, then surfaced through Home and Top Navigation.

Home → pin HQ and key team spaces for everyone (or encourage it).
Projects → HQ/team spaces are configured like any other project (tools, people).
Top Navigation → Hey! carries announcements/notifications from HQ.
My Stuff → assignments/dates created in team spaces flow into personal views.

Mental model / Flow

If you’re unsure where something belongs, the simplest rule is: company-wide info goes to HQ; department coordination goes to team space; deliverables go to initiative projects.

HQ: one place for “everyone needs this.”
Team space: one place for “this department needs this.”
Work project: one place for “this initiative/client needs this.”
Avoid duplicating posts across spaces—link back to the source instead.

Objects & Terms

This approach uses projects in different roles.

HQ project: often All-access; used for announcements, links, events, and shared files.
Team project: a project configured as a department hub; tools renamed to match team workflow.
Pinned projects: teams often pin HQ and their department space for quick access.
Project tool customization: rename/add/remove tools to fit each team.

State machine / Lifecycle

HQ and team spaces are long-lived projects; lifecycle is mostly about keeping them maintained rather than closing them.

HQ/team projects should stay active continuously.
Archive old announcement threads or close comments when topics are settled (if your account uses that).
Review tools quarterly and remove the ones no one uses.

Happy path workflow #1 — Create a company HQ

Use this when you want one official place for company-wide updates and resources.

1Create a new project named “HQ” (or “Company HQ”).
2Set it to All-access so everyone can find/join it (if that fits your company).
3Choose tools: a message board for announcements, a place for links/files, and a schedule for company events (as needed).
4Post a welcome message: what belongs here, and what doesn’t.
5Pin HQ on Home and encourage others to pin it too.
6Create a “Start here” doc/message with key links (policies, onboarding, tools).

Expected outcome: Everyone has one reliable place to find company-wide information.

Happy path workflow #2 — Create a team space that actually fits the team

Use this when a department needs ongoing coordination outside of specific projects.

1Create a new project named after the team (e.g., “Engineering Team”).
2Write a description: mission + team lead + how to use this space.
3Open Set up tools and turn off tools the team won’t use.
4Rename tools to match the team’s language (e.g., “Weekly Planning”, “Incidents”).
5Add Doors for the team’s daily systems (repo, runbooks, dashboards).
6Invite the team members; keep membership focused to avoid noise.

Expected outcome: The department has a home for coordination that doesn’t pollute company-wide channels.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Where should an announcement go?	HQ if it affects most/all employees.	Team space or a specific project if it’s scoped.
Should HQ be All-access?	Yes if you want broad discoverability and self-serve joining.	No if company policy requires invite-only access.
Need long-term reference docs?	Put them in HQ and keep them updated.	Avoid scattering policies across many projects.
Team is overwhelmed by tools?	Turn off unused tools and rename the rest.	Don’t keep empty tools “just in case.”

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Using HQ for everything — HQ should stay high-signal; team work belongs in team spaces or projects.
No posting rules in HQ — Write a “what belongs here” post so people don’t guess.
Not pinning HQ — If HQ isn’t easy to access, people won’t use it.
Duplicating announcements — Post once in HQ and link to it elsewhere.
Forgetting to maintain links — Review HQ links quarterly; stale links destroy trust.

Checklist: pre-check + post-check

Pre-check

HQ project exists (name is obvious).
HQ has a clear welcome/start-here post.
HQ has the minimum tools needed.
Key links/resources are collected in one place.
Team spaces exist for major departments (if needed).

Post-check

People know: HQ vs Team space vs Work project.
HQ remains high-signal (not spammy).
Tools are customized per team (renamed/removed).
Doors link to critical external systems.
Quarterly maintenance plan exists (links/tools/structure).

Practice lab (5–15 min)

Goal: Stand up an HQ in under 15 minutes.

Steps

Create an HQ project (All-access if appropriate).
Turn on only 2–3 essential tools.
Write a welcome message with: what belongs here + posting rules.
Add 5 key links as a starter (handbook, PTO, support, tooling, onboarding).
Pin HQ and reorder it to the top of your Home.

Verify you did it right

HQ is discoverable and easy to access.
A newcomer can answer “where do I find company info?” in one click.
HQ does not have unused/empty tools cluttering it.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Teams and HQ
Using projects as HQ and team coordination spaces.
Projects
How to rename/add/remove tools to customize spaces.
The Home Screen
How to pin and rearrange important spaces.

Training Your Team

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Use the Learn Center and Help Guides to train basics quickly.
Start with an “Intro” walkthrough, then teach people where to post what.
Live classes can help with setup and rollout questions.
Support is available when you’re stuck.

Purpose / Outcome

This section helps you roll Basecamp out to real humans—so it sticks beyond the first week.

Pick a small set of training resources for beginners.
Create a shared vocabulary: projects, tools, Hey!, My Stuff.
Teach “where to post what” with examples, not theory.
Run a short rollout plan: pilot → expand → standardize templates.
Know where to get help (support + live classes).

Who is this for + When to use

Use this when onboarding new hires, migrating teams into Basecamp, or resetting habits after messy usage.

You’re the admin/ops person leading rollout.
You’re a team lead onboarding a department.
You’re adding clients/outside collaborators and need clear rules.
You want consistent usage across many projects.

Where in navigation + Related tabs

Training happens outside the UI too, but should always reference the actual navigation people use.

Start trainees on Home + Top Navigation so they don’t get lost.
Teach My Stuff early so people know “what to do next.”
Use one pilot project to teach Projects + tools in context.
Share Pro Tips after week 1 (shortcuts, jump menu, focus mode).

Mental model / Flow

The easiest training pattern: teach navigation first, then teach posting rules, then teach habits.

Orientation: Home, Hey!, Find, My Stuff.
Posting: “durable info goes to messages/docs; actions go to to-dos/cards.”
Habits: daily Hey! + My Assignments; weekly cleanup and planning.
Reinforcement: templates and a short “how we use Basecamp” post.

Core jobs-to-be-done (rollout tasks)

Concrete rollout jobs you can assign to a rollout owner.

Create a pilot project and run real work through it for 1–2 weeks.
Write a one-page “How we use Basecamp here” guideline in HQ.
Set tool naming conventions (Announcements, Planning, Requests, etc.).
Define client/external collaborator rules if you work with outsiders.
Collect feedback and simplify (turn off tools that confuse people).

Happy path workflow #1 — 1-week rollout plan

A practical rollout that avoids overwhelming the team.

1Day 1: Set up HQ + one pilot project; invite pilot team.
2Day 2: Teach navigation (Home, Hey!, My Stuff, Find) in 15 minutes.
3Day 3: Teach posting rules with real examples from the pilot project.
4Day 4: Assign work in to-dos; review My Assignments and Up Next.
5Day 5: Do a 20-minute retro: what felt confusing? remove/rename tools.
6Week 2: Expand to a second team/project using a template.

Expected outcome: Team uses Basecamp for real work, with less confusion and fewer “where do I post?” questions.

Happy path workflow #2 — Teach “where to post what”

Do this as a short workshop using one real project as the example.

1Pick a real project and list 6 examples (announcement, decision, task, file, question, status update).
2For each example, choose the correct tool and explain why.
3Create a “Posting map” message in the project: what belongs where.
4Have each teammate post one sample item into the correct tool.
5Review Hey! together so they see how notifications connect to posts.
6End by showing Find: how to retrieve anything later.

Expected outcome: Everyone shares the same mental model for where information and actions belong.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Training format?	Live walkthrough if the team is new to tools.	Self-serve docs/videos if the team is experienced and needs only references.
Rollout size?	Start with a pilot team/project to iron out habits.	Roll out to everyone once the pilot is stable.
Tool complexity?	Keep a minimal tool set at first.	Add more tools only when there’s a real need.
Need outside help?	Use Basecamp live classes or support.	If internal champion exists, document and reuse their playbook.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Training too much at once — Teach navigation first, then one tool at a time using real work.
No written posting rules — Write a short “what belongs where” post in HQ and key projects.
Not using a pilot — Pilots surface confusion early—before you scale it.
Leaving tool names generic — Rename tools so beginners can self-correct.
Skipping reinforcement — Templates + weekly habits are what make the change stick.

Checklist: pre-check + post-check

Pre-check

HQ exists and contains rollout notes.
One pilot project is running real work.
Posting rules are written in the pilot.
At least one champion is identified.
Support/resources are known by the rollout owner.

Post-check

Team members can explain Home/Hey!/My Stuff/Find.
Team posts durable info in messages/docs and actions as to-dos.
Confusing tools are removed/renamed.
A template exists for repeatable projects.
New hires have a clear onboarding path.

Practice lab (5–15 min)

Goal: Run a 10-minute micro-training with a teammate.

Steps

Open Home and point out pinned projects + assignments preview.
Open Hey! and explain badges and reading/processing notifications.
Open My Assignments and move 1 item into Up Next.
Use Find to search a keyword and filter to a project.
End by showing where to post a decision (message/doc) vs a task (to-do).

Verify you did it right

Teammate can navigate without getting lost.
Teammate can pick the right place to post common items.
Teammate knows how to find items later.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Training Your Team
Learn Center, help guides, intro video, live classes, and support path.
Mastering Basecamp (Learn Center)
Free tutorials and quick tips for core tools.
Getting Started with Basecamp
Suggested reading order for newbies.

Basecamp Pro Tips

Newbie-focused, based on Basecamp Help Center “Getting Started” navigation.

Quick scan

3–5 bullets

Use the Jump menu to navigate instantly (Cmd/Ctrl + J).
Keyboard shortcuts speed up daily navigation (My Stuff, Find, etc.).
Change participation type to mute noisy projects while keeping access.
Use focus mode, themes, and small UI tricks to stay comfortable.

Purpose / Outcome

Pro Tips help you move faster, reduce noise, and keep your attention focused once the basics are working.

Navigate faster using the Jump menu and keyboard shortcuts.
Reduce notification overload by adjusting participation type.
Manage comment-thread notifications by subscribing/unsubscribing.
Use focus mode and themes to stay comfortable during heavy work.
Switch accounts quickly if you’re in multiple Basecamp accounts.

Who is this for + When to use

Use this after your first week (or anytime Basecamp feels “too busy”).

You’re drowning in notifications and need to control attention.
You switch between projects/accounts frequently.
You want faster navigation without clicking around.
You want to keep discussions tidy (close comments when done).

Where in navigation + Related tabs

These tips mostly enhance Top Navigation and personal daily flows.

Jump menu helps you reach Projects, People, and ‘my’ pages quickly.
Keyboard shortcuts connect to My Stuff and Find.
Participation type affects how Hey! notifies you about a project.
Account switching affects Launchpad usage in Top Navigation.

Mental model / Flow

Pro Tips are “levers” you can pull to change speed and noise without changing how projects are structured.

Speed levers: jump menu, shortcuts, account switching.
Noise levers: participation type, thread subscribe/unsubscribe, close comments.
Comfort levers: focus mode, themes, emoji shortcuts.

Core jobs-to-be-done

Repeatable power-user jobs.

Jump to a project/person instantly with the jump menu.
Open My Stuff or Find without hunting through menus.
Mute project noise while staying able to access content.
Follow or unfollow a comment thread based on relevance.
Keep long threads readable with “Back to top” behavior.

Happy path workflow #1 — Use the Jump menu like a pro

Do this when you want to move around Basecamp without clicking through Home.

1Press Cmd+J (Mac) or Ctrl+J (Windows/Linux).
2Start typing a project name or a person’s name.
3Use arrow keys to select the right result, then press Enter.
4To jump to personal pages, type “my” to reach assignments/bookmarks/drafts/activity.
5Repeat whenever you feel yourself “clicking around” too much.

Expected outcome: You can reach any common destination in seconds without leaving the keyboard.

Happy path workflow #2 — Reduce noise from a project (without losing access)

Use this when you’re included in a project but don’t need constant notifications.

1Open the project you want to quiet down.
2Open the ••• menu near the project name.
3Choose the option to switch participation to “just follow” (muted notifications).
4Keep working normally; you’ll still be notified if you’re @mentioned or assigned a task.
5Re-enable normal participation later if you need full notifications again.

Expected outcome: You keep access to the project but stop getting unnecessary notifications.

Decision points

Use this as a quick A/B chooser so you don’t overthink setup.

Situation	If A…	If B…
Too many notifications from a project?	Switch to “just follow” to mute noise.	If you’re responsible for work there, keep full participation.
Need updates on a specific thread?	Subscribe to that comment thread.	Unsubscribe if you’re no longer involved.
Need faster navigation?	Use Jump menu + shortcuts daily.	If you prefer clicking, at least learn Find + Home reset.
Switching accounts often?	Use Launchpad/account switching shortcuts.	If you rarely switch, ignore this tip.

Common mistakes (and how to avoid them)

These are the usual “newbie traps” when teams move from email/spreadsheets into Basecamp.

Muting the wrong project — Don’t mute projects you own; mute ones where you’re only occasionally involved.
Staying subscribed to every thread — Unsubscribe from threads once decisions are done.
Ignoring keyboard shortcuts — Learning 2–3 shortcuts pays off quickly.
Over-customizing themes early — Get workflow right first; then tune comfort.
Leaving comments open forever — Close comments on finished topics to prevent zombie conversations.

Checklist: pre-check + post-check

Pre-check

You can open Jump menu with Cmd/Ctrl+J.
You know at least 2 shortcuts (My Stuff, Find).
You know how to change participation type.
You know how to subscribe/unsubscribe threads.
You can switch accounts when needed.

Post-check

You reduced noisy notifications without missing important ones.
You can navigate to any project/person in <10 seconds.
You keep discussions tidy (close comments when done).
You can use focus mode when deep-working.
Your workflow feels faster and calmer.

Practice lab (5–15 min)

Goal: Become noticeably faster in 10 minutes.

Steps

Use Jump menu to open 3 different projects without clicking Home.
Use Find shortcut (Cmd/Ctrl + /) once to search a keyword.
Open My Stuff shortcut (Cmd/Ctrl + ;) once and check assignments.
Pick one project you’re only observing and switch to “just follow”.
Subscribe to one thread you care about; unsubscribe from one you don’t.

Verify you did it right

You can navigate keyboard-first.
You have one muted project that’s no longer noisy.
Your thread subscriptions reflect what you actually care about.

Official docs links

Short labels only (no raw URLs). Use these to confirm details or go deeper.

Basecamp Pro Tips
Jump menu, shortcuts, participation type, focus mode, themes, and more.
Top Navigation
Where Find/Hey!/Activity/Pings live.
My Stuff
Where shortcuts land you for assignments/bookmarks/drafts.

Your favorites

Getting Started with Basecamp

Quick scan

Purpose / Outcome

Who this is for + When to use

Where in navigation + Related tabs

Mental model / Flow

Happy path workflow #1 — Create your first project

Happy path workflow #2 — Make Home feel like “your dashboard”

Decision points

Common mistakes (and how to avoid them)

Checklist: pre-check + post-check

Pre-check

Post-check

Practice lab (5–15 min)

Steps

Verify you did it right

Official docs links

How Basecamp Works

Quick scan

Purpose / Outcome

Who is this for + When to use

Where in navigation + Related tabs

Mental model / Flow

Objects & Terms (starter glossary)

State machine / Lifecycle

Happy path workflow #1 — Daily operating rhythm

Happy path workflow #2 — “Where should this go?” posting flow

Decision points

Common mistakes (and how to avoid them)

Official docs links

Top Navigation

Quick scan

Purpose / Outcome

Who is this for + When to use

Where in navigation + Related tabs

Mental model / Flow

Objects & Terms

Core jobs-to-be-done

Happy path workflow #1 — Find a missing item fast

Happy path workflow #2 — Keep Hey! under control

Decision points

Common mistakes (and how to avoid them)

Official docs links

The Home Screen

Quick scan

Purpose / Outcome

Who is this for + When to use

Where in navigation + Related tabs

Mental model / Flow

Objects & Terms

Happy path workflow #1 — Add or change your company logo

Happy path workflow #2 — Use the project directory to find the right project

Decision points

Common mistakes (and how to avoid them)

Checklist: pre-check + post-check

Pre-check

Post-check

Practice lab (5–15 min)

Steps

Verify you did it right

Official docs links

My Stuff

Quick scan

Purpose / Outcome

Who is this for + When to use

Where in navigation + Related tabs

Mental model / Flow

Objects & Terms

Core jobs-to-be-done

Happy path workflow #1 — Build your Up Next list

Happy path workflow #2 — Subscribe My Schedule to your calendar

Decision points

Common mistakes (and how to avoid them)

Checklist: pre-check + post-check

Pre-check

Post-check

Practice lab (5–15 min)

Steps

Verify you did it right