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

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.

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.

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).

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.

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.

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.

Write your first automation rule

Go to Operations → Automation. Click New Rule. The form is three blocks:

• Trigger: Priority equals Critical
• Condition (optional): leave empty
• Action: Notify Demo Admin (or any named user)

Save the rule. Click the Dry Run button (▶) next to it to preview which tasks it would affect — a tasks-affected count appears next to the rule. Click Apply (✓) to actually run it; the matching tasks are processed and the result is written to the rule's history tab.

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?"