Skip to content

Sources and access

A source is a Confluence Cloud site or a Notion workspace your team has connected. WikiFix reaches each one through people’s own accounts:

StepWhose access
Connecting a sourceThe admin who connects it, signed in with their own Atlassian or Notion account
Reading pages for a scanThe admin who connected the source; each report then shows only what its owner can see
Applying a fixThe member who applies it – the edit is saved under their name in your source

So a report never reaches beyond its owner’s view, and a fix needs the member’s own edit permission on the page, as in Confluence or Notion itself. If the admin who connected a source leaves, or their sign-in ends, its scans pause until an admin connects it again.

A report shows what its owner can see to everyone it’s shared with. If you share a report with someone who can’t open some of its pages in Confluence or Notion, they still see the findings and the quotes from those pages. Share a report only with people who may read what its owner can.

Each member links their own Atlassian or Notion account once per source, the first time they scan or fix something there – it’s how WikiFix knows what that member can see and edit. A source you haven’t linked shows as Sign in to … to scan it.

If a sign-in ends – you changed your password, or someone revoked access – WikiFix asks you to sign in again before it reads that source.

  • Disconnect a source from Admin → Sources. Its scans stop, and the sign-in tokens we hold for it are deleted. Nothing already stored from it is deleted until the team is.
  • Remove a member from Your team. They lose access right away, their scheduled scans stop, and their reports stay readable to admins and to the people they were shared with.
  • Delete the team from Your team. Everyone loses access right away, we delete the team’s sign-in tokens at once, and we delete the team’s data 30 days later. A few records follow their own schedule, as the DPA lists.

What we store about connections and accounts, and for how long, is in the Privacy Policy.