Projects in Userback act as containers for collecting and managing feedback across different websites or applications, allowing you to tailor settings, and organize feedback by client or versions. This guide will walk you through the different settings available to you, helping you tailor each project to your specific needs.
Accessing Project Settings
Locate and click the settings button at the top-right corner of your Userback project. Here's a quick link: Project Settings
General Settings
Here's a detailed look at what you can adjust under General Settings:
About General Settings
About General Settings
Project Name
This is the identifier for your project. Make it descriptive enough so you can easily distinguish it from other projects.
Description
Add a concise description to give context to the project. This can be particularly useful when managing multiple projects.
Category
Implement categories to streamline the sorting and filtering of your feedback.
How to Edit Categories
How to Edit Categories
You can easily add or edit the categories in each of your projects.
1. Go to Project Settings and Select General
2. Under the Category heading, you have a few options;
Click on an existing category to rename it
Click the x to delete the category, or,
Click the + to add your own categories
3. Click 'Save Changes'
📘Note: You can add up to 20 categories per project.
Workflow Settings
This feature is particularly useful for adapting the Userback workflow to match your task management process from other systems. You can also change the names, colors, and positioning of statuses within your workflow to better fit your needs.
How to Customize Your Workflow Settings
How to Customize Your Workflow Settings
Customize status names, colors, and drag and drop them into their preferred order. To introduce a new status, click the "+ Add Status" button.
📘Note - The Open and Resolved statuses are default workflows for open and resolved feedback. While it is possible to rename these workflows, their position within the workflow cannot be modified.
Automation Settings
Optimize your feedback management with these automation features:
Automatically Assign New Feedback
Set a default user for each type of feedback to ensure it goes to the right person, enhancing response times and workflow efficiency.
How to Automatically Assign New Feedback
How to Automatically Assign New Feedback
Go to Project Settings and Select the Automation's Tab
Under the Default Assignee option, choose team members from the dropdown list to assign them as default assignees for different feedback types based on their roles or expertise.
🔔 You've Got Feedback! Consider enabling email notifications to ensure assignees are informed about new feedback assigned to them.
Reopen Feedback
Enable this option if you'd like feedback items to be reopened when the reporter responds, ensuring nothing slips through the cracks.
Reporter Notification
The Reporter Notification feature automatically sends a customizable confirmation email to users when their feedback is received
How to Enable and Edit Reporter Notification
How to Enable and Edit Reporter Notification
Go to Project Settings and Select the Automation's Tab
Toggle on Reporter Notifications and choose the feedback type
Edit the Subject and Message of the email with your preferred messaging
You can further customize the email content by using template variables, which can help personalize the email with the reporter's name and the feedback link. Simply copy and paste the following into the template to auto-fill:
%%reporter_name%%
%%feedback_link%%
Additionally, you can use markdown syntax to include links in your email. For example:
[Visit our website](https://www.example.com)
[Contact us](mailto:help@example.com)
Click Save Changes
📘Note: By clicking on the Preview button, you can take a quick look at your email as it would appear to the client.
About Unsubscribed Reporters
About Unsubscribed Reporters
When a reporter opts out of email notifications, their unsubscribed status is shown in the Feedback details.
Privacy Settings
Userback helps you collect valuable feedback while protecting user privacy. We provide two methods to ensure sensitive information never gets captured:
Class-Based Exclusions: Add the "userback-ignore" class to any HTML element you want to exclude from screenshots and recordings.
Privacy Settings Configuration: In your project's privacy settings, specify selectors to exclude. For example, add
input[type="password"]to exclude password fields from screenshots.
Tip: you can also set privacy rules for your Session Replays. Learn how here.
User Location Privacy
User Location Privacy
Userback's location tracking, based on user IP addresses, can be pivotal for contextual feedback. However, respecting user preferences, this can be deactivated on a per-project basis for complete anonymity.
Screenshot Privacy Tools
Screenshot Privacy Tools
Empower your feedback collection with visual context while maintaining privacy. Use the .userback-ignore class to hide sensitive elements from screenshots or configure global rules in your project settings.
Advanced Settings
Basic Authentication
If your website or web app requires basic authentication (.htaccess), our servers might not be able to access your site URL including static resources such as images and stylesheets, as such, you will need to configure some basic authentication settings for your Userback Project.
To make your site accessible to our screenshot servers, you can either whitelist our server IPs or provide us with your basic authentication details.
How to Save Your Basic Authentication Details
How to Save Your Basic Authentication Details
Go to Project Settings and Select the Advanced Tab
Under Basic Authentication, click "Add"
Enter your basic authentication details and save
📘Note: Userback does not store any authentication information in plain text
HTTP Headers
If whitelisting IPs isn't feasible for giving the Userback Screenshot Engine access, you can add additional HTTP headers to identify requests from our screenshot servers. This is especially useful when your site is in a protected environment. By adding extra HTTP headers, you can ensure that these requests are recognized and appropriately whitelisted.