Userback UAT process

During the user acceptance testing (UAT) phase, we ask you to validate deliverables and key functionality using Userback, our online feedback tool. We'll set up one Userback project (or workspace). There are two ways to submit feedback, and this guide covers both:

• Part 1 — Installing and using the extension without a Userback licence (Extension Key method)
• Part 2 — Using a full Userback licence (username and password)

Not sure which applies to you? If we've sent you a username and password invitation, use Part 2. If we've given you an Extension Key instead, use Part 1.

Part 1 - Installing & Using the Extension (No Licence Required)

This method is for testers submitting quick feedback without a full Userback account. It uses a unique Extension Key per site/project, which we'll share with you. This is the fastest way to onboard testers, and there's no limit on how many people can use it.

Step 1 — Install the Browser Extension

Install the Userback extension in Google Chrome or Microsoft Edge (the two supported browsers).

For Microsoft Edge: 

Once installed, click the Extensions icon in your browser toolbar and switch on ‘Show in toolbar’ so the Userback icon is always visible.

For Chrome: 

1. Select the three vertical dots
2. Select Extensions, Visit Chrome Web Store
   

3. Once you are in the Chrome extension site, type Userback into the search bar and select Userback: Visual Feedback & Bug Report

   

   4. Click on the Userback extension

   

   5. Now select Add to Chrome

   

   6. Then click Add Extension

   

   7. On the top right, click Extension icon. Then click the pin to save the extension so its visible in the browser

   

   8. Once the pin is selected, the extension is now visible

   

   9. Please then follow the installing the Browser extension key when signing in using the key link.

Step 2 — Log in with Your Extension Key

1. Click the Userback icon and log in by clicking the 'Sign in with a key' link
2.  Add the Extension we've provided you for your project.
3. If you're testing across multiple projects, you'll need to sign out and sign back in with the relevant key each time you switch projects.

Step 3 — Update Your Profile

1. Click the extension icon and go to ‘My Profile’ by clicking the round circle top right.
2. Update your name and email address, then save.

Step 4 — Logging a Bug

1. Go to the page you'd like to report feedback on, then click the Userback icon in your top tool bar.

2. Choose to report via Screenshot or Video Recording.
3. In the panel on the right-hand side, select the correct site/project at the top.
4. Leave ‘Assign to’ set to Automatic.
5. Fill in the Title and ‘Leave a comment’ fields.
6. Important: Please add the URL at the top of the page you are providing so we know where to look.
7. Use the toolbar at the bottom of the screen to draw or add text on the screenshot.
8. Click Submit.

Note: screen and video recording are only available through the browser extension — this isn't an option if you're logging bugs through the Userback app.

Part 2 — Using a Userback Licence (Username & Password)

We'll provide up to three (occasionally more) full Userback licences per company. Full licence holders can manage the bug workflow directly in Userback — editing, commenting, and moving bugs through each stage from identification to resolution.

We'll email an invitation to each nominated tester to set up a username and password. Invitations expire after 72 hours, so please action these promptly.

With a full licence, you can log bugs two ways:

Option A — Logging Bugs via the Userback App

1. Log into https://app.userback.io/
2. Select the relevant site/project, then choose Feedback.
3. Click the + button in the top right corner.
4. Fill in the Add Feedback form, expanding the session info section to add the page URL.
5. Click Create.

Note: screen and video recording aren't available through the app — only through the browser extension.

Option B — Logging Bugs via the Browser Extension

Full licence holders can also use the browser extension for the added benefit of screenshot and video capture. Follow the same installation steps as Part 1 (Steps 1 and 3), but log in using your Userback username and password instead of an Extension Key. Then follow Step 4 in Part 1 to log a bug.

Viewing & Tracking Bugs

We recommend using Board View for the best visibility. Under Status, click All to make all Open, Under Review, and Resolved are showing on the board.
 

Bugs move through the workflow in this order:

• Open — Dataweavers owns these and works on them
• Under Review — you own these; re-test until you consider them resolved
• Resolved — mark as Resolved, or move back to Open with comments and screenshots if not fully fixed
• Existing Bug — if there are any bugs found that also exist in your production live site, they will be added here.

We'll flag blockers for go-live using Priority: High (orange flag) or Urgent (red flag). You can filter by Priority if that's helpful.

Top Tips for Effective Bug Logging

• Clearly explain expected behaviour vs. what you actually saw — this helps us validate the bug faster.
• If you have a suggested fix or pointer, add it as a comment on the bug — we appreciate the extra context.
• Please make sure the page URL is also saved as part of the initial bug reported.

FAQs

What's the difference between the licence method and the Extension Key method?

The licence (account) method suits testers who'll manage the bug workflow in Userback — editing, commenting, and moving bugs through each stage. We provide three full licences.

The Extension Key method suits quick feedback from a larger group — annotated screenshots, videos, and comments, without needing a full account. There's no limit on how many testers can use it, so it's an easy way to bring more people on board mid-testing.

Will session replay be disabled for browser extension users? Is this feature needed?

Session replay isn't supported via the browser extension, as it's designed for quick capture (screenshots, recordings, annotations) rather than detailed behaviour tracking.

What optional user data gets captured and shared in Userback?

Userback can optionally capture details such as name/email, page visited, clicks, time on page, and user type. This helps us better understand each bug logged. You choose what's collected.

Userback can also be customised to capture testing-specific data, including:

• Test group (e.g. Beta testers, internal QA, external users)
• Feature being tested (e.g. new search bar, updated checkout flow)
• Test version (e.g. v2.1-beta, staging build)
• Bug or issue type (e.g. UI glitch, performance lag)
• Steps taken before feedback (e.g. clicked ‘Submit’, filled out form)
• Environment (browser type, device, operating system)
• Feedback tags (e.g. ‘confusing’, ‘broken’, ‘slow’)

Will project-level access be enforced?

Yes. Our Userback Administrator sets specific access levels. Client-side users are invited as collaborators and restricted to your workspace only.

Will we need to use the extension on an ongoing basis once we're live?

No. Once UAT is complete and you've gone live, the extension can be removed. Your workspace will be archived, and all feedback exported and saved for you to access later if needed.