This question is related to the following two questions:

1. Web 8.5 - Experience Manager Boostrap URL pointing to localhost, how to change to actual website url? by Nicholas Whetmore
2. How to enable XPM button on DXA, SDL Web 8 by Hirokazu Shikata

I can see from the answers to those two questions that the WebsiteRootUrl setting in Topology Manager is used by both:

1. Experience Manager - When using the Enable inline editing for Page TBB, and
2. The Publish Settings Page (in the _System Structure Group) - When using DXA.

My question is whether the WebsiteRootUrl setting in Topology Manager is used anywhere other than is these two places in a standard installation (excluding in any customisations, etc.).

For example, if the URL of the Content Manager changed, and we did not update this configuration, what other problems might we see?

Presumably the lookup when adding Topology Mappings, etc. is done using the CoreServiceRootUrl setting, so I wouldn't expect that to be impacted?

This question is related to the following two questions:

1. Web 8.5 - Experience Manager Boostrap URL pointing to localhost, how to change to actual website url? by Nicholas Whetmore
2. How to enable XPM button on DXA, SDL Web 8 by Hirokazu Shikata

I can see from the answers to those two questions that the WebsiteRootUrl setting in Topology Manager is used by both:

1. Experience Manager - When using the Enable inline editing for Page TBB, and
2. The Publish Settings Page (in the _System Structure Group) - When using DXA.

My question is whether the WebsiteRootUrl setting in Topology Manager is used anywhere other than in these two places in a standard installation (excluding in any customisations, etc.).

For example, if the URL of the Content Manager changed, and we did not update this configuration, what other problems might we see?

Presumably the lookup when adding Topology Mappings, etc. is done using the CoreServiceRootUrl setting, so I wouldn't expect that to be impacted?