Create Accountor Login
Docs

Platform Connections

Part of the MountDev Ops Workspace documentation. Updated November 8, 2026

MountDev Ops Workspace documentation | Updated November 8, 2026

Our Commitment MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Some services work for every account at once, such as one bot check on every form. Their keys are Platform Connections. They are kept in one account only, the controller account, and nowhere else.

Who Sees This

Only the controller account, and only its owners and admins. On Settings, in the Connections card, on the Connected Services tab, the controller account has a Platform Connections section above its own services. Every other account has no such section and sees nothing about it.

What Is Kept There

  • Cloudflare, for the websites and domains we look after (the DNS key).
  • Cloudflare Hosting Storage.
  • Google Search Console, Google PageSpeed, Wordfence, and Google Web Risk, for the checks and reports on every site.
  • Ahrefs, for visibility reports.
  • A Google Sign-In Client, for deliverability reports.
  • Cloudflare Turnstile, the bot check on forms, which stays in Forms Settings and shows here with its last use.

Each one is connected the same way as any Connected Service, with a key that is sealed and never shown again. The section shows when each was last used (action core.connections.list).

What Is Never Kept There

Your email, texts, calls, and payments always go through your own accounts with your own providers. A Platform Connection never sends, texts, calls, or charges for anyone. An account that has not connected its own provider waits with the step to connect one.

How They Are Used

When the platform needs one of these keys for a request, it asks the controller for that one service, uses it for that request, and keeps nothing. Each use is written in the controller's Activity Log by service name, at most once an hour, never with the key. If an account has its own connection of the same kind, its own always comes first for that account.

No View into Any Account

Holding Platform Connections does not let anyone see another account. The controller account's people see only the controller's own data and when each platform connection was last used. No screen, search, report, export, API action, or AI agent in any account reads another account's records. The only way into an account is a temporary access grant that the account's own owner or admin gives a named person, with an end time, recorded in that account's activity log.

Moving a Key into Platform Connections

A key moves only when the owner of the controller account enters it there. Until then the platform keeps using the key it uses today, so nothing stops working while keys move. Nothing is deleted when a key moves.

Ask Us Anything

We’d love to hear from you!