Quickstart

From signup to a connected workflow in under 10 minutes.

Eight steps. By the end you'll have a project with tasks, a CAPA that traces back to a bug, an automation rule that watches your overdue work, and a sense of how the modules talk to each other. Every signup gets seed data so you don't have to set anything up before clicking around.

What you'll do

  1. Sign up and land in your tenant
  2. Find your way around the sidebar
  3. Open a task and edit it inline
  4. Move it through Kanban
  5. Add it to a sprint, watch the burndown update
  6. File a bug, link a ticket, open a CAPA
  7. Write your first automation rule
  8. Invite a teammate and check the audit log
1

Sign up and land in your tenant

Go to azorasolutions.com/login and sign up with email + password. No credit card. Your tenant is provisioned immediately — every record from this point forward carries your account_id and is invisible to other tenants.

You'll land on the dashboard with seed data: 25 sample tasks across 5 projects, a few vendors, a CAPA in progress, and an org chart. Don't delete it — it's how the rest of this guide works.

What just happened: A row was created in the accounts table. Every other piece of data you'll create this session inherits that account_id. More on isolation →
2

Find your way around the sidebar

The left sidebar has six groups: Work (News, Tasks, Kanban), Planning (Sprint, Roadmap, Calendar), Insights (Reports, Performance), Tools (Meetings, Units, Documents, Wiki, Hallway, Task Dump, Automation), Quality (CAPA, NCR, Risk Register, Audits, Traceability, Test Mgmt), and Admin (Settings, Users).

Hit Ctrl+K any time to open the command palette and jump to any panel by name. Hit ? for the full keyboard-shortcut overlay.

If a panel feels empty: It's because the seed data is project-shaped, not module-shaped. Tasks have CAPAs that have audit findings. Vendors have POs. Documents reference units. Click around — the cross-references appear naturally.
3

Open a task and edit it inline

Click Tasks in the sidebar. You'll see a table — title, project, assignee, status, priority, due date. Click any cell to edit in place. No modal, no submit button. The change saves on blur.

Use j/k to move between rows, Enter to open the task drawer for the full editor (story points, blocked-by, parent task, requires-QC checkbox).

Try this: Change a task's status to "Under Review" — if it has requires_qc=true, the system won't let you mark it Done until QC passes. Same gate is enforced by the API and the automation engine, not just the UI.
4

Move it through Kanban

Switch to Kanban. Same tasks, different view. Drag a card across columns: To Do → In Progress → Under Review → Done. The status updates everywhere — Tasks list, Sprint board, Roadmap, Calendar — because it's the same row.

Toggle swimlanes by assignee or project from the toolbar. Flip on WIP limits to see who's overloaded.

5

Add it to a sprint, watch the burndown update

Go to Sprint. Drag a few tasks from the Backlog onto the active sprint. The burndown chart on the right updates as you go. The velocity bar (last 4 sprints) shows the team's typical commit-vs-complete delta.

Story points come from the task's drawer (Step 3). If a task has no points, it shows up as — in the sprint summary; you can set them inline.

6

File a bug, link a ticket, open a CAPA

This is where Azora's integration story lands. From the seed data, find a bug (Tasks panel, filter by Type = Bug). Click into it.

  • Click Linked Tickets in the right rail. The seed has a customer support ticket that triggered this bug — click to jump to the ticket.
  • From the bug's drawer, click Open CAPA. A CAPA gets created with the bug pre-linked as the source nonconformance.
  • Fill in the CAPA's effectiveness check date. Save. Now jump to Quality → Traceability — the CAPA shows up in the matrix, linked to the requirement it descends from.
What just happened: Three modules (Project Management, Support, QMS) shared a record. No webhooks, no sync jobs — they're rows in the same Postgres database, joined by foreign keys.
7

Write your first automation rule

Go to Tools → Automation. Click New rule. The form is three blocks:

  • Trigger: "Task is overdue by more than 3 days"
  • Condition (optional): "Priority is Critical"
  • Action: "Notify the assignee's manager"

Save with Dry run on. The cron worker runs every 5 minutes — within the next 5 you'll see a "would-have-fired" entry in the rule's history tab. Flip dry-run off to actually send notifications.

Cap: Each rule is capped at 100 actions per tick. A misconfigured rule can't accidentally notify your whole company. More on the engine →
8

Invite a teammate and check the audit log

Go to Admin → Users. Add a teammate by email + role. They get an invite link valid for 24 hours.

While you're there, click Audit Log. Every CRUD operation you've made in this session is there — actor, action, before-state, after-state diff. This is what auditors want; it's there from day one, not a feature you turn on.

Done. You've now seen the loop: tasks → kanban → sprint → bug → CAPA → traceability → automation → audit log. Everything else (HR, ERP, Finance, Facilities, Wiki) follows the same pattern. Click around.

What's not in this guide

A real per-module documentation site is on the way. In the meantime, the deepest writeups already on the marketing site are these:

Stuck somewhere?

Email us. We answer.

support@azorasolutions.com — 24h response on Pro, 4h on Enterprise.