Tasko Handbook

Getting started

Tasko is your team's workspace for projects, documents, training, chat, and more — all in one place, reachable at tasko.linko.team.

Signing up

• Go to tasko.linko.team and choose Sign Up.
• Enter your email and choose a password (or, if your administrator has enabled it, you'll receive a one-time code by email instead of setting a password).
• Confirm your email using the link or code sent to you.
• If you were invited to an existing workspace, follow the invite link you received — it will drop you straight into your team's workspace after signup.

Logging in

• Return to tasko.linko.team and sign in with your email and password.
• If you belong to more than one workspace, you'll be asked which one to open.

Finding your way around

• Left sidebar — every app you have access to (Tracker, Chat, Documents, etc.) is listed here. Click an icon to open that app.
• Top bar — search, notifications (the bell), the Feedback button (a megaphone icon), and your account menu live here.
• Parpar — the butterfly icon opens the AI assistant panel, available from anywhere in the app.
• Widgets — some features (like an active video call) stay docked as a small floating panel while you keep working elsewhere.

Tracker

Tracker is where issues and projects live — the core of day-to-day work planning.

Projects and issues

• A Project is a container for issues, with its own members and set of statuses.
• An Issue has a title, description, status, priority, assignee, due date, and estimated time. Issues can have sub-issues (a parent/child breakdown of larger work).
• Issue templates let you pre-fill common issue types instead of starting from scratch each time.

Views

• Switch between a Kanban board (drag cards between status columns) and a list view.
• Group issues by status, assignee, priority, component, or milestone.
• Order manually (drag to reorder) or sort by status, priority, last updated, or due date.

Milestones and components

• Milestones represent larger goals or releases — group issues under a milestone to track progress toward it.
• Components tag issues by feature area, useful for filtering across a large project.

Chat

Chat covers channels, direct messages, and threaded conversations.

• Channels can be public (anyone can join) or private (invite-only), each with its own member list.
• Direct messages are one-on-one (or small group) conversations, separate from channels. A DM can later be converted into a private channel if the conversation grows.
• Threads — replying to a specific message opens a dedicated thread panel, keeping side conversations out of the main channel feed.
• Messages support reactions, editing, pinning, and @mentions.
• A floating chat widget keeps a conversation accessible while you work in another app.

Parpar AI Assistant

Parpar ("butterfly" in Azerbaijani) is your built-in AI assistant. It has live, real-time access to your workspace data — it doesn't just chat, it can actually look things up and take action for you.

What Parpar can do

Read-only, available to everyone including guests:

• Find issues, projects, statuses, and milestones
• List workspace members and chat channels
• Read recent messages in a channel
• List and mark your notifications as read
• Search documents and get full issue details (including comments)

Actions that change data (Member and Admin roles — each shows a confirmation dialog before it happens, unless you've turned on auto-approve):

• Create or update issues, including bulk updates across many issues at once
• Create projects, add comments, send channel messages
• Create documents and channels, update project details

Admin-only, with confirmation:

• Delete issues, documents, or channel messages

Roles and permissions

You can change this default in Parpar's settings (gear icon) — always ask, or always auto-approve, regardless of your role.

Chat history and usage

• Your last 50 conversations with Parpar are saved and switchable from the history icon (clock icon).
• Parpar replies in whichever language you write in — English or Azerbaijani.
• A usage badge near the top of the Parpar panel shows what percentage of your daily AI usage allowance you've used — click it to see the exact numbers. This limit resets daily and exists to keep the whole team's AI costs predictable.

Contacts

Contacts is the shared address book underlying the rest of the platform.

• A Person can optionally be marked as an Employee of your organization.
• Organizations represent companies — useful for grouping contacts by employer, especially in Recruit and CRM-style workflows.
• Each contact can have multiple communication channels attached (email, phone, social profiles).
• Avatars can be an uploaded image, a solid color, a Gravatar, or an external URL.

Calendar Beta

Schedule events, manage recurring meetings, and — if connected — keep everything in sync with Google Calendar.

• Create single or recurring events; edit or cancel one instance or the whole series.
• Set a visibility level per event (public, free/busy only, or private) and an access level per calendar.
• Choose a Primary Calendar — the one new events default to.

Google Calendar sync

Connect your Google account under Settings to enable real two-way sync: events created in Tasko appear in Google Calendar and vice versa, and edits/cancellations flow both directions. Invite emails for synced events are sent automatically.

Documents

A collaborative wiki for team knowledge, specs, and notes.

• Documents live inside a Teamspace — create or join one before adding documents.
• Documents can be nested arbitrarily deep (a document can contain sub-documents), and reordered by drag-and-drop in the navigator.
• Editing is real-time and collaborative — multiple people can edit the same document at once.
• Snapshots let you save a version and restore it later if needed.
• "My Documents" shows everything you've touched across every teamspace in one place.

Controlled Documents QMS

A formal, versioned document-control system for regulated or quality-managed content — policies, SOPs, and procedures that need review, approval, and audit history.

• Each document has a version number (major.minor), a unique code, and a lifecycle: draft → effective → archived/obsolete.
• A formal review and approval workflow routes documents through reviewers and approvers before they become effective — including optional external (outside-the-company) approvers.
• Document Templates let you start a new controlled document with the correct numbering and structure already applied.
• Every change requires a Change Control record explaining the reason and impact.
• Documents can require periodic re-review, and can be linked to Training so staff must read and acknowledge them.

Training

A built-in learning management system — courses, quizzes, and tracked completion. This is central to running staff certification and onboarding programs.

• A Training is a course with a title, description, and quiz questions, plus a required passing score. It moves through Draft → Released → Archived; once released, its content is locked so results stay comparable.
• Managers send Training Requests to specific people, optionally with a due date and a maximum number of attempts.
• Each attempt is scored automatically against the passing threshold.
• Key views: My Trainings and My Results (for trainees), Trainees' Results and All Trainings (for managers).

Test Management Beta

For QA teams tracking manual test cases and test runs.

• Structure: Test Project → Test Suites → Test Cases (each with a type, priority, and status).
• A Test Plan groups specific cases to be executed together.
• Running a plan creates a Test Run; a step-by-step "Test Runner" lets you record pass/fail per case.

Survey Beta

Simple polls and questionnaires.

• A Survey is a reusable question set (short text, single-choice, or multi-choice, with an optional "other" free-text option).
• A Poll is one person's submitted answers to a survey.
• Editing a survey template later does not change already-submitted responses — each poll is a snapshot at the time it was answered.

HR Beta

Org structure and time-off management.

• Departments form a tree (org chart) with a team lead, managers, and members. An employee becomes "Staff" once assigned to a department.
• Time-off requests use built-in types: Vacation, Sick, PTO, Remote, and Overtime.
• A schedule/structure view shows the org chart alongside a calendar of who's out and when; public holidays can be set per department.
• Submitting or approving a request automatically notifies the relevant manager.

Recruit

Applicant tracking for hiring.

• Candidates (shown as "Talent") are people with a resume, skills, and source noted.
• Vacancies are open positions, each with its own Kanban pipeline of interview stages.
• An Application links one candidate to one vacancy and moves through that pipeline.
• Interviewers leave Reviews (verdicts) tied to a candidate.

Inventory Beta

A product catalog — not a stock/warehouse system.

• Manages Products, nestable Categories, and Variants (SKU-level options of a product, e.g. size or color).
• There is no purchase-order, supplier, or stock-quantity tracking — this module is purely for describing what you sell, not managing how much of it you have.

Video Calls / Office

A virtual office for meetings and ambient team presence, built on real video infrastructure (LiveKit) — not a stub.

• Floors contain Rooms, each with an access mode: public (join freely), knock (request to join), or private.
• In a call: mute/unmute, camera on/off, screen share, reactions, and inviting others in.
• Per-room settings can enable live transcription and recording.
• Meeting Minutes documents can be created automatically or manually per call, and calls can be linked to Calendar events.
• A floating widget keeps you visibly "in the call" even while browsing other parts of the app.

Process (automation)

No-code workflow automation attached to custom object types (see Custom Object Types below).

• A Process defines a set of States, connected by Transitions that trigger when their criteria are met.
• Each transition runs an ordered list of Steps — create or update a record, add a tag, create a to-do, request approval, or even kick off a sub-process.
• Executions can be triggered automatically (on create/update) or on a schedule, and each run is tracked with its own progress and per-person to-dos.

Custom Object Types

Lets an administrator define entirely new record types without writing code — for example, "Equipment" or "Vendor."

• A Master Tag defines the schema (fields) for a new object type; a Card is one record of that type.
• Cards can be grouped into spaces and permission-scoped using Roles.
• This is the building block that both Process and the Inventory-adjacent Products feature are built on top of.

Gmail integration Beta

Connect your personal Gmail account to send and receive email tied to a specific Contact, without leaving Tasko.

• Connection uses Google's standard OAuth sign-in — no password sharing.
• Once connected, mail with a contact appears as a message timeline on that contact's record.
• A conversation can be explicitly shared so teammates without their own Gmail connection can still view it.

Telegram integration Beta

Similar to Gmail, but for Telegram conversations.

• Connect your personal Telegram account via phone number + PIN pairing with the Tasko bot.
• Messages sync per-contact, the same way Gmail messages do.
• You can choose to sync all chats or only starred ones.

GitHub integration

Two-way sync between Tracker issues/pull requests and a real GitHub repository.

• An admin authorizes the GitHub App once at the workspace level, then maps specific repositories to specific Tracker projects.
• Issue status, labels, and description sync in both directions.
• Pull requests show their real GitHub state (open/closed/merged, mergeable, review decision) directly inside Tasko, including inline code review comments.

Notifications

• You're notified of mentions, reactions, and activity on things you're following.
• Delivery channels: in-app inbox (always on), browser push, and sound alerts — each configurable per notification type in your settings.
• Notifications are in-app/push only today — individual events (like a new mention) do not currently trigger a separate email.

Feedback button

The megaphone icon in the top bar opens a short feedback form — anything you write goes directly to the platform's creator, with no ticketing or auto-reply. Use it for bugs, confusing screens, or feature requests.

Admin Dashboard

A separate, creator-only monitoring tool at tasko.linko.team/admin.html, gated by its own access token (not tied to regular platform accounts).

• Overview stats: total workspaces, total people, AI messages sent, OpenAI token usage and estimated cost (today and last 30 days), active video calls, and feedback received.
• Per-person breakdown of AI usage and cost.
• Live list of active video call rooms and participants.
• The last 500 feedback submissions.
• A broadcast tool to send a real email to every verified user in the workspace — used for announcements, updates, and news.

This dashboard does not manage billing, delete workspaces, or suspend users — it's for monitoring and communication, not administration of the platform itself.

Available but not enabled Not active

These modules exist in the platform and can be turned on for your workspace if you need them, but are not active today:

• Lead — a sales CRM pipeline (funnels and leads tied to a customer).
• Board — a generic Trello-style Kanban board, separate from Tracker.
• Bitrix — a sync connector for organizations migrating from or using Bitrix24 CRM.
• Products (PLM) — versioned product releases linked to Controlled Documents, for regulated manufacturing workflows.
• Rating — a document scoring/reaction system based on activity and reactions.

Getting help

• Ask Parpar directly — it can look up almost anything in your workspace for you.
• Use the Feedback button for bugs or suggestions.
• For account or access issues, contact your workspace administrator.