There’s a new Profile tab, and it’s not a Settings subsection pretending to matter. It holds four things: your bio, your goals, who you’re actually writing for, and any notes you want to leave about your own voice.
Fill it in once and it feeds the two AI transforms that create genuinely new material: hook variants and Note ideas. AI Quick Edits and the rewrite/newsletter/essay transforms don’t touch it, because those are editing text you already wrote in your own voice. There’s nothing for a profile to add there.
Register a URL and NoteSurge will hit it with a POST the moment a note is scheduled, published, or fails. It’s the same primitive Zapier, n8n, and Make automations run on.
The signing secret stays visible in Settings any time. It’s not a one-time reveal, because you’ll need it indefinitely to verify signatures, the same choice Stripe and GitHub made for their own webhook secrets.
An org owner can set a teammate to one of three levels now: viewer, who can look but not touch; contributor, who can draft and edit but not schedule or publish; or full publisher.
Before this, anyone on the team could do anything anyone else could, which is fine until it isn’t.
Any draft, pending, or failed note in Queue can be shared as a link now, and whoever you send it to can leave a comment with no NoteSurge account of their own.
Generate the link, send it, and their feedback shows up in your queue the moment they post it.
One catch worth knowing: the link only shows once. Navigate away before copying it and you’ll have to regenerate a new one, not recover the old one. The raw token is never actually stored, only its hash.