Content Snare product changelog

Hey [First name], Here's what's shipped in Content Snare since our last update. We’ve had three releases since our last update, so this one’s a bit longer than usual. Personal access tokens for your AI tools You can now connect your own AI assistant, scripts and automations to Content Snare with a personal access token. Generate a token, paste it into your tool, and it can work with your requests and clients through our API. It's under Settings → Security → Personal Access Tokens, where you can: Permissions: choose what each token can do, like read requests, manage clients or review answers. Expiry: tokens expire automatically. Admins pick how long, and editors' tokens last 90 days. Rotate and revoke: replace a token or switch it off at any time. To connect Claude to Content Snare, paste the following into the Claude Code tab. This won't work on Chat. >> Follow the instructions at https://pages.contentsnare.com << If you don't already have the API enabled, you'll need to ask the support team for access. Compressed sections You can now group small questions together so your client answers them and submits them in one go. It's handy for small groups of questions like "first name, last name, email" where clicking submit after each one is overkill. Think of it as a question group. To turn it on, open a section's Options in the request builder and switch on Compressed section. Submitting: your client fills in the whole section and submits it once. If anything's still missing, they're told before they submit. Reviewing: approve the whole section with Approve All, or reject single questions. Your client sees the rejected ones highlighted and resubmits just those. The rest stay as they were. Comments: comments can be added to each question individually. Your team can also open View All Comments to see every comment in the section in one list, labelled by question. Copy all answers: grab every answer in the section in one go. Personalised instructions You can now put variables or placeholders in instruction areas. Type /variables in the instructions editor to add one. You can use the client's name, salutation, email and company, the request owner, the due date and folder, and your company's details. Set them up in a template and every request you send from it is personalised. Request expiry Requests can now expire on their due date. Once a request expires, your client can't open or download it, and they see a message asking them to contact you if they need more time. To set it up, turn on Close client access after the due date when you create a request. It works on standard, quick and recurring requests, and it's off unless you turn it on. Timing: a request expires on its due date, at the same time of day you published it. Expired status: expired requests show as Expired on your dashboard, and you can filter by it. Reminders: if you're using the default Due Today email, it now tells your client the request has expired*. No reminders go out after that. Plan limits: an expired request stops counting toward your active request limit. * If you've edited your Due Today email, it won't mention the expiry, so check the wording before you use this. A better table view on your dashboard The table view on your requests dashboard has been rebuilt. We think it's a big visual upgrade. You can now: Group and sort: group your requests and sort each group on its own. Frozen columns: the request name stays in view while you scroll sideways. Progress: see how many questions are answered, approved and waiting for review. Quick settings: hover a request to change its due date, owner, folder or reminders without opening it. Unread comments: the unread comment count shows next to the request name. Requests waiting for your review are tinted, and the row buttons have moved into the ⋯ menu. Your other lists use the same table now too: recurring requests, templates, files, clients, folders and your team. New cards and stage