Copilot Dashboard migration
Changes to the Copilot website and Copilot Dashboard
Copilot’s New Website 
Starting February 25, 2025, Copilot will be accessible at copilot.app instead of copilot.com.
Redirect Period
Between February 25 and April 1, 2025, copilot.com will automatically redirect to copilot.app, so you may not notice any changes right away.
After April 1
The redirect will end, and copilot.com will no longer be available. Please update your bookmarks and links to copilot.app before then.
Accessing the Copilot Dashboard
The Copilot Dashboard (where internal users log in) now lives at dashboard.copilot.app. There’s no change to how you sign in—your credentials remain the same—just make sure to use the new URL to authenticate.
Impact on Client Portal URLs
Whether or not you set up a custom domain for your client portal, your clients’ experience remains unchanged. By default, client portal URLs have always used the format {businessName}.copilot.app rather than a .com domain, so your clients can continue using the same link as before. Email notifications to clients also remain exactly the same as before.
Migration Action Items
The vast majority of businesses that run on Copilot don't have to do anything to migrate except logging in on the new URL and remembering that Copilot is now on copilot.app.
The only time there may be migration work is if you are using the API directly (i.e. not through Zapier or Make) or if you have embeds or Custom Apps set up. Please see the FAQ below for more information.
Frequently Asked Questions
We’re consolidating the Copilot brand on a single .app domain rather than juggling both a .com URL and a .app URL. This will streamline our branding and reduce possible confusion around multiple domains.
You can contact us at support@copilot.app.
1. Review X-Frame-Options & CSP frame-ancestors
If you've configured HTTP headers to only allow embedding on our current domain, update them.
Example 1:
Change X-Frame-Options: ALLOW-FROM https://copilot.com to X-Frame-Options: ALLOW-FROM https://copilot.app.
Example 2:
Update Content-Security-Policy: frame-ancestors 'self' copilot.com to Content-Security-Policy: frame-ancestors 'self' copilot.app.
2. Update REST API endpoint URLs
Please update all API endpoint references in your embedded application from copilot.com to copilot.app. All other parts of the endpoint URLs will remain the same.
For example, change https://api.copilot.com/v1/clients to https://api.copilot.app/v1/clients.
3. Check for Hardcoded Domain References
Search your codebase for any hardcoded references to copilot.com and update them to copilot.app. This includes absolute URLs, configuration values, and any domain-specific logic.
4. Update postMessage Target Origins
Copilot's App Bridge supports sending postMessages to redirect the parent frame. Any code that sends messages to our platform using window.parent.postMessage(data, "https://copilot.com") should be updated to window.parent.postMessage(data, "https://copilot.app").
5. Check document.referrer Verification
If your application verifies it's being loaded from our domain using document.referrer, update these checks.
Example:
if (document.referrer.includes("copilot.com")) should become if (document.referrer.includes("copilot.app"))