Quickstart

From a provisioned tenant to a connected workflow in about 15 minutes.

Eight steps. Open-beta tenants are sales-provisioned — email us and we'll seed your tenant with sample data and send you a login within 24 hours. Or explore the live demo right now (no signup). By the end of this guide you'll have moved a task through Kanban, planned a sprint, escalated a meeting action item to a CAPA, written your first automation rule, and seen the audit trail.

What you'll do

  1. Request a tenant and land in the dashboard
  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. Run a meeting, escalate an action item to a CAPA
  7. Write your first automation rule
  8. Invite a teammate and check the audit log
1

Request a tenant and land in the dashboard

During open beta, tenants are provisioned by us — email sales@azorasolutions.com with your team name and how many seats. We'll create the tenant record, add representative sample projects, tasks, quality records, vendors, people, and meetings, then send the access details within the stated beta provisioning window.

Sign in at azorasolutions.com/login with the credentials we send. You'll land on the dashboard with the seed data already loaded. Don't delete it — it's how the rest of this guide works.

What just happened: A row was created in the cp_accounts table. Every record you create this session inherits that account_id. More on isolation →
2

Find your way around the sidebar

The left sidebar has ten sections. The ones you'll use most:

  • Home — dashboards.
  • Work — News, Tasks, Kanban, Bug Reports.
  • Projects & Planning — Sprint, Roadmap, Calendar, Goals, Dependencies, Mgmt OS.
  • Quality — CAPA, NCR, Audits, Risk, FMEA, Traceability, MDSAP.
  • Engineering & Lab — Units, Equipment, Test Mgmt.
  • Operations — Vendors, POs, Automation.
  • Knowledge — Wiki, Documents, Meetings, Hallway, Templates.
  • HR — Employees, Leave, Onboarding.
  • Insights — Reports, Performance, Discovery.
  • Admin — Users, Audit Log, Modules.

Settings (Notion config, appearance, your account profile) lives in the avatar menu in the top-right, not in the sidebar. 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: The seed data is project-shaped, not module-shaped. Tasks link to CAPAs which link to audit findings. Vendors have POs. 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 ↑/↓ to move between rows. The peek drawer opens automatically as you navigate. Hit F2 to open the full task 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

Run a meeting, escalate an action item to a CAPA

This is where Azora's integration story lands. From Knowledge → Meetings, open the seeded "Sprint planning" meeting (or create a new one). Add an action item in the notes — for example, "Investigate intermittent assembly tolerance failure on Optic-12."

  • Click Create task from action item. A task is created with the meeting linked as its source — the link shows on both records.
  • From the new task, jump to Quality → CAPA. Click New CAPA and paste the task ID into the Source nonconformance field. Save.
  • Fill in the CAPA's effectiveness verification date. Save. Now open Quality → Traceability — the CAPA shows up in the matrix, linked to the requirement it descends from.
What just happened: Meetings, Project Management, and QMS shared a record. No webhooks, no sync jobs — they're rows in the same Postgres database, joined by foreign keys. Direct bug → CAPA creation is not yet part of this workflow.
7

Preview and apply a task automation rule

Go to Operations → Automation. Use a disposable task, then click New Rule. The browser rule builder has two blocks:

  • When: Status equals To Do
  • Then: Add label needs-review

Save the rule. Click Dry Run to preview the matching tasks without changing them. Review the count, then click Apply to run this supported task mutation manually. The matching task notes receive [auto: needs-review], and the committed result is recorded in Automation history.

Current execution boundary: browser-authored task mutations—status, priority, assignee, and label changes—can be previewed and applied manually. Notification and webhook rules are server-preview-only, and the scheduled worker is default-off and code-forced to dry-run, so it does not perform scheduled writes or deliveries today. Time-based and aggregate triggers are not part of the rule builder. More on the engine →
8

Invite a teammate and check the audit log

Go to Admin, then the Users tab. Click Add User. Enter the teammate's name, email, role, department, and manager. The recommended path sends a one-time set-password link; if email delivery is unavailable, an admin can use a temporary password as a fallback and share it out of band.

While you're there, open the Audit Log tab. Most write paths in this session are there — actor, account, action, entity. QMS-specific routes (CAPA, NCR, change control) capture full before/after diffs. Designed for the auditor question "who did what, when?"

Done. You've now seen the loop: tasks → kanban → sprint → meeting → CAPA → traceability → automation → audit log. Everything else (HR, ERP, Finance, Facilities, Wiki) follows the same pattern. Click around. Admins can resend a user's one-time setup link from the user row.

What's not in this guide

This guide covers the first connected workflow. For deeper technical and product references, continue with these pages:

Stuck somewhere?

Email us. We answer.

support@azorasolutions.com — best-effort email support during open beta. At GA, response-time commitments follow the applicable plan or enterprise services agreement.