Doc Drift for Confluence

Support

Version 1.0 · Effective November 1, 2026

Doc Drift for Confluence is a Confluence Cloud app from ARCH BADGER 500, LLC. This page explains how to get help.

How to get help

Email support@archbadger500.com.

Please include:

  • Your Confluence site URL, for example yourcompany.atlassian.net
  • The app version. A Confluence admin can find it under Apps → Manage your apps.
  • The page link, and for flag problems, the repository and pull request number
  • For webhook problems, the status code GitHub shows under the webhook's Recent Deliveries
  • The steps to reproduce the problem, and what you expected to happen
  • Screenshots or error messages

Never send API tokens, passwords, your webhook secret, or other secrets. We will never ask for them.

You can also contact Atlassian Support. Atlassian passes app issues on to us.

How to set up and use the app: see the documentation.

Support hours and response targets

We answer support email Monday to Friday, 9:00 AM to 5:00 PM US Central Time, excluding US federal holidays.

Severity Example First response
Critical The app is down for everyone, it changes pages beyond its own properties, or there is a security issue Within 24 hours, Monday to Friday
High A main feature is broken or flags are clearly wrong Within 2 business days
Medium A feature works only partly, or there is a workaround Within 3 business days
Low A question, a cosmetic issue, or a feature request Within 5 business days

The full terms are in our Service Level Agreement.

Report a bug or request a feature

Email support@archbadger500.com. Put "Bug" or "Feature request" in the subject line.

A public tracker is coming later. Until then, email is the only channel, and we reply to every request.

Security issues

Email support@archbadger500.com with SECURITY in the subject line. Security reports are handled as Critical.

Please describe the issue and how to reproduce it. Don't include real customer data or secrets.

FAQ

What permissions does the app ask for?

  • Read pages (read:page:confluence), to find code references on them
  • Page events (read:confluence-content.summary), to know when a page is created or edited
  • Read and write content properties (read:confluence-props, write:confluence-props), only for the app's own properties. This cannot edit page text, titles or labels.
  • Edit pages (write:page:confluence), to save those properties through Confluence's v2 API, and to create or update the app's own weekly digest page when an admin turns that on for a space. The app does not edit any other page.
  • Digest restriction check (read:content-details:confluence, read:content.metadata:confluence), only for that optional digest. The app reads whether a flagged page and its parent pages have view restrictions. It does not change restrictions and does not store them.
  • Search (search:confluence), to find flagged pages with CQL
  • App storage (storage:app), for settings and the reference index

The app asks for no permission to call servers outside Atlassian.

Does the app change my pages?

It never changes page text, titles, labels or comments on your own pages, and it never moves or deletes pages. It saves its own content properties on pages it flags: a summary (ab500_drift_v1) you can search with CQL, and the byline text. When an admin turns the freshness marker on (off by default), it also saves ab500_drift_freshness_v1 (a status and a time only) and adds one sentence to the byline tooltip: "Readers and Rovo should treat this page as possibly stale." That sentence is stored on the byline property, not in the page body. If an admin turns on the weekly digest, the app creates and updates only its own digest page in each listed space.

Does the app read my source code?

No. GitHub sends a notice for each push. The app reads only the repository name, branch, the names of changed, added and removed files, the pull request number from the latest commit message, the commit id and the time. It never receives code, and it doesn't store commit messages or author names or emails.

If you use the Doc Drift GitHub Action and set its optional CODEOWNERS input, the Action may also send GitHub team slugs such as @org/team from your repository's CODEOWNERS file. The Action does not send or store individual GitHub usernames or email addresses, and the app does not store them if they are present. A team slug can include a person's name. The popup shows the team slugs until someone clears the flag. A repository webhook does not send them.

Does the app use AI?

No. Matching is fixed rules in the app's code. The app sends nothing to an AI model.

Why isn't a page flagged?

  • The page hasn't been edited since the app was installed. The app indexes a page when it is created or edited, so older pages are checked after their next edit.
  • The page's space isn't mapped to the repository in the app's settings, or the file matches an ignore pattern.
  • "Only merged pull requests" is on, and the push wasn't a pull request merge.
  • The push wasn't to the repository's default branch, or GitHub didn't deliver it (check Recent Deliveries; a 401 means the secret doesn't match; a 400 means the notice couldn't be read, so check the webhook's content type).
  • The match score was below the threshold, or someone marked those references "Not relevant" on that page.
  • More than 25 pages matched the push. The app flags at most 25 pages per push.

Who can clear a flag?

Anyone who can view the page. "Still accurate" marks the page verified until a later pull request flags it again. "Not relevant" also stops the same references from flagging that page again.

Where is my data stored? Does anything leave Atlassian?

Doc Drift is built on Atlassian Forge and runs entirely on Atlassian's cloud. Settings, the reference index, match details, and the webhook secret are kept in Forge storage and Forge SQL, in your site's data residency location. The content properties are kept on pages in your Confluence site: the summary, the byline, and, only when an admin has turned the freshness marker on, ab500_drift_freshness_v1. GitHub team slugs from the optional CODEOWNERS input, when you use it, are kept with the flag detail in Forge storage until the flag is cleared. We run no servers of our own, and the app makes no calls outside Atlassian.

The one exception is optional: a site admin can let outside AI tools use the app's read-only tools through Atlassian's MCP service. This is off unless an admin turns it on. The details are in section 5 of our Privacy Policy.

How does licensing work?

Doc Drift is sold through the Atlassian Marketplace. Pricing, and any free tier, are shown on the app's Marketplace listing. Atlassian handles billing and licenses.

If a site's license isn't active, the app doesn't index pages or act on GitHub notices, the byline says "Doc Drift license is inactive.", and the settings page shows a warning.

How do I uninstall the app, and what happens to my data?

A Confluence admin can uninstall it from Apps → Manage your apps. Delete the webhook in GitHub too.

When the app is uninstalled, Atlassian's Forge platform deletes the app's settings and index for your site. Atlassian keeps a deleted copy for 28 days. A reinstall starts with the default settings and an empty index. If you reinstall and want your old data back, email us within 21 days of the uninstall and we will ask Atlassian to restore it.

The content properties are saved in Confluence itself, so they stay on flagged pages after an uninstall. A Confluence admin can remove them with Confluence's REST API: DELETE /wiki/rest/api/content/{id}/property/ab500_drift_v1, DELETE /wiki/rest/api/content/{id}/property/ab500_drift_byline_0ddac1f1, and, when the freshness marker was saved, DELETE /wiki/rest/api/content/{id}/property/ab500_drift_freshness_v1 (or, on the v2 API, DELETE /wiki/api/v2/pages/{id}/properties/{property-id}). While the app is installed, the CQL search ab500DriftSchema >= 1 finds every marked page. We also provide a script that finds and removes these properties, including after an uninstall (see Removing the App's page properties), or email support@archbadger500.com and we'll help. See section 6 of our Privacy Policy.

Policies