Wrkbase Help Center: answers, not a support queue

Sign up on the Free plan. No credit card required. Your workspace is created immediately and you land straight in it, ready to invite people and add your first task. It starts in your own timezone, date format, and currency, and you can change any of them in Company Settings.

Up to 5 members, tasks, time tracking, attendance, team chat, calendar, leave, HR tools (onboarding, HR documents, org chart), custom roles, and reports. Payroll, performance, the AI agent, leads, finance, timesheets, shift scheduling, automations, and the API are on Team and Enterprise.

Yes. Free supports up to 5 members with everything except payroll, performance, the AI agent, leads, finance, timesheets, shift scheduling, automations, and the API. There is no trial clock. Free stays free.

Inside your workspace settings. Team and Enterprise are both self-serve checkouts, billed monthly or yearly, and moving between paid plans is prorated. Talk to sales only if you need 200+ seats or custom terms.

Add a card to any column on the board, set an assignee, priority, and optional due date. Tasks can carry labels, checklists, and file attachments.

Priority (Low/Medium/High) and labels are for filtering and sorting the board. They don't change permissions or automation on their own, they're organizational.

Yes. Save a task as a template from the create form or from an existing task, checklist included. Anyone can start a new task from it, and a template can be set to repeat daily, weekly, or monthly.

Yes, comments support @mentions, which notify the mentioned person, and file attachments.

Yes. It starts the time-tracking timer automatically for whoever is assigned. Move it to any other status and the timer stops. See the Time tracking section below.

There is no manual Start/Stop button. Moving a task card to "In Progress" starts the clock for that task; moving it to any other status stops it. This is deliberate, see the blog post on why.

Time entries are derived from status-change events, so correcting a mistake means correcting the task's history rather than editing a number directly. This keeps the log from silently drifting from what actually happened.

Your logged hours roll up per task and per day, visible on your own dashboard. Managers see it aggregated for their team; admins see it company-wide.

Attendance is a separate clock from task time tracking. You sign in for the day, optionally log breaks, and sign off, independent of which tasks you work on.

Your organization's configured office hours are the reference. Signing in after the configured start time or signing off before the configured end time is flagged automatically, computed server-side rather than self-reported.

Yes. Open Wrkbase in your phone browser and add it to the home screen. It then opens straight to a one-tap clock for sign in, breaks, and sign off. It needs a connection; there are no offline punches.

Yes. In Company settings, sign-in location can be Off, Record, or Require. Record saves where each sign-in and sign-off happened. Require (Team and Enterprise) refuses a sign-in outside your work locations and says how far away the person is. Sign-off is never blocked.

On Team and Enterprise, managers build a weekly rota and publish it, and each person is told their shifts. A published shift is what lateness is measured against that day. Each week also has a timesheet filled in from the attendance clock: correct a day with a reason, submit it, and your manager approves it or sends it back.

Start and end a break from the attendance screen; the break is excluded from your worked-hours total for the day.

You, your manager (for your team), and admins (company-wide): the same role-based scoping used everywhere else in Wrkbase.

Yes. Signing in, taking a break, and signing off each post an automatic status message to the Activity feed, so the team sees it live without anyone having to announce it manually, and without it crowding out real conversation in Team chat.

Four kinds of conversation: a company-wide Team room for real discussion, an auto-posted Activity feed for status updates, and on-demand direct/group threads you start with specific people. Not a maze of channels, but not one undifferentiated room either.

Yes, full-text search covers every conversation you have access to, plus an AI-grounded search that can answer natural-language questions about what was discussed.

Attendance sign-ins/sign-offs and task status changes post automatically to the Activity feed, a separate stream from Team chat. Those are system-generated, not typed by the person.

Task due dates, approved leave (yours, or your team's if you manage people), and personal events all merge into one calendar. There is no separate leave-tracking tool to keep in sync.

Submit a leave request with a date range from the calendar; it enters a pending state until a manager approves or rejects it.

Your manager, in one click from their dashboard. Admins can approve for anyone.

Yes, leave types are configurable per organization, and your remaining balance per type is visible wherever your leave requests are shown.

The 0-100 score is the completion rate of what was due in the period, computed automatically. A period with nothing due has no score at all and is left out of averages. The number is never typed in by a manager; written reviews, goals, and 1:1s sit beside it under Performance.

You can't edit it directly, because it isn't self-reported. If the underlying task data is wrong, correcting that data is what changes the score.

Managers and admins see both individual scores and company/team trend lines over time, feeding from the same task and time data as the individual score.

Payment status is computed server-side from what was actually recorded as paid, never trusted from the client, and never a status you can toggle by hand without a corresponding payment record.

Yes, multi-currency is supported for salary records.

Yes, full payment history is visible to the employee it belongs to, and to admins.

Partly. Generating a pay run for a period creates a line for everyone with a salary set, using that salary as the amount. Add bonuses, commission, or deductions per line while it's a Draft, then approve it as a batch and mark it paid. For anyone marked hourly, the amount is their rate times their hours in the period (an approved timesheet where there is one, the attendance clock otherwise), with overtime past your daily threshold paid at your multiplier, and you can correct it on the Draft. Wrkbase does not move money itself: actual payment happens through your existing payment method, and gets recorded in Wrkbase.

Create an onboarding template under HR, optionally for one department, with the checklist items you want. When an invited employee accepts their invite, a checklist starts from the newest template for their department, or the general one. Assign each task once it starts; assignees are notified. For accounts you create directly instead of inviting, start the checklist from their profile.

Under HR, create a document template: choose the letter type (offer, appointment, contract, welcome, experience certificate, relieving letter, NOC, full-and-final settlement, or other) and one of four letterhead styles, then write the body or have the AI draft it. From an employee's Documents page, pick the template to generate a PDF with their details filled in, then download it or email it to them.

Holidays are under HR > Holiday calendar; they appear on the shared calendar and are left out of working days in attendance. Compliance documents such as visas, work permits, certifications, and contracts are added on each employee's profile with an expiry date, and HR is reminded 30 days before each expires.

From Leads, choose Import CSV, upload the file (up to 5,000 rows), check the suggested column mapping and preview, and import. Duplicates by email, or by name and company, are skipped, and new leads are assigned to whoever has the fewest open leads. Leads are on Team and Enterprise.

A follow-up task is created for the lead’s owner, due in three days, with the usual reminders. If a lead goes seven days without activity, its owner is alerted.

Open the lead and choose Convert to customer. Its details are copied into Finance as a customer you can invoice, and the lead is marked Won.

Yes. Send emails the invoice PDF to the email address on the customer's record, marks it Sent, and starts overdue tracking. If the customer has no email address, add one first. When payment arrives, record it on the invoice and it's added to your income.

Submit a claim with a category, amount, date, and receipt. An approver approves it or rejects it with a reason, and you are notified. Once approved, it is marked paid from an account, which records the expense.

Yes. Import your bank's CSV from Finance; each amount's sign decides income or expense, rows already recorded are flagged as duplicates, and Wrkbase suggests which income pays which open invoice for you to confirm. Finance is on Team and Enterprise.

Time tracking, performance, per-employee and per-department summaries, weekly and monthly digests, lead pipeline and conversion, and nine finance reports (income, expenses, both breakdowns, profit and loss, cash flow, outstanding invoices, overdue invoices, and a monthly comparison), as PDF or Excel.

Kicking off a report never blocks the request that started it. The PDF or XLSX renders asynchronously and notifies you when it is ready, so you can keep working.

PDF and XLSX, from the same underlying renderer.

Announcements are a company-wide bulletin board. Posting is scoped by role like everything else in Wrkbase.

A pinned post always surfaces first, ahead of newer unpinned posts, so time-sensitive notices don't get buried.

It plans and executes real actions across tasks, salary, and employee records (creating tasks, adjusting records, notifying people) from a registered action library. It cannot invent capabilities or bypass permissions your role does not already have.

No. It always drafts an itemized plan first and waits for you to review and confirm before executing anything.

Steps run one at a time. A single failure never cascades into the rest of the plan, and the failure is recorded like any other outcome.

Yes. Every attempt, whether it succeeds or fails, is written to the same immutable audit log a human action would be, visible in real time on the audit log page.

Re-checked at execution, server-side, every time. The plan you approved is not treated as a standing authorization. Your actual role at the moment of execution is what is enforced.

Four: Boss (everything, including billing, roles, and the audit log), HR (people, leave, payroll, and HR tools company-wide), Manager (work, leave approvals, leads, and finance, without payroll), and Employee (their own work and pay, plus read access to company tasks).

Yes, on every plan. Create your own roles and choose their permissions, or adjust a default role and reset it later. Nobody can edit a role more senior than their own.

No. Every record-level "own vs. any" scope is enforced server-side. Hiding a button in the interface is not how access control works here.

In-app, email, and push, each configurable per person.

Yes, notification preferences are per-person and per-channel, not all-or-nothing.

No. Updates push live over a JWT-authenticated realtime connection.

Every action, human or AI agent, that mutates data: who or what did it, what it did, and when. Logins and sign-ins land in the same trail, not a separate security log.

No. Database-level triggers block edits and deletes on audit records, so it cannot be quietly cleaned up after the fact, including by an admin.

HTTPS end to end, with JWT-authenticated realtime connections and CSRF protection on every mutating request.

We're not going to claim one we don't hold. What's documented on the security page is the actual enforcement model. You can watch it happen in the live audit log rather than take a badge's word for it.

No. Free supports up to 5 members; Team is priced per member with no minimum seat count.

Your workspace and data stay accessible under the Free tier's limits. Nothing is deleted automatically. That stays your decision.

For a standard Enterprise plan you don't need to: it's a self-serve checkout in your workspace settings. Use the Contact page for 200+ seats, custom terms, or roadmap questions like SSO.

You do. It stays tied to your account and workspace, and you can export it at any time.

Yes, your workspace data can be exported on request.

Scope, sub-processors, security measures, and deletion terms. See the DPA page for the full document.