Skip to main content

Configure Your Feedback Settings

How to set up the Workflow, Automation, Privacy, and Advanced tabs under Feedback > Settings for a site.

Written by Jon

Where these settings live

Go to Feedback > Settings for the site you want to configure. The settings allow you to update various feedback settings including the Feedback Widget, Email Forwarding, Workflow, Integrations, Automation, Privacy, and Advanced.

This article covers the last four: Workflow, Automation, Privacy, and Advanced.

See Create and edit your Userback widget and Email Forwarding for instructions on configuing your Feedback widget and how Email forwarding works.

The Integrations tab is covered by the full Integrations collection: see How Integrations Work in Userback for the overview, then the article for whichever tool you're connecting.

Not the same as Site Settings. Feedback > Settings configures how this site collects and manages feedback. Site Settings controls general site info, domains, and members who have access to the site. Site settings are opened from the Site card's ··· menu or Site Settings directly. See Site Settings: General, Domains & Members.

Workflow

The Workflow tab controls the statuses a feedback item can move through and can be customized to fit your own internal feedback workflow:

  • Open is the default status every new feedback item starts in.

  • Below it is your list of custom statuses, for example In Progress and Under Review. Drag a status to reorder it, or use its remove control to delete it.

  • Click Add status to create a new one.

  • Resolved is a fixed field at the end of the list, marking an item as done.

You can land on this same Workflow settings page from two other places, not just the Feedback > Settings sidebar: a feedback item's status dropdown has a ⚙ Manage Status link, and the board's swimlane settings-cog opens it too. All three are the same page, so a change you make from one place applies everywhere.

Automation

The Automation tab has three parts: routing new feedback, reporter notifications on submit and resolve, and a CSAT-on-resolve survey.

Triage rules for new feedback

For each feedback type General, Bug, Task, and Idea, you can set:

  • Assignee: who new feedback of this type routes to by default.

  • Due date: how far out to set the due date automatically, from a dropdown of preset timeframes.

Below that, the Auto Categorization toggle turns on AI-based categorization: Userback compares new feedback against your existing categories and tags it with the closest match. If nothing matches closely enough, the item is left uncategorized.

This works best when your category library is reasonably broad so it is worth manually categorizing feedback as it comes in so that the AI will learn and start using more categories over time.

Reporter automations

  • Confirmation email: A toggle that emails the reporter to confirm their feedback was received. Click Edit template to customize the subject and message, insert template variables, or add a markdown link.

  • Reopen Feedback: A toggle that automatically reopens a resolved item if the reporter replies to it again, so a follow-up doesn't sit unnoticed in a closed item.

  • Resolve & Auto-reply: A toggle that adds a Resolved & Auto-reply option to the status dropdown. Choosing it resolves the item and sends a customizable reply in one step, with the same template-variable and markdown-link options as the confirmation email.

    This reply's template can optionally reference one of your surveys, but sending it is a manual choice made at resolve time, unlike the automatic survey send described next.

Reporter satisfaction survey (CSAT-on-resolve)

The reporter satisfaction survey, is separate from the manual Resolve & Auto-reply option above: when turned on, it automatically emails a satisfaction survey to the reporter a set delay after their feedback is resolved, without anyone having to choose that reply template at resolve time.

  • When feedback is resolved, email the reporter with a satisfaction survey: The Toggle is off by default for every site, including new sites. Turn it on here if you want the survey sent automatically.

  • Survey: Which CSAT-type survey to send once the toggle is on. New sites come with an auto-created Feedback Resolution CSAT survey ready to select, or choose + Create another CSAT Survey.

  • Send it: The delay after resolution: Immediately, 15 or 30 minutes, 1, 2, 6, or 12 hours, 1 or 2 days, and more.

  • Trigger: Ask me each time shows a "Feedback resolved 🎉" confirmation dialog every time you resolve an item, asking whether to send the survey, with Don't send and Send survey buttons and a link back to this page. Always send skips that dialog and sends automatically on the schedule above.

  • Edit Email: Customize the survey invitation email itself.

Privacy

The Privacy tab controls what Userback captures and stores:

  • Ignore user location: A toggle that stops Userback from resolving a reporter's IP address to a location.

  • Restrict PII from MCP responses: A toggle that keeps personally identifiable information out of responses returned through the Userback MCP server.

  • Screenshot masking rules: Will provide a list of CSS selectors and the rule applied to each (block, ignore, or mask), so sensitive on-screen content never appears in a captured screenshot. Click + New Rule to add one.

  • Session Recording rules: The same selector-and-rule shape as above, applied to session replay recordings instead of screenshots.

You can also mark an element for exclusion directly in your site's HTML with a userback-ignore class, as an alternative to adding a rule here.

Advanced

The Advanced tab covers two things needed for sites that sit behind extra network security:

  • Basic authentication: For sites protected by HTTP basic auth (for example, .htaccess), click Add basic auth and enter the credentials so Userback's screenshot service can still reach the page. Userback doesn't store this in plain text.

  • HTTP headers: Click Add header to send a custom HTTP header with Userback's screenshot requests, useful when a protected environment identifies allowed traffic by header instead of by IP whitelisting.

What's next

Related articles

Did this answer your question?