Access FM Dojo from locked-down organizations
FM Dojo should be enabled through an approved IT allowlist, managed browser policy, or installable web app deployment. It should not be positioned as a way to bypass a company firewall or content filter.
IT allowlist
Best first step for organizations that block unknown SaaS tools. Ask IT to allow FM Dojo as an approved developer productivity site.
Installable web app
After the origin is allowed, users can install FM Dojo from Chrome, Edge, Safari, or mobile home-screen flows and launch it like a desktop app.
Managed browser app
IT can deploy FM Dojo as a managed web app through Chrome Enterprise, Microsoft Edge, Intune, Jamf, or similar endpoint tooling.
Required allowlist entries
Use the smallest allowlist that matches how the organization manages SaaS access. These entries are for the FM Dojo web app itself, not for private FileMaker Server access.
https://www.fmdojo.comPrimary app, authentication, static assets, and product workflows.
https://fmdojo.comCanonical domain redirects and links.
https://*.fmdojo.comCustomer sites, future app subdomains, and enterprise routing when enabled.
wss://www.fmdojo.comReal-time browser features when a network proxy separates WebSocket policy from HTTPS.
Optional allowlist entries
These are only needed when the organization wants billing self-service or community access from managed devices.
https://billing.stripe.comHosted billing portal for payment methods and invoices.
https://fmdojo.discourse.groupCommunity forum links from the app menu.
Installable web app
Install FM Dojo after the organization allows the FM Dojo origin. The installed app still uses the same approved domain, authentication, cookies, and network policy.
Chrome or Edge
Use the install icon in the address bar, or choose the browser menu and install this site as an app.
Managed devices
IT can deploy FM Dojo as a managed web app through browser or endpoint management after approving the domain.
iPhone or iPad
Open FM Dojo in Safari, use Share, then Add to Home Screen.
Security review packet
Use this summary when an IT or security team asks why FM Dojo should be unblocked.
- Business category: developer productivity, FileMaker development, and team workflow tooling.
- Primary data path: user browser to FM Dojo over HTTPS.
- Server-management path: private FileMaker Server access should use an approved connector, reverse tunnel, cloud command channel, or isolated VPN worker.
- Authentication: FM Dojo account sessions use normal browser cookies over HTTPS.
- Installed web app: same origin, same login, same allowlist requirements as the browser site.
Private server access
Allowing FM Dojo in a browser does not automatically grant access to a FileMaker Server behind a firewall.
For FileMaker Server management, keep the private-network access path separate from the user-facing web app. Use an outbound connector, customer-hosted reverse tunnel, cloud provider command channel, site-to-site VPN into an isolated segment, or a dedicated per-customer VPN worker.
Read firewall access guidanceNeed a formal unblock request?
Use the technical support path for allowlist evidence, procurement review, or customer-specific deployment questions.
Include the organization name, the blocking product or proxy if known, the required domain format, and whether the request is for browser access, managed web app deployment, or private FileMaker Server management.