Use the whole Progresso suite

1. 1Sign in with your authorized Google account.
2. 2Open Dashboard to see today’s attendance, active work, due tickets, leads needing attention, and calendar.
3. 3Open your profile to confirm your name and role. Owners can configure the agency, members, boards, weekly email, exports, and MCP in Settings.
4. 4Allow browser notifications when prompted so inactivity and checkout warnings can reach you.

Good to know: Recommended first-day setup: join the correct projects, confirm ticket assignments, enable notifications, then test check-in, start a ticket timer, and check out once.

1. 1Check in from the Dashboard or Time page when your workday begins.
2. 2Start the timer from the ticket you are actively working on. Stop or switch it when the task changes.
3. 3Add decisions, links, blockers, and progress to the ticket’s Collab area so the work remains understandable.
4. 4When moving a ticket to Done, enter a completion note. Progresso automatically adds it to Collab with your identity and timestamp.
5. 5Review AI tracking suggestions, approve correct work, correct its ticket when needed, and dismiss personal or irrelevant activity.
6. 6Clear anything in “needs a quick word from you” on Time — a timer that ran long or closed by itself just needs a note, or a trim to the real hours.
7. 7Check out when finished. If inactivity is detected, respond to the warning so work does not continue untracked.

Standard tracking

Check-in records attendance; ticket timers record the work itself. Inactivity protection warns before automatic checkout, and ends the timer at your last activity so idle time is not logged. Keep browser notifications enabled and return to the Progresso tab when warned.

Logging past work

Use Log past work on the Time page for anything the timer missed. Pick the day, then either a start and end time or a start and a length. Progresso warns if the block overlaps something you already logged, and admins can log on another member’s behalf.

Timers left running

1. 1If a timer is still running after 8 hours, Progresso closes it on the server — this works even with the browser shut, which the in-page inactivity warning cannot do.
2. 2The entry is capped and flagged, and you get a notification. It counts as logged time, but is marked as awaiting your word on it.
3. 3On Time, either confirm it with a note about what you worked on, or choose “I worked less than this” and set the real number.
4. 4Any finished entry can be trimmed later with the scissors button. The original span is kept alongside your correction, so nothing is quietly rewritten.

Good to know: Correcting your own hours down is expected and encouraged — it is the difference between reports that are roughly right and reports the team can rely on. Nothing about an adjustment is held against you.

Local AI tracker

1. 1The Mac tracker samples active application and window-title metadata; it does not capture screenshots.
2. 2Raw records and learned examples are stored privately in the local .ai-tracker-data folder.
3. 3A tiny local classifier handles familiar work and dismissed personal contexts.
4. 4Gemma starts only for ambiguous activity and unloads immediately after each answer; it is never fine-tuned.
5. 5Review suggestions on Time. Approval creates tracked time, changing the ticket teaches the correct context, and dismissal teaches non-work.

Good to know: Personal or sensitive applications can be excluded. Nothing in the AI inbox becomes a time entry until you approve it.

Use Leads as the CRM pipeline: assign ownership, update stages, schedule follow-ups, and keep notes current. Financials connects paid work and project value so owners can monitor outstanding amounts and revenue context. Access depends on role.

Owners manage recipients and rollout behavior in Settings.

MCP lets compatible AI clients work with live Progresso data under your existing account permissions. Open Settings → MCP connector, copy the generated configuration, paste it into your client, restart the client, then test by asking for the dashboard pulse or your tickets.

• Never share access tokens, refresh tokens, or service-role credentials.
• Do not commit environment files or MCP configurations containing credentials.
• MCP follows the signed-in user’s database permissions.
• Use global sign-out and issue fresh connector credentials if a token may be exposed.