Ekko's onboarding is intentionally short — four steps, sensible defaults on every field — but every choice you make here drives a number you will see later in Sprint Planning. This guide tells you what each field controls so you can fill it in deliberately, not blindly.

Working through it should take three to five minutes. You can hit Back at any time without losing what you typed.

Step 1 · General settings

The only choice on this step is theme.

Light: Bright background, dark text. Best for printed-feeling planning sessions or daylight rooms.
Dark: Dark background, light text. Easier on the eyes for long sessions.
System (recommended): Ekko follows your OS theme — auto-switches when your laptop does.

Step 2A · Capacity mode (the most important choice)

Sprint Planning displays each person's available work in either hours or story points. Pick the unit your team actually plans in — and pick the same one your team's estimates are in.

Hours mode

Working hours per day — your typical productive hours. Many teams set this to less than 8 because humans take breaks, context-switch, and attend meetings that should not count as story work.
Default tax hours per week — non-project overhead (meetings, admin, support) baked into capacity. Default for everyone, can be overridden per person in Team Management.
Best for time-based estimates (original estimate / remaining estimate in Jira).

Story points mode

Story points per day — how many points a typical person on your team finishes in a working day.
Default tax story points per week — same idea as tax hours, but in points.
Best for points-based teams. Capacity, time-off, and tax all switch to points so the math is consistent.

Step 2B · What is the "tax"?

Tax is Ekko's name for non-project overhead — the work that eats into someone's week but is not a sprint ticket. Standing meetings, on-call shifts, support rotations, code review, mentoring, and so on.

Capacity is computed as:

On step 2 you set the default tax (per week, in hours or points). It applies to everyone on every project. Individuals get overrides later in Team Management — useful for engineering managers, on-call rotations, or part-time contractors.

Step 2C · Default board and business days

Default sprint board (optional) — when you set this, Sprint Planning opens directly on this board's most recent sprint instead of making you pick. Great for teams who plan on the same board every two weeks.

Business days — which days count as working days for capacity math. Defaults to Mon–Fri. Move them around if your team works Sun–Thu or has a four-day week.

Step 3 · Team setup (optional)

This step lets you seed a project's team list during onboarding so capacity, filters, and the team-only summary view all work the moment you finish.

Pick the project from the dropdown (populated from every board you can see).
Search for Jira users in that project. Pick as many as you want.
Or click Skip — you can do this any time in Team Management.

Step 4 · Review

The review screen plays back everything you chose. Hit Back to fix anything, or Complete Setup to save and land on the home dashboard.

Behind the scenes, three things happen on Complete:

Org settings (business days) are written for your whole Jira site.
User settings (theme, capacity mode, hours/points, tax, default board) are written for your account.
If you added team members, they are bulk-added to that project's team and onboarding is flagged as complete.

Re-running onboarding later

Process changed? Promoted? Switched from hours to points? Open Settings → Advanced → Reset Onboarding. The wizard reappears on the next page load with your current values pre-filled, so you can step through and adjust the bits that matter.