33 questions, answered straight

Running client delivery — projects, people, time, and the reporting that keeps clients informed. It is aimed at teams who are answerable for dates: agencies, studios, and in-house delivery orgs.

Worksynk ships as modules, and most are off by default even when your plan covers them. A workspace owner or admin turns them on under Settings → Modules. If a settings page looks empty, that is almost always the reason.

Only the workspace owner, since enabling one affects what the account is billed.

Disabling a module hides its interface and blocks its endpoints, but does not delete your data. Turn it back on and your policies, budgets, or SLA configuration are where you left them.

Yes. Connect Jira, Asana, Azure DevOps, or Zoho and import a project — issues arrive as tasks with their status and assignee mapped. Linked projects keep syncing, so a team mid-migration can work in both for a while.

Yes. Five statuses ship by default and you can rename, recolour, reorder, or archive any of them and add your own under Settings → Statuses. Velocity and reporting read from status categories, so the numbers keep working after you change the labels.

No. Sprints suit teams working to a cadence who care about throughput; milestones suit dated outcomes a client is waiting for. Plenty of teams use one and not the other — both are modules you can leave off.

That is the intent. Timers run against the work item, timesheets split billable from unbilled, and timer security settings exist specifically to keep the hours honest enough to bill.

Set a recurrence rule instead of recreating the task. The next instance appears on schedule, and editing the rule changes future instances rather than the history.

No, and the product is explicit about this. It is a decision aid computed from your data. A low score is a prompt to look at something, not a verdict on whether the project will land.

Overdue work, blockers, movement through statuses, and milestone progress. Because each input is real work in the workspace, you can open the items driving a change rather than trusting a number.

Yes. The score is captured daily, so you read it as a trend. A project drifting down over a fortnight is a different conversation from one bad day.

The executive summary and workload reports are visible to owners and admins only, and depend on the Analytics module being enabled.

No. It operates inside the permissions of the person asking. If you cannot open a project, neither can the assistant on your behalf.

In the app, no — an action that changes data shows you what will happen before it runs. Over a connected MCP host it can: a write tool executes the moment it is called, with no confirmation prompt. That is why connections default to read-only, and why you should only grant write access to a host that genuinely needs it.

Claude, ChatGPT, Cursor and other MCP-compatible hosts. Each has its own setup walkthrough, and every connection can be reviewed or revoked from settings.

Usage draws on workspace AI credits. Consumption is visible in the workspace, so spend is something you can watch rather than discover.

No. The portal is a client-facing read-only view specifically so you can give visibility without consuming a workspace seat.

The portal is a persistent view of their projects with updates and approvals. A status link is lighter, for when a client just needs to see progress. An external member seat is the third option, for clients who need to participate directly.

Yes, with white-label branding — your name, colour, and logo replace ours across the surfaces your team and clients see.

Handoff packages the deliverables, captures the client's confirmation, and issues a certificate — so sign-off is a record rather than a recollection.

No. GitHub has first-class support, and there is generic git-host support for teams on something else. Both link repositories to projects so commits and pull requests attach to the work they reference.

Deliveries are signed, so your endpoint can verify the signature. Destinations are validated when you create them, and every delivery attempt is recorded so failures are diagnosable.

Yes — import jobs bring existing work across rather than asking someone to re-key a backlog.

Meetings are scheduled against a project with a join link, reminders go out beforehand, and AI follow-ups capture what came out of the call next to the work it concerns.

No — that is usually why standardisation fails. The hierarchy and the definitions stay consistent, but modules, statuses, and workflows are configured per workspace so each team keeps the parts that fit its work.

Statuses map to categories. Teams can rename, recolour, and reorder freely, and velocity and reporting continue to read from the underlying category.

Activity logs, login history, credential access logs, AI action records, and IP whitelisting — all product surfaces rather than policy documents.

Yes. SLA policies are aware of business hours and holidays, and warn you before a response or resolution target is missed rather than after.

Owners and admins only. Financial reporting also depends on the Budgets module and on rates being set for your people.

Yes, because it is computed the same way everywhere — overdue work, blockers, movement, and milestone progress — even when teams have renamed their statuses.

Yes. Risk patterns and blocker radar name the cause, and every input is real work you can open from the score.

No. It is a standing view that reads live data, which is generally the point — nobody should be assembling a portfolio slide by hand.