Confluence is where SmartChoice keeps the record of every customer it serves. SmartTile writes that record for our engineers — account pages, site-survey reports and the platform documentation library — from the same data that runs your monitoring. It is SmartChoice's Confluence; you do not connect yours.
When an engineer picks up your outage at 2 a.m., the first question is what is at this site and how is it wired? At most providers the answer is scattered across a billing system, e-mails and someone's memory. SmartChoice keeps a Confluence page per customer account, and SmartTile writes it from the systems of record instead of an engineer retyping them.
<Customer> — Account #<number> in SmartChoice's Customers space, from the live Customer Page Template: services and child accounts from Rev.io (pricing stripped at the source), SmartTile organizations, locations and circuit devices, and the SmartSurvey write-up and photos. One sub-page per organization when the account is split.
When a SmartSurvey is published, its report and photos land on the site's page. Only the managed region is ever rewritten; updates to an existing page are off by default and paused on any conflict.
SmartTile's policies, runbooks and guides are published to SmartChoice's product space, labelled by classification. Auditor-only documents are read-restricted to SmartChoice's compliance and executive groups.
| The moment | Without it | With SmartTile + Confluence |
|---|---|---|
| A new engineer takes your ticket | They ask you what is at the site. | Your account page lists the locations, circuits and survey notes already. |
| An engineer adds a note by hand | The next automated refresh wipes it. | A section a person edited is detected and skipped — never overwritten. |
| Two people refresh at once | The later write silently wins. | Publish re-checks the live page version against the preview and refuses a stale write. |
A SmartChoice engineer enters the Rev.io account number (required) and optional survey; SmartTile pulls Rev.io, SmartTile inventory, the SmartSurvey and any attached e-mails.
Every page is rendered for review first, with the section-by-section plan: replace, fill, unchanged, or skipped because a person edited it.
Only within 24 hours of the preview, and only if nobody changed the page since. Attachments are updated in place.
Every run is kept with its plan and result; a test mode writes to a [TEST] page first.
/rest/api/content?title=…&spaceKey=…Find an existing page by title/rest/api/content/{id}?expand=body.storage,versionRead the live page before merging/rest/api/contentCreate a page from the template/rest/api/content/{id}Write the merged page at the next version/rest/api/content/{id}/child/attachmentUpload survey photos and generated files/rest/api/content/{id}/labelClassification labels (documentation library)/rest/api/content/{id}/restrictionRead restriction for auditor-only documentsThe builder and every Confluence write path are limited to SmartChoice super admins. No tenant can reach them.
Rev.io pricing is removed before the page is built; phone-system credentials never reach the SmartTile server.
Managed regions are fenced with markers and a content signature; everything outside them is preserved byte for byte.
If the auditor-only group restriction cannot be applied, the page is restricted to the publishing account alone.
| Question | Answer |
|---|---|
| “Can SmartTile publish to our Confluence?” | Not today. This integration writes only to SmartChoice's Confluence. |
| “Can we see our page?” | It is SmartChoice's internal record; ask your account team for a copy of anything you need. |
| “Can we get our site-survey report?” | Yes — through SmartSurvey's PIN-protected share link, which does not depend on Confluence. |