Question 1

How do requests become tasks?

Accepted Answer

Inbound requests are captured in one intake queue. When a request is accepted, Plynt creates a linked task with owner, deadline, and the original context attached.

Question 2

Can I run boards, lists and sprints on the same project?

Accepted Answer

Yes. Every project supports multiple views — board, list, timeline, sprint — over the same tasks. Views don't fork the data.

Question 3

How do dependencies and blockers work?

Accepted Answer

Any task can block or be blocked by any other. Blocked work is filtered out of 'ready' views so teams focus on what's actionable.

Question 4

Where does a client's history live?

Accepted Answer

Every client has a single timeline that unifies deals, projects, tasks, invoices, and messages. There's no separate CRM to reconcile.

Question 5

Can external clients see selected work?

Accepted Answer

You can share a client-facing view with scoped visibility. Only the records you expose are readable; nothing else leaks across.

Question 6

How are roles assigned?

Accepted Answer

Roles are assigned per workspace. Admin, editor, and viewer are provided by default; custom roles can restrict modules, actions, or record types.

Question 7

What about contractors and part-time members?

Accepted Answer

Membership is per workspace with per-module access. Contractors can be scoped to a single project or client area.

Question 8

How does time-off approval work?

Accepted Answer

Requests route to the approver you configure. Approved leave is reflected in attendance, capacity planning, and payroll exports.

Question 9

Can attendance connect to timesheets?

Accepted Answer

Yes. Clock-in / clock-out, breaks, and overtime remain linked to the work items time was captured against.

Question 10

How is margin per client calculated?

Accepted Answer

Cost (time × rate + expenses) is subtracted from revenue on the same objects that produced the work. Margin updates as reality does.

Question 11

Can I issue and track invoices from Plynt?

Accepted Answer

Yes. Draft, send, mark paid, and record partial payments. Invoices reference the underlying deliverables so the audit trail stays clean.

Question 12

Where do dashboards read from?

Accepted Answer

Dashboards query the same live objects your team edits — never a separate warehouse. What you see is what shipped, right now.

Question 13

Can I build a custom view?

Accepted Answer

Yes. Views compose filters, groupings, and computed columns over any module. Save, share within the workspace, or export.

Question 14

How isolated are workspaces?

Accepted Answer

Each workspace is scope-enforced end-to-end. Queries, records, and audit logs never cross workspace boundaries.

Question 15

What is captured in the audit log?

Accepted Answer

Every state change — who, what, when — is written to an append-only log scoped to that workspace.

Question 16

Do I need to migrate off my current tools first?

Accepted Answer

No. Most teams import clients and open projects, keep sending from their current mail client, and switch over module by module.

Question 17

Can I try Plynt with real data?

Accepted Answer

Yes. Every paid tier includes a 7-day trial with full functionality on a real workspace.

Question 18

Does Plynt work for small teams?

Accepted Answer

It's designed to. A single-person business can run one workspace; larger organizations can operate many, cleanly separated.

Answers, grounded in how Plynt actually works.

Work OS

Client OS

People & Access

Requests & Attendance

Finance OS

Analytics OS

Workspace & Security

Common questions we hear during evaluation.

Didn't find your answer?

One truth for the whole service business.