Changing the sign-in address

Hi @syuroff_CORP,

Great question! I have a list of some of the considerations that I'm sharing from this article. I'm sure not all of them will apply, but I hope it's helpful. Are there other use cases not covered here that you're wondering about in particular?

• There’s no down-time for the account. After you save your sign-in address, the change will take effect immediately.
• If your team signs in to 1Password with single sign-on (SSO), the administrator for your team’s identity provider will need to update the redirect URI in the IdP. Team members will need to re-link apps and browsers to their accounts. This may require an owner or administrator to initiate recoveries for any team members that aren’t using a 1Password app.
• If your team uses the 1Password SCIM Bridge, you’ll need to regenerate the scimsession file and update the bearer token.
• If you’ve added a 1Password tile to your Okta dashboard, you’ll need to update the sign-in URL.
• Team members will need to download a new copy of their Emergency Kit that contains the new sign-in address. Only the sign-in address changes. Secret Keys and other details remain the same.
• Team members who bookmarked 1Password.com will need to update their bookmark with the new web address.
• For team members signed in to a 1Password app, the account change will be recognized automatically if they unlock the app within 30 days. Team members who miss this 30-day window or are using older versions of 1Password will need to sign back into their accounts in the app.
• Any Secrets Automation workflows will need to be recreated. Specifically, service account tokens will need to be rotated, and the 1password-credentials.json file for Connect servers will need to be recreated.

Very helpful, thanks for that link.  It seems like it should be completely transparent as far as the app and browser integrations are concerned, as there's no mention of them in the article.