BOTLOBBIESIs linking Epic the same as signing in to the website?
No. Epic linking authorizes an Epic identity for the bot setup. Website login identifies the web account managing saved bots and access. Completing one does not mean you have completed every step required by the other.
Recognize the different destinations
The Epic linking flow generates an authorization request and waits for confirmation from Epic. The website account form accepts its own sign-in details or supported recovery process. When you see a request for an identifier and web password, do not enter an Epic code as if it were a password. Likewise, receiving a website verification email does not authorize a new bot account on Epic. Each screen should state which relationship it is establishing and which account the result will affect.
Choose the recovery path that matches the failure
If you cannot remember your website password, use the web account's password recovery rather than generating another Epic device code. If the panel says the bot's Epic authorization needs attention, use that bot's linking or recovery action rather than creating another web username. If you can log in but do not see the expected saved bot, first check which website account is signed in and which bot record was claimed. Repeating an unrelated authorization can make the original ownership question less clear.
Confirm each step by its own result
A successful website login should reveal the account context and permitted saved records. A successful Epic approval should show the linked Epic identity in the relevant setup. A connected bot should then provide a separate connection checkpoint. Reading those results individually prevents the assumption that one success message guarantees a ready party. If help is needed, name the exact screen that fails and the expected next step, without sending passwords, login links, or temporary Epic authorization material to explain the difference.