Your first connected workflow.

Open your workspace

Open the workspace your team has arranged with Azora. Before starting, confirm which sample records and permissions are available for this exercise.

Use your access instructions to sign in. Keep the sample records available while following the guide. The public demo is read-only; changes in this guide require an appropriately configured workspace.

Find your way around the sidebar

Navigation follows the solution you choose. In the updated shell, the left rail opens seven core solutions grouped by purpose, plus shared Collaboration. Open All Solutions for the directory; Clinical Research & Trials appears separately as a future portfolio, with existing authorized workspaces preserved. Your account determines which destinations are available.

• My Workspace — your cross-solution home.
• Pinned panels — your working set, in the order you choose.
• Recent records — return to recently visited work you may still access.
• Solution panels — workflow groups and hubs; tabs keep related registers together.
• Search — open the command palette with the sidebar search button or Ctrl+K.

Use the sidebar arrow or Ctrl+B to show panel labels. On a narrow screen, this opens a navigation menu; choose a panel to continue. Settings lives in the avatar menu in the top-right. If your account uses the earlier shell, choose solutions with the top-bar switcher. Hit ? for the keyboard-shortcut overlay.

Open a task and edit it inline

Open My Work and choose its List view. The task table shows title, project, assignee, status, priority, and due date. Editable cells save on blur; open a task for its full detail.

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.

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.

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) retain the audit evidence supported by the workflow. Designed for the auditor question "who did what, when?"