What the Hub May Call in Your Account
Part of the MountDev Ops Workspace documentation. Updated November 13, 2026
MountDev Ops Workspace documentation | Updated November 13, 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.
Every update passes all 3,965 automated checks before it ships, and every screen change is walked through before release.
Off Until You Turn It On
The MountDev hub is the engine behind a few services, such as email that arrives at a support address and the notices a team sees on its bell. For a provider's own account, the hub can call your workspace for four things, and each is off until an owner or admin of your account turns it on. Nobody else can turn one on, and an AI agent or an API key cannot.
- Mail: an email sent to one of your support addresses is filed in your Helpdesk as it arrived. The hub can only send mail in. It cannot read anything back.
- Bell: a notice for one of your people appears on their bell. Write only.
- Owners: the hub can ask for the email addresses of your owners, and nothing else about them or your records.
- Health: how fast your workspace answers, as times and counts only.
Settings, Connections lists them. See Which Hub Calls Are On shows the four (action core.hub_routes.read), and Let the Hub Call for One Thing turns one on or off (action core.hub_routes.set). Turning one on is written in the Activity Log with who did it.
What It Never Does
Turning a route on never gives the hub a view into your account. No route returns a client, a ticket, an invoice, a file, or a key. The hub's other calls, such as keys, imports, and records, are never open to your account at all, and a platform's own controller account has none of these routes.