---
title: "Trusted Domains, Front-End Performance Improvements, Gratitude"
date: 2024-11-29
number: 0214
url: https://railway.com/changelog/2024-11-29-trusted-domains
---

# Trusted Domains, Front-End Performance Improvements, Gratitude

Bonjour Hi! 

This is a Canadian Changelog due to our American colleagues being out for a certain turkey or ham consumption related holiday. 

Before they departed for such federal holiday, they told us to say here that they are thankful for you, the developer, for using Railway. For the rest of us- we continue shipping features for you and your Black Friday traffic spikes. 

Now, we go onto the Changelog and put on a Habs game.

## Trusted Domains

We know that some companies desire better organizational controls for the Pro Workspaces that are on Railway. We know that if we were to ask some people about how they feel about those controls- they’d say: *“*blows raspberries* bof”*

To help with this, we shipped the [Deployer role](https://railway.com/changelog/2024-11-15-welcome-to-railway-dot-com) to limit employee access to Infra and [Google SSO](https://railway.com/changelog/2024-11-22-google-auth) for those who would like to login via their Google Workspace, and now… we have Trusted Domains.

For some companies who are growing rapidly on Railway, Railway would make it passively difficult to bring your team to the platform. Admins would have to go through the pain of having to manually invite people to their Workspace. 

[Image: Untitled]

No longer. You can now set a domain to be linked to the Workspace- and any person who makes an account on Railway will be added to the Workspace automagically with the default role you apply. T with a little bit of witch magic made it so that if you already verified your domain for a service, would be already trusted for the Workspace.

You can configure a Trusted Domain within the Pro Workspace settings page today. We’d love to hear more feedback on more corporate level features you’d want to see on the platform.

## Dashboard Performance Improvements

The Railway team would like to avoid being shamed, although, we are no strangers to guilt.

Existential opening aside- there is a certain eagle eyed developer who is looking at front-end performance and going on X calling people out. We would like to avoid being on that list.

Luckily JR, is working on improving the canvas and needs to knock out some performance improvements and refactors before he begins his next project. We tackled unnecessary re-renders are improved a bit to make the product feel more reactive. 

(Still more to go in this department, so report your nits and bugs to Help Station.)

## Gratitude

On a serious note, and *importantly* not a feature, we’ve witnessed massive growth on the product thanks to you.

Your continued support by using and paying for the product means that we all can work on foundational infrastructure for today and the future. For those who deploy day in and out- this is why we show up to ship features every day for.

If you aren’t on Railway today- and if you still read the Changelog and follow along, we’re ever thankful that you are here with us on the journey. *(We hope for you to join us on a later stop.)*

## Improvements and Fixes

- Improved DDoS mitigation measures to our global network infrastructure.
- Move GitHub button above the Google login button
- Add MCR example on Image deploy source
- We now group by regions on the deployments pane
- We now properly prevent you from using replicas if your service is configured with a cron.
- Fixed settings configuration validation in staged changes