First week after install

This is the onboarding use case: a working board with real people on it, not a tour of every setting.

Day 1 — admin and mail

1. Sign in as the administrator created in the installer.
2. Open Settings → Global (/settings/global). Set app name, logos, default language, and (if you use it) Slack webhook.
3. Configure SMTP and send a test path you care about (password reset or a task notification).
4. Add queue cron if mail should leave the server in the background.
5. Create at least one extra user under Settings → Users if teammates will log in. Roles: Admin vs Normal, plus any custom role you add under Roles.

Until SMTP works, invites and password resets will fail silently from the user’s point of view.

Day 1 — first workspace

A fresh install has no workspace. You cannot usefully create projects until one exists.

1. Click Create (top bar) or Create New on the empty-workspace screen.
2. Name it after the company or the first client, not “Test”.
3. Choose a workspace type.
4. Optional: website and description.
5. Open Invite Workspace members and add the users who should see this work. Users must already exist under Manage Users.

Details: Workspaces.

Day 2 — first project and lists

1. Create → Create Project. Pick a background, a clear name, the workspace, and a short scope in the details field.
2. Open the project Board.
3. Add lists that match how work actually moves, for example:
   • Backlog
   • This week
   • In progress
   • Review
   • Done
4. If every new project should start with the same columns, configure pre-made boards in Settings so the next project is not empty.

You can rename a list by clicking its title. Archive lists you no longer need instead of deleting history in a panic — see Board lists.

Day 2 — tasks people can finish

Add a handful of real tasks, not “Task 1”. For each:

• Assign someone in the workspace
• Set a due date if it has one
• Add a checklist if the card would otherwise hide three jobs
• Start the timer only when someone is actually working

Open the same project as Table, Calendar, and Dashboard once so the team knows those URLs exist (Views).

Day 3 — habits

• Filter the board by member or overdue (Filters).
• Star projects the team opens every morning.
• Import a starter backlog if you already have a spreadsheet (admins).
• Turn on due-task scheduler cron if you want the 08:00 reminder command to run.
• Optionally enable AI assist so people can draft descriptions and checklists instead of staring at a blank card.

After this week you should be able to answer: who owns this workspace, where does new work enter, and where do we look at time? If those three are fuzzy, fix structure before adding more projects.