Dash Administrators now have the capability to lock/unlock the alias value within Build. When an alias is locked its field will be disabled and can't be changed until unlocked. An alias can be locked at the root and page level.

This was added for a couple of reasons.

1. Some Microsites, especially those on GardnerWeb, utilize manually defined routes in our code-base (removing the /kc/ and /zc/ from the URL). These manually defined routes are mapped to the Microsite's defined alias value in Build. For that reason, if someone were to change the alias value in Build it would break the manually defined route completely. Now with alias locking, we can remove that possibility by preventing the alias from being changed on those particular Microsites.
   
2. Some Microsites are now embedded on non-build pages, like the contact pages. These too make use of the defined alias value within Build to specify which Microsite to embed. Locking the alias value in Build here prevents the same thing from occurring on these embedded Build pages.