Your first session has one goal: create a project with a board that can hold real work. Do the steps below in order; each step unlocks the next part of the application.
1. Sign in and verify the account
Taskavel can use its passwordless sign-in flow as well as account security settings. Follow the sign-in link or normal authentication flow supplied by the application, then complete email verification when the application asks for it. Project pages, settings, and everyday work sit behind authenticated and verified access, so do not skip a verification message as “optional”.
If an invitation brought you here, open the signed invitation link while signed in to the account that should join the project. New people may be asked to finish account setup first. The invitation is then associated with that account and sends them into the project they were invited to.
2. Complete the onboarding wizard
The first-run wizard collects the profile information Taskavel needs before opening the full workspace. Add the name teammates should recognize and complete the required profile fields. The application uses that identity in assignments, task activity, comments, and standups.
Open Account Settings → General after onboarding and set your timezone. Due dates, task reminders, daily standups, and manual time entries are interpreted using the account timezone. Correcting it later does not make an unclear deadline retroactively clear to a team, so agree on the expected timezone before scheduling work.
3. Create the first required project
Use the projects area or project switcher and choose Create project. A project is not merely a label: it is the access boundary for boards, tasks, members, milestones, notes, activity, and project integrations. Start with one focused body of work, such as a client delivery, product release, or internal initiative.
Give the project a descriptive name and create it. The owner is the person who creates the project. Owners can later change project settings, delete the project, and control project-level AI access. You can create additional projects later when work needs different members or a different workflow.
4. Set up the first board and columns
Open the project’s board. A board presents the project’s tasks in Kanban and list views. The first board has columns; use them as the stages through which work moves. A simple starting workflow is To do, In progress, Review, and Done.
Owners and admins can add, rename, reorder, and remove columns. Columns can also be marked as planning, progressing, testing, or finish. Keep the first workflow small: a team gains more from consistently moving tasks through four clear stages than from creating a column for every exception. Add another board only when the project has a genuinely separate stream of work.
5. Create the first task
From the board, create a task in the first column. Write a name that describes a deliverable or decision, not a vague category. Add a description when the assignee needs context. Then add only the planning information that is known now:
- Assign one or more project members when ownership is clear.
- Set a due date only when the team has agreed what it means.
- Select a priority and tags if they help the team filter later.
- Attach the task to a milestone if it contributes to a defined deadline.
- Add a checklist for lightweight steps, or subtasks when a step needs its own task and date.
Move the task to the next column when its state changes. Completing it is stricter than moving it: incomplete subtasks, checklist items, and blocking dependencies must be resolved before Taskavel marks it complete.
6. Invite a collaborator when the project is ready
Open the project’s team or member settings. An owner or admin can invite an email address as an admin, member, or guest. Choose the lowest role that fits the work: members can create and update project work; guests can view project content but cannot change it. Owners and admins manage the project structure and members. The active-member allowance is enforced when inviting members, while guest invitations are handled separately.
The recipient receives a signed invitation link. The invitation list lets an owner or admin resend or cancel an unaccepted invitation. Do not share a generic project URL as a substitute for an invitation; membership is what grants access.
7. Pick the next workflow, not every feature
After the first task is moving, choose the guide that matches today’s need:
- Boards & columns for shaping the project workflow.
- Task details for dependencies, reminders, checklists, and attachments.
- Collaboration for roles, comments, and task watching.
- Time tracking or Daily standups for personal work routines.
- Integrations, AI & credits, and Taskavel MCP only after the core project workflow is established.
Avoid deleting or permanently destroying data during setup. Archiving a task keeps it recoverable; permanent destruction is a separate, irreversible action.