The team needed to stop doing Goodword work from a pile of old email addresses.
I asked everybody to update the address attached to our project tracker. I also told them to watch for invitation emails and accept them so the changes could take effect.
The company name had changed before every tool did. That is normal. A brand can be decided in one meeting. Accounts and permissions have to be changed one system at a time.
The work included company email, shared services, administrative addresses, and the tools used to build and organize the product. Each change needed an owner and a quick check afterward.
Changing an email can create duplicate users if the service does not recognize the existing account. It can also leave files under the old identity or remove access somebody still needs.
We were a small team, so the migration did not require a large IT project. It still required a list.
The private record includes individual addresses, invitations, and service configuration. Those details stay out of this article.
The public-safe event is the company transition. Goodword was no longer only the name on a product plan. It was becoming the identity the team used for daily work.
The same week also included technical work on an external connection and the normal stream of product decisions. The email change sat beside that work rather than replacing it.
We could verify the migration by opening the tool again under the new address and checking the same projects and files. If access was missing, the old account still gave us a reference while we corrected the invitation or ownership setting.
I posted the instruction in the general channel. Update the address. Accept the email. Tell me if something does not work.
Then we moved through the tools one by one.