Editing a shared HTML report without sending a new link: what step is missing?

Paste HTML, click the text on the page to fix it, then sign in to share a link. When the recipient reopens that same link, they see the saved edits. We'd like critique on two steps: the sign-in step and what happens after an edit.

We work with a lot of internal HTML: reports, briefs, small presentations. We needed one place to collect and share them, so we built NOS, a workspace that holds documents and HTML pages: https://nos-workspace.com/ This is the flow we'd like critique on. You paste the HTML of an existing report, see it rendered as a page, and click the text you see to fix it without opening the code. Pasting, editing and previewing work without an account. To save the page and get a public link, the author signs in. Whoever receives the link opens it without an account. Later the author changes a number and saves again. When the recipient reopens the same link they got earlier, they see the saved version. Nobody has to send a new link. Two questions. Is asking people to sign in at the moment they create the link the wrong point in the flow, or is it fine once they've already tried editing? And when you change a report someone already has, is "reopen the same link" enough, or is there a step you'd expect between your save and their next read?