# Review a two-factor setup before changing the publishing device

Original constructed teaching cases. No real accounts, participants or customers.

S1 — Constructed new phone: the app was installed, but no account entry has been verified. Decision: keep the existing access route and complete the official setup/readback deliberately. Result: setup pending, not a verified migration; no secret is copied into the record.

S2 — Constructed product dependency: a member plans to disable two-factor authentication while retaining Sales Navigator access. Decision: read the documented dependency before changing it and resolve the actual access problem through the supported route. Result: a held workaround, not an unexplained product failure.

S3 — Constructed public proof: a draft screenshot contains a setup key and code. Decision: omit that screenshot and describe the checked status without secrets. Result: a safe teaching record; no claim that an exposed real key has been revoked or that the account is now fully secure.