Without a login you can do nothing - so do that. Even if you have a login, if they've only given you that and nothing else, then you cannot reasonably be expec

Without a login you can do nothing - so do that. Even if you have a login, if they've only given you that and nothing else, then you cannot reasonably be expected to complete the update on a Friday with no oversight and no support from a team. So don't, if it seems prudent not to. Another commenter mentioned that hopefully you're in a US timezone since that means you'll have the rest of the day to figure things out. So start figuring - compile a text document with links to information about the upgrade process. Cross-reference this with what you know about how the current system operates. Do a solid hour's worth of research and try to determine how the process will go. Identify potential pitfalls: are you going to get stuck behind a prompt for additional credentials, or asked for a license key that you don't have? If the upgrade process fails catastrophically, what's your easiest route to restoring from backup? Is there something you can take snapshots of, as an insurance policy? Call the vendor (hopefully your org has an active support contract) and level with them: you're a support guy too, you're out of your depth (or so you think, anyway) and you need a sanity check and some advice. Perhaps you have internal team members who could help in similar ways (probably not, since you're asking here). If it seems too risky, I just wouldn't do it. Type up a nice note about the research you did, and how you foresee the process being executed. Then notate why you're uncomfortable hitting the big red button, and what you'd need in order to more forward. Then, update your ticket with that note, place it on next week's schedule, go home, and enjoy your weekend. Best of luck.