Quick start

The shortest real path from signing in to your client's first comment. Nine steps, nothing spare. It assumes your agency already exists — the operator creates it and sends you the credentials, because Pinfolio has no self-service signup.

1. Sign in to the administration

Open /admin on your agency's address — either the subdomain {slug}.{platform host}, or your own domain if you already have one set up. You sign in with the e-mail and password the operator gave you.

https://your-agency.example.com/admin

The administration is in English

Labels and buttons in /admin are English, so the steps below name them exactly as they appear on screen. The client-facing pages are available in Czech and English.

A forgotten password can be mailed to you from the Forgot your password? link on the sign-in page.

2. Set the notification address

Do this before anything else. Branding in the left-hand menu, the Mail section, the Notification e-mail field.

That single address receives a mail about every new comment and every approval, and client replies to those mails go there too. With the field empty, no mail goes anywhere — the comment is saved, but nobody learns about it until they look in the administration. Until the address is set, the Dashboard shows a No notification e-mail is set notice at the top.

Check what is already in the field

A newly created agency has the owner's address in this field. That is often right, but if a shared team address should be watching the feedback, overwrite it here.

Two more fields nearby are worth a look:

Field	What it does
Default language (Identity section)	The language of the review page until a visitor picks another one.
Sender name (Mail section)	The name notifications are sent as. Empty means the agency name. Unlocked by the Studio plan.

Press Save at the bottom.

3. Create a project

Projects in the menu, then the New project button. You fill in four things:

Field	What goes in it
Client name	The client's or company's name. The client sees it in the header of the review page.
Slug	Letters, digits, hyphen and underscore only. It is generated in lowercase from the client name, but you can overwrite it.
Password	The project password you will send to the client. Required. The eye icon reveals it.
Archived	Leave it off. An archived project drops out of the default list and its review URL stops working.

The slug is also the address: the slug acme-web makes the review URL /review/acme-web. Pick it knowing the client will see it. You can rename it later — links that have already gone out forward to the new address.

Save with Create.

4. Add the first screen

Open the project from the list (the Edit action). Below the form there is a Screens table with a New screen button:

Field	What goes in it
Label	The screen's name, for example "Homepage" or "Contact". The client sees it in the list on the left.
Desktop image	The desktop design. PNG, JPEG or WebP, up to 10 MB. Required.
Mobile image	The mobile design of the same screen, if you have one. Optional; it can also be added later with Add mobile.

Saving creates the screen together with version v1. The next image of the same screen is not uploaded here but with the Upload new version action (the upward-arrow icon in the screen's row) — see step 9.

If the site already runs somewhere, you can capture screens from a URL instead of uploading them, with Add screens from URL next to New screen — see Screens from a URL.

Screens are reordered by dragging the handle in the table; the client sees them in the same order.

Look at it through the client's eyes

The Preview action, on the project and on each screen (there it is the eye icon), opens the review page in a new tab. As a signed-in member you get in without the password, so you do not have to send yourself anything.

5. Copy the review URL

Back in the Projects list, every row has a Review URL column. Clicking it copies the address to your clipboard (with a URL copied confirmation). It looks like this:

https://your-agency.example.com/review/acme-web

6. Send the client the link and the password

The client needs two things: the link and the project password. Nothing else — they create no account.

You can look the password up at any time: in the project (Edit) the Password field is read-only and the eye icon reveals it.

Two channels when the design is sensitive

Send the link by e-mail and the password another way, by message or on the phone. Anyone holding both sees every design in the project and every comment with its author's name.

A new password is set with the Change password action at the top of the project page. It signs out every client currently inside, and they will have to enter it again; their comments stay theirs.

7. What the client then does

The client opens the link and enters the project password. Then they type their name — that is the whole sign-in, and the name appears on everything they write. Then they click anywhere on the design, write their note and send it; the thread shows up on the image as a numbered marker that can be replied to. The client can change the name later with the Change name link in the review page header.

All of that has a page of its own you can send along with the link: Guide for clients.

8. Where the feedback shows up

In three places:

Where	What you see
E-mail	The address from step 2 receives a message in the agency's language with the author's name, the project, the screen, the version, the comment text and links straight to the project in the administration and to the screen as the client sees it. Your own replies from the preview of the review page produce no mail.
Dashboard	The administration's front page: at the top, notices when something needs attention (no notification address, the plan ending or ended) and a line with the plan's usage; below them the Active projects, Unresolved comments and Screens counts and a Latest unresolved comments table with the ten newest unresolved threads on the latest version of each screen. Clicking a row opens the review page in a new tab, right on that comment's pin, where you can reply.
Comments	The list of threads across projects (replies are not rows of their own; a Replies column counts them): project, screen, version, author, text, replies, date, a Resolved toggle and an Open on screen action. Filters: unresolved only (default), Version — Latest only (default) or All versions — and project.

Comments are never written or edited in the administration — the client writes them on the review page. You can reply in the preview of the review page, where you appear under your account name.

9. Close the loop

Two steps that make this a working process rather than an archive:

1. Resolve the thread. In the Comments list, flip the Resolved toggle on the comment, or tick several rows and use the Mark resolved bulk action. A resolved thread stops counting towards open feedback and its marker on the image turns grey. Resolving it also resolves its carried copies on older versions.
2. Upload a new version. On the screen in the project, the Upload new version action: the new image (desktop, mobile or both) and a Carry over open comments checkbox, which is ticked. That creates v2, the client sees it as the current one, and v1 stays in the history to read.

Carrying over copies the open threads onto the new version and leaves the originals on the old version as a record of what was said. A thread and its copies share one resolved state, though — resolve it once, on any version, and it is resolved everywhere. Counts look only at the latest version, so a carried thread is counted once.

What next

• Projects and screens — archiving, replacing an image, deleting a version, ordering screens.
• Comments and approvals — filters, bulk actions and what an approved version means.
• Guide for clients — what the client sees and can do on the review page.
• Branding and settings — colour, logo, language, footer, MCP token.
• Team and roles — inviting a colleague, owner and member.
• E-mail notifications — what is sent and to whom.
• Troubleshooting — when mail does not arrive or the client cannot get in.
• Documentation home