FAQ
Getting started
3 questions
The address of the site you are reviewing. That is it. If it is a staging site behind a password, have those details to hand.
Yes. Mark the project as live or staging so everyone knows which they are looking at — comments on the wrong one are the usual mix-up.
No. Feedbk fetches a real site at a real address, so there has to be something to look at, even if it is a work in progress.
Your clients
5 questions
No. They open the link you send, type their name so you know who left each comment, and start. No password, nothing to install. On a link open to anyone the email is optional — it is only there so they hear when you reply.
That is yours to decide. On a link open to anyone it is optional by default — a reviewer who skips it simply hears nothing back, and is not recognised on a later visit, since there is nothing to recognise them by. Tick “Ask for an email address” on the link to insist on one anyway. Limit the link to addresses or a company domain and the email is the way in, so it is always required.
Yes. Leave it open to anyone with the link, limit it to a list of email addresses, or limit it to one company domain so only people at that company can enter.
Yes. Replace it or revoke it at any time. The old link stops immediately, and anyone using it is asked for a new one.
Their own comments, other client comments on that project, and your replies. They never see internal notes, other projects, or anything about your workspace.
Reviewing
7 questions
A screenshot is frozen. Feedbk serves the real site, so menus open, video plays and your client can browse to a page three clicks deep and comment there.
A pin remembers the element it was attached to, not just a position, so it usually follows the thing it was about. When that element is gone the comment is still there to read.
Yes. A comment remembers the width it was left at, because something being broken usually means broken on one of them.
A round is one pass of feedback. Closing one and starting the next keeps the history readable, so there is no argument later about what was asked for first time.
Yes, up to three per comment — a replacement image or a screenshot of something odd.
Yes, your own. The comment is marked as edited with the time it changed, so nobody is left wondering whether what they read is what was written. Clients can correct their own the same way.
You can delete your own, and a workspace owner can delete anything in the workspace. Deleting the first comment of a thread takes its replies with it.
Your team
4 questions
Owners see every project in the workspace and can invite people and manage share links. Members see only the projects they are assigned to.
Yes. One account can belong to several, with a different role in each — an owner of your own, a member of a client's — and a switcher appears once you are in more than one.
It goes to the project's trash for 30 days. A workspace owner can restore it — a thread comes back with the replies that went with it — or remove it for good. After 30 days it goes on its own. Members and clients have no trash: they delete their own comment and that is the end of it for them.
Remove them from the workspace. Their account stays, because it may belong to other workspaces, and the comments they wrote keep their name.
Privacy and the site itself
3 questions
No. Nothing is installed on your site and nothing about it is altered. Feedbk fetches it and shows it inside the review screen.
No. Each review session fetches the site live, so what you see is what is there now, not a copy from last week.
Encrypted before they are stored, and only ever used to open that project's own site.
Price
2 questions
Nothing, while we are getting started: unlimited projects, clients and reviewers.
We will say so well before anything changes, and nothing you have already put in goes away.