SaaS Product Support

Legal & security: read the Rule Vault Data Processing Agreement & Written Security Policy.

What Rule Vault Does

Jira keeps no history of automation rule changes — an edited or deleted rule is gone for good. Rule Vault takes a daily snapshot of every automation rule on your site, keeps a version history for each one, shows you exactly what changed, and lets you restore any rule to any previous version in one click.

You'll find Rule Vault in Jira under Settings (gear icon) → Apps → Rule Vault, in the left sidebar. The app has three tabs: Rules, Activity, and Setup.

1. First-Time Setup (Connect a Token)

Rule Vault reads your automation rules through Atlassian's Automation API, which requires an API token from a Jira admin account. A dedicated service account is recommended so the connection survives staff changes.

1. Sign in to Atlassian as the account you want Rule Vault to use, and go to id.atlassian.com → Security → API tokens.
2. Click the plain "Create API token" button — not "Create API token with scopes." Scoped tokens are rejected by the Automation API. Copy the token (it's shown only once) and note its expiry date.
3. In Rule Vault, open the Setup tab. Enter the account's email and paste the token, then click Update credentials.
4. Rule Vault tests the connection immediately. Success shows a green banner: "Connected as [email protected]. Daily snapshots are active." An error here means the token is wrong, scoped, or the account isn't a Jira admin.

2. Snapshotting Your Rules

A snapshot is a point-in-time capture of every automation rule on the site. Rules that haven't changed since the last snapshot are skipped, so snapshots are cheap and versions only accumulate when something actually changed.

• Automatic: Rule Vault snapshots your whole site once a day, on its own. No action needed.
• Manual: open the Rules tab and click Snapshot now — do this right after you make a batch of rule changes you want captured immediately.

After clicking, a status message shows how many rules were queued (e.g. "Snapshot started: 245 rules queued, 0 deletion(s) detected"). Large sites are processed in paced batches, so give a big snapshot a few minutes, then click Refresh.

The first snapshot captures every rule as version v1 — that's your baseline. From then on, each detected change adds a new version.

3. Viewing Rules and Their History

The Rules tab lists every captured rule with its current state (ENABLED / DISABLED / DELETED), how many versions Rule Vault holds, and when it last changed. The most recently changed rules sort to the top.

1. Find the rule you're interested in and click History.
2. The history panel lists every stored version (v1, v2, …) with its capture timestamp.
3. Click Diff on any version to see what changed from the previous version, in plain language — for example: "Rule renamed", "Trigger changed", "Changed action 'clone' (value.operations[3])", "Rule disabled".

Diffs ignore cosmetic noise (timestamps, metadata) — if a diff is empty, the rule was re-saved without a real change.

4. Restoring a Rule

Restore rolls a rule back to any stored version. There are two cases:

• The rule still exists: open its History, pick the version you want, click Restore. The live rule is updated in place to that version's configuration.
• The rule was deleted: it shows a DELETED badge in the Rules tab. Restore recreates it from the stored version — in a disabled state, so you can review it in Jira's automation settings and enable it deliberately. It will never start firing behind your back.

Every restore is recorded in the Activity log with who-, what-, and when-level detail, so your audit trail covers recoveries too.

5. Change Alerts (Optional)

If you want to be notified when rules change or disappear, set an alert project:

1. On the Setup tab, enter a project key (e.g. OPS) under Alert project key and save.
2. Whenever a snapshot detects modified or deleted rules, Rule Vault creates an issue in that project, labelled rule-vault-alert, listing what changed.
3. Use your existing notification scheme, watchers, or an automation on that label to route the alert to email or chat.

First-time captures don't alert — only genuine changes and deletions do.

6. The Activity Tab

The Activity tab is a running log of everything Rule Vault has observed and done: CAPTURED (new version stored), MODIFIED, DELETED, and RESTORE events, with rule names, versions, and timestamps. It's the quickest answer to "what changed on this site recently?" and doubles as evidence for audits.

7. If Something Looks Wrong

Legal & security: read the Release Sync & Notes Data Processing Agreement & Written Security Policy.

What Release Sync & Notes Does

Teams that ship one product from several Jira projects have to mirror every version by hand: create it in each project, keep names and dates identical, release it everywhere at once, and then assemble release notes project by project. Release Sync & Notes removes that toil. You pick one lead project as the source of truth and any number of follower projects; versions created, renamed, re-dated, released, archived, or deleted in the lead are mirrored automatically in every follower. When it's time to ship, one click gathers the issues from every project in the group into a single combined release-notes document, publishable straight to a Confluence page.

You'll find the app in Jira under Settings (gear icon) → Apps → Release Sync & Notes. It has four tabs: Sync Groups, Dashboard, Release Notes, and Audit Log.

How to Get the Most Out of It

• Treat the lead project as the source of truth. All version changes flow lead → followers, never backwards. Make version edits in the lead only; edits made directly in a follower don't propagate and will be overwritten the next time the lead changes or a reconcile runs.
• Leave deletion sync off unless you need it. It's off by default: deleting a version in the lead then leaves follower versions in place. Turn it on only for groups where followers should mirror deletions too.
• Use a name filter to scope what syncs. If the lead project also has internal versions (hotfixes, experiments), set the group's filter — e.g. names starting with "2." — and everything else is ignored.
• Adopt, don't duplicate. If a follower already contains a version with the same name as a lead version, the app adopts it rather than creating a duplicate — and aligns it to the lead. The follower's previous description and dates are recorded in the Audit Log before being overwritten, so nothing is silently lost.
• Trust the nightly sweep. Once a day the app reconciles every group, healing anything a missed event left behind. "Reconcile now" runs the same repair on demand.

1. Create a Sync Group

1. Open Settings → Apps → Release Sync & Notes → Sync Groups.
2. Under "New sync group," give the group a name (e.g. Product releases).
3. Pick the lead project — the one whose versions define the release train.
4. Pick one or more follower projects. (The lead can't also be a follower.)
5. Optionally set "Only sync versions whose name starts with" to scope the group.
6. Review the five toggles: create, update (name/description/dates), release, and archive sync are on by default; deletion sync is off by default.
7. Click Save group.

2. Align Existing Versions (Reconcile)

Right after saving a group, press Reconcile now in the group's row. The app compares the lead's versions against every follower and brings them in line: missing versions are created, same-name versions are adopted, and differing fields are aligned to the lead. The result message tells you how many operations ran and how many versions were adopted. Running it a second time should report zero operations — that's how you know everything is in sync.

3. Day-to-Day Syncing

From here on, the app works on its own. Change a version in the lead project — create, rename, edit its description or dates, release, unrelease, archive — and the change lands in every follower, normally within seconds. Nothing to click.

The Dashboard tab shows every lead version with its state (unreleased / released / archived), release date, follower count, and a live in sync / pending indicator. If something shows pending for more than a minute, press Reconcile now on the group — the sweep repairs any missed change.

4. Generate Combined Release Notes

Prerequisite: issues appear in release notes when their Fix versions field is set to the version in question — in each project, on the issues themselves.

1. Open the Release Notes tab.
2. Select the sync group. The Version dropdown fills with the lead project's versions (released and archived ones are labeled).
3. Pick the version and choose how to group the notes: by Project (a section per project) or by Issue type (Story / Bug / Task sections).
4. Click Generate combined notes. The document renders as Markdown with clickable issue links and a count of included issues — copy it anywhere, or continue to publishing below.

5. Publish to Confluence

1. With notes generated, click Publish to Confluence… and pick the destination space.
2. The Confluence page title field defaults to "Release notes — version" — edit it to whatever you like before publishing.
3. Click Publish page. A success message links the new page id; the page appears in the chosen space with the same grouped content and working issue links.

6. The Audit Log

The Audit Log tab records every action the app takes — creates, updates, adoptions, deletions, reconcile sweeps, and Confluence publishes — newest first, with the space name, version, and details. Update entries include the prior values of any field that was overwritten (e.g. Updated description (prior: description='…')), so an overwritten description can always be recovered by copying it back from the log.

7. If Something Looks Wrong

Legal & privacy: read the Checklist All HQ Privacy Policy.

What Checklist All HQ Does

Trello's Advanced Checklists let you give checklist items due dates and assignees — but Trello has no view that shows those items across boards. A manager can't see everything assigned to the team, and deadlines buried inside cards get missed. Checklist All HQ is a Trello Power-Up that puts every checklist item from every board you choose into one filterable table: item, assignee, due date, card, list, and board. Filter by person or due date, check items off right from the table, jump to any card, and export the view to CSV for client reporting.

1. Install the Power-Up

1. Open the Trello board you want to start with.
2. Open the board menu → Power-Ups → search for "Checklist All HQ" (or find it in the Power-Up directory) → click Add.
3. A Checklist All HQ button appears at the top of your board.

2. First Run — Authorize

Click the Checklist All HQ board button. The first time, Trello asks you to authorize the Power-Up — this grants it a token to read and update checklists as you, limited to boards you can already access. Each member of your team authorizes individually. Your card data goes directly between your browser and Trello — it is never stored on our servers (see the privacy policy above).

3. The Console

The console is one table of checklist items. Out of the box it shows the current board; pick more boards in Settings (next section) to see your whole workspace.

• Filter by board, by member (including Unassigned), or by due window — Overdue, Due today, Due this week, or No due date. "Open items only" is on by default; untick it to include completed items.
• Sort by clicking any column header; click again to reverse. Overdue items are highlighted red.
• Check items off with the checkbox in the first column — the change is saved to Trello instantly.
• Open the card by clicking its name.
• Export CSV downloads exactly what the current filters show — handy for status reports and client updates.
• Card badges: on the board itself, cards show an orange "N items due" badge counting their open, due-dated checklist items.

4. Choose Which Boards Feed the Console

1. On the board's Power-Ups screen, open Checklist All HQ → ⚙ Settings (the gear icon).
2. Tick the boards you want included — any open board you're a member of is listed.
3. Click Save, then reopen the console. Items from all selected boards appear together, each labeled with its board and list.

5. Free Plan, Pro Plan & Billing

The free plan tracks the current board only. The Pro plan unlocks workspace-wide tracking (unlimited boards) and is priced flat per workspace — not per user: $12/month, or $99/year with a 7-day free trial. Every member of the workspace benefits from one subscription.

• Upgrade: open the console on any board — the upgrade banner shows both options. Checkout is handled securely by Stripe; the app never sees your card details.
• Manage or cancel: open ⚙ Settings → Manage subscription (or go directly to the billing portal), sign in with your billing email, and update your card or cancel anytime. Cancellations take effect at the end of the paid period.

6. If Something Looks Wrong

Legal & privacy: read the ConfigMonitor Privacy Policy.

What ConfigMonitor Does

Jira's built-in audit log tells you that a workflow, field, or scheme changed — it never tells you what changed. When a workflow breaks or a field disappears from a screen, admins are left guessing. ConfigMonitor answers the whole question: it automatically snapshots your site's configuration every hour — workflows, custom fields, field configurations, screens, screen schemes, permission schemes, notification schemes, and issue type schemes — computes before/after diffs, names the admin who made each change, and keeps a filterable timeline you can export to CSV for compliance evidence.

You'll find ConfigMonitor in Jira under Settings (gear icon) → Apps → ConfigMonitor — Configuration Audit.

1. Install and Capture Your Baseline

1. Install ConfigMonitor from the Atlassian Marketplace (a Jira site admin approves the read scopes at install).
2. Open Settings → Apps → ConfigMonitor and click Snapshot now.
3. You'll see "Baseline captured: N configuration objects." That baseline is the starting point — history begins at install, so changes made before ConfigMonitor was installed aren't visible.

From then on, ConfigMonitor snapshots automatically every hour. Use Snapshot now whenever you want a change you just made captured immediately.

2. Reading the Timeline

The timeline lists one row per configuration change, newest first: when it happened, the object type and name, the kind of change (created, modified, or deleted), who made it, and a plain-language summary — for example, "Transition 'Escalate' added to workflow 'Bug workflow'." Use the object-type dropdown to focus on just workflows, just custom fields, and so on.

3. Who Made the Change

ConfigMonitor correlates every detected change with Jira's native audit log and shows the matching admin in the Actor column. For a handful of object types, Jira's own log records nothing — in those cases ConfigMonitor says "not captured by Jira" rather than guessing. That's deliberate: it tells you the change is real but Jira didn't log an author for it, which is information you can't get anywhere else.

4. Compliance CSV Export

Click Export CSV to download the timeline exactly as filtered — timestamp, object type, object name, change type, actor, and summary per row. It's the change-management evidence a SOC 2 or ISO 27001 auditor asks for, ready to attach.

5. If Something Looks Wrong

Legal & privacy: read the Audit Log & Board History Privacy Policy.

What Audit Log & Board History Does

Trello's activity menu stops at the last 1,000 actions, whole classes of changes never appear in it, and when a card is deleted its history vanishes with it. Audit Log & Board History gives a board a permanent memory: every action, in one searchable timeline — who did what, when — including who deleted which card, with filters by person, action type, and date, and CSV export for reviews and compliance. History is recorded by a server that keeps listening even when nobody has the board open.

1. Install and Start Recording (Admin Required)

1. Open the Trello board → board menu → Power-Ups → search for "Audit Log & Board History" → click Add.
2. Click Connect in the popup that appears (or later via the board's Power-Up settings). Trello asks you to authorize — the token is read-only, expires after 30 days, and is used only to set up recording; it is never stored on our servers.
3. Recording begins immediately, and the settings panel shows every board member who switched it on and when.

2. The Timeline

• Whole board: click the Audit Log button at the top of the board. Filter by person, action type, or date range; page through as far back as your plan keeps.
• One card: open any card and click the Card history badge to see just that card's timeline.
• Deletions: deleted cards are highlighted — the row shows who deleted the card, when, and the card's title, even though the card no longer exists in Trello.
• CSV export (Pro): downloads exactly what the current filters show — ready to attach to a review, dispute, or compliance request.

Every member of the board can read the board's timeline — the same visibility Trello's own activity feed has. An audit log only one person can read is a log the team cannot trust.

3. Free Plan, Pro Plan & Billing

The free plan records one board per workspace with a rolling 7-day history window. Pro removes both limits — unlimited boards, history kept for as long as you're subscribed — and adds CSV export. Pricing is a 7-day free trial, then $5 per month, or $50 per year (two months free) — one flat price for the whole workspace, with no per-seat counting and no limit on members.

• Upgrade: open the Power-Up's settings on any board and click Upgrade. Checkout is handled securely by Stripe; we never see your card details. The plan activates within a minute of payment.
• Manage or cancel: settings → Manage billing opens the Stripe billing portal for invoices, payment method, switching between monthly and annual, and cancellation. Only a workspace admin can open it.
• If a payment fails, your history is safe: paid history is protected for 30 days past any billing hiccup — far longer than Stripe's retry cycle — so a card problem never destroys your record.

4. Stopping Recording & Deleting History

Because this is an audit product, stopping and deleting are deliberate, admin-only, visible acts:

• Stop recording (settings, admin only): recording halts immediately, every board member can see who stopped it and when, and the history is kept for 30 more days — export it, delete it deliberately, or re-connect within that window to keep it.
• Delete this board's history (settings, admin only): offers a CSV export first, requires typing the board id to confirm, and leaves a permanent deletion record — who, when, how many events, covering which dates — visible to every board member. Every deletion in this product leaves that mark, including automatic free-plan pruning.
• Disabling the Power-Up does not stop recording — it clears only your own settings. If any single member could switch off the board's audit log, it would not be an audit log. Ask an admin to stop recording from settings.

5. What Gets Stored (the Short Version)

The server stores action metadata: the action type, the actor's Trello member id (never their name), card and list ids and titles, timestamps, and which fields changed. It never stores card descriptions, comment text, attachments or their filenames, or anyone's name, username, email, or avatar — names you see in the timeline are resolved in your own browser from the board itself. The full detail is in the privacy policy.

6. If Something Looks Wrong

Legal & security: read the Find and Replace Privacy Policy.

What Find and Replace Does

Trello has no find and replace. When a client gets renamed, a product gets rebranded, or a term is retired, the old wording sits on dozens or hundreds of cards. This Power-Up searches card titles, descriptions and checklist items for any text — across the current board, or every board in the workspace on Pro — shows a before/after preview, rewrites every match in one job with a per-card change log, and can undo the entire job for 7 days. It can also watch boards for banned or outdated terms and alert you the day one reappears.

1. Install and Authorize

1. On your board, open Power-Ups, find Find and Replace + Banned Term Watch, and add it.
2. Click the new Find & Replace board button.
3. The panel asks you to authorize (read and write). This is your own Trello authorization — every search and every edit the Power-Up makes runs under your own permissions. It can never change anything you couldn't change by hand.

2. Search

Type the text to find. Matching is plain text (no regular expressions), case-insensitive by default with a case-sensitive option. Results list every matching field — which card, which field, how many hits — with the surrounding text for context. On the free plan you search the current board; Pro adds the whole workspace (workspace admin required for workspace-wide).

3. Preview and Rewrite (Pro)

1. Enter the replacement text and open the preview: every field shows its exact before and after. Untick any row you want left alone.
2. Run the rewrite. The job applies to the card's live text at that moment — anything edited between preview and execution is skipped and reported, never overwritten.
3. The change log lists every field: changed, skipped, or refused (a card you can't edit fails that item only; the rest of the job lands). Export it as CSV for your change-management records.

One approved rewrite runs exactly once — double-clicking the button or retrying a request cannot apply it twice.

4. Undo

Every rewrite job can be undone for 7 days, once per job. Undo is conflict-safe: a field is restored only if it still holds exactly what the rewrite wrote. If a colleague edited the field afterwards, their edit wins and the change log reports a conflict instead of clobbering their work.

5. The Banned-Term Watch (Pro)

Save a term and watch a board, and the Power-Up raises an alert the day the term reappears in a title, description or checklist item — with a link to the exact card and field. The watch alerts only; it never edits a card on its own. Any subscribed member can add terms and see alerts; removing a term or dismissing its alerts requires the member who added it or a workspace admin, so the watch can't be quietly switched off.

6. Free Plan, Pro Plan & Billing

• Free: search the current board with context, before/after preview, and per-card links to fix things by hand.
• Pro: execute rewrites, whole-workspace search and rewrite, a change log with CSV export, 7-day undo, saved patterns and the banned-term watch.
• Pricing: $10/month or $100/year — one flat price for the whole workspace, with no per-seat counting and no limit on members. The annual plan starts with a 7-day free trial.
• Billing is handled by Stripe Checkout and the Stripe customer portal (invoices, payment method, cancellation). Upgrading and billing actions require workspace admin.

7. If Something Looks Wrong

Legal & privacy: read the Board Merge & Split Privacy Policy.

What Board Merge & Split Does

Trello has no merge operation at any plan tier — consolidating two boards means moving lists one at a time, watching label sets duplicate, and keeping no record of what went where. Board Merge & Split turns that into one previewed job: merge an entire board into another (same-named lists drain their cards into their namesake; unique lists move wholesale with comments and activity intact), or split chosen lists out to an existing board or a brand-new one. Every job gets a dry-run preview first, a per-operation audit receipt afterwards, and can be undone.

1. Install and Authorize

1. On your board, open Power-Ups, find Board Merge & Split, and add it.
2. Click the new Merge & Split board button.
3. The panel asks you to authorize. This is your own Trello authorization — every read and every move runs under your own permissions. It can never change anything you couldn't change by hand.
4. Admin required: merging, splitting and undoing require you to be an admin of both boards involved (board admin, or admin of the workspace that owns them) — verified against Trello, not assumed.

2. Preview a Merge

Pick the other board and the direction, then run the preview. It shows the exact plan before anything is written: which lists will drain into a same-named list on the target, which will move wholesale, card counts, which labels already match, which will be created, and which have a color conflict — plus warnings, including anything an undo would not be able to restore. Previews are free and unlimited. You can override any colliding list to move-and-rename with a suffix instead of draining.

3. Execute

1. Click execute. The confirmation step spells out the counted consequences — lists moved, cards moved, labels created, whether the source board closes — and asks you to type the source board's name. The server enforces the same check.
2. The job runs server-side in small batches with automatic rate-limit backoff. A closed tab never corrupts a merge — reopen from History and it resumes where it stopped.
3. Labels missing on the target are pre-created (same name and color) ahead of the move, so Trello's native matching doesn't mint duplicates. Color conflicts are flagged, never silently "fixed".
4. The finished job's receipt lists every operation and its outcome, and is exportable as CSV. Receipts are kept 365 days.

4. Split

Tick lists on the current board and send them to an existing board (collisions follow the same merge semantics) or to a brand-new board, created empty in the same workspace. A split never closes the source board.

5. Undo

Merges and splits can be reversed: lists go back to their original boards and positions, drained cards return to the list they came from, archived shells reopen, a closed source board reopens, and labels the merge created are removed. Undo is conflict-safe — anything a teammate changed after the merge is reported as a conflict and left exactly where they put it. Where an undo has limits (a drained list bigger than one recording, or an undo of more than 500 operations), the preview names it and asks you to acknowledge it before the merge runs — never afterwards. Undo is never paywalled: a lapsed subscription can always put a board back.

6. Free Plan, Pro Plan & Billing

• Free: unlimited dry-run previews, single-list moves (parity with Trello's own Move menu), and undo.
• Pro: full multi-list merges and splits, split to a brand-new board, label pre-creation, and job history with CSV receipts.
• Pricing: $9/month or $90/year (two months free) — one flat price per workspace, with no per-seat counting and no limit on members. The annual plan starts with a 7-day free trial.
• Billing is handled by Stripe Checkout and the Stripe customer portal — Manage billing in the panel opens it for invoices, payment method, plan changes and cancellation. Upgrading and billing actions require workspace admin.
• Subscribed to our other apps too? Enter the same billing email at checkout as your other Macon Apps subscriptions and they share one billing record — the portal then shows them together. Subscriptions bought before this (each on its own record) are managed from their own app's Manage billing button.

7. If Something Looks Wrong

A product of J.P. Johnson Law LLC

Legal & privacy: read the Shift Handover Log Privacy Policy and Terms of Use.

What Shift Handover Log Does

Teams that run around the clock — operations centers, plants, labs, help desks, security posts — pass the baton at every shift change, and anything passed verbally or in a chat thread gets lost. Shift Handover Log is a Microsoft Teams app that gives a channel a structured handover log built on your actual shift schedule: the outgoing shift files a written handover, raises Info / Watch / Urgent items that carry forward until they're resolved, and the incoming shift acknowledges that they've read it — so there is always a record of what was handed over, to whom, and whether it was received. Missed handovers show up as visible gaps instead of silence.

The app lives as a tab in a Teams channel. Everyone signs in automatically with their Microsoft 365 account — there are no separate passwords or API tokens, and all times are shown in your own local time zone.

1. Add the Tab and Set the Shift Schedule

1. In the Teams channel where your shift team works, click + at the top of the channel, search for "Shift Handover Log", and add it.
2. The configuration screen asks for three things: your shift labels (comma-separated, e.g. Day, Swing, Night), the hour the first shift starts, and the time zone the schedule runs in (it defaults to yours).
3. The number of shifts must divide 24 evenly — 2, 3, 4, 6, 8, 12, or 24 shifts per day — so every hour of every day belongs to exactly one shift. The screen shows the derived schedule (e.g. "3 shifts of 8 hours, starting at 06:00") as you type.
4. Name the tab and click Save. The log is ready immediately.

2. Filing a Handover

1. Near the end of your shift, open the tab and click Start handover. The app knows from the schedule which shift you're on and which shift comes next.
2. Write the summary: what happened, what's running, what the next shift needs to know.
3. Click Raise an item for anything that needs tracking beyond your shift, and give each item a severity:
   • Info — for awareness.
   • Watch — keep an eye on it.
   • Urgent — act this shift.
4. Click Submit handover. The handover is stamped with your name, your shift, and the time, and appears instantly for the incoming shift.

3. Reading and Acknowledging

When you come on shift, the tab shows "Handover waiting for you" with the outgoing shift's summary and items. Read it and click "I have read this" — that acknowledgment is recorded with your name and time, so the outgoing shift (and any supervisor) can see the handover actually landed. Acknowledgment is per handover: the record shows exactly who confirmed receipt of what.

4. Open Items Carried Forward

Items raised in a handover don't vanish when the next handover is filed — they appear under "Open items carried forward" on every subsequent shift until somebody resolves them. An Urgent item raised on Tuesday's night shift is still staring at Friday's day shift if nobody has dealt with it. On the paid plan, aging analysis shows how long each item has been open across shifts.

5. People and Roles

• Everyone in the channel can read the log — a handover the incoming shift can't see is no handover at all.
• Writing needs a seat: use Add people (with the built-in people picker) to add the colleagues who file handovers. On the free plan, five people can hold write seats; the paid plan removes the limit.
• Roles: a Member writes handovers; an Admin also manages people and the shift schedule. The person who creates the log is its first admin.
• Anyone who no longer needs to write can release their seat for somebody else.

6. Free Plan, Paid Plan & Billing

The free plan covers one log, five writers, and the last five handovers of history — enough to run a single crew and see whether the app fits. The paid plan removes all three limits and adds continuity reporting, aging analysis, and CSV export. Pricing is $5 per user per month, or $50 per user per year (two months free).

• Upgrade: the subscription is purchased through the Microsoft commercial marketplace — from the app's page in the Teams app store or Microsoft AppSource. Checkout is handled entirely by Microsoft; we never see your payment details.
• Assign licenses: after purchase, assign licenses to the people who need the paid features in the Microsoft 365 admin center (Billing → Licenses), just like any other Microsoft 365 license.
• Manage or cancel: the subscription is managed in the Microsoft 365 admin center under Billing → Your products — seat count changes, switching between monthly and annual, and cancellation all happen there.

7. If Something Looks Wrong

A product of J.P. Johnson Law LLC

Legal & privacy: read the Assurance Map Privacy Policy and Terms of Use.

What Assurance Map Does

An assurance map is a matrix: your principal risks down one side, every internal and external assurance activity across the other, organised by line of defence. Almost every organisation that has one keeps it in a spreadsheet — and the spreadsheet is wrong within a quarter, because assurance work goes out of date and a spreadsheet doesn't notice. Assurance Map is a Microsoft Teams app that holds the same matrix and computes, as at any date you choose: which risks have no current assurance, which are covered only by work that has gone out of date, which rest on nothing but the risk owner's own self-assessment, where the same risk is reviewed twice on the same line of defence, and which activities carry a documented basis for reliance under the IIA's coordination and reliance standard (Standard 9.5).

The app lives as a tab in a Teams channel (or as a personal tab). Everyone signs in automatically with their Microsoft 365 account — no separate passwords or API tokens. It reads nothing from your chats, files, mail, meetings or calendar, and evidence is stored as a reference or a link, never as a copy of a report.

1. Add the Tab

1. In the Teams channel your audit, risk or governance team uses, click + at the top of the channel, search for "Assurance Map", and add it.
2. The configuration screen asks for a tab name and, optionally, the legal entity the map covers. Everything else — risks, sources, activities — is added from the tab itself.
3. Click Save. The map is ready immediately.

2. Build the Map

1. Add your principal risks — the register-level risks your audit committee sees, each with a reference (e.g. PR-01), a title, and an optional category.
2. Add assurance sources — the functions that provide assurance: information security, health and safety, data protection, quality, finance control, internal audit, external audit, regulators — each with its line of defence (Line 1 management, Line 2 risk and compliance, Line 3 internal audit, or External).
3. Record activities — what each source actually does: the piece of work, its type (self-assessment, management review, second line review, internal audit, external audit, regulatory inspection, certification), how often it happens, when it last happened, and its outcome if rated.
4. Link coverage — connect each activity to the risks it assures, at Full, Partial, or Indirect strength. The coverage tiles at the top compute themselves from that point on.

3. Reading the Analysis

On the paid plan, the reliance panel additionally shows how many activities have a documented basis for reliance — competence, objectivity and adequacy of evidence each recorded, and the work neither unperformed nor out of date — and what is blocking the rest.

4. Committee Snapshots and Export (Paid)

• Analyse as at a date: recompute the whole map as at any past date — or a future one, to see what will have decayed by the next committee.
• Snapshot for the committee: freeze the computed position before each audit committee. The position you reported stays answerable a year later, after every underlying row has moved on.
• CSV export: download the coverage analysis, one row per risk-coverage pair, ready for the committee pack.

5. Free Plan, Paid Plan & Billing

The included plan covers one map for a single team, up to five people and up to ten risks, with live coverage and currency analysis — genuinely useful on its own. The paid plan adds unlimited risks and maps, assurance sources maintained from any team and aggregated into one map, reliance analysis, duplication findings, analysis as at a past date, committee snapshots, and CSV export. Pricing is $8 per user per month, or $80 per user per year (two months free), with a 5-seat minimum and a one-month free trial.

• Upgrade: the subscription is purchased through the Microsoft commercial marketplace — from the app's page in the Teams app store or Microsoft AppSource. Checkout is handled entirely by Microsoft; we never see your payment details.
• Assign licenses: after purchase, assign licenses to the people who need the paid features in the Microsoft 365 admin center (Billing → Licenses), just like any other Microsoft 365 license.
• Manage or cancel: the subscription is managed in the Microsoft 365 admin center under Billing → Your products — seat count changes, switching between monthly and annual, and cancellation all happen there.

6. If Something Looks Wrong