What Pinfolio is

Pinfolio is a tool where an agency shows website designs to a client and the client writes feedback straight onto the image. Instead of screenshots attached to an e-mail, the client gets one link. Instead of a list of notes someone transcribes from e-mails, calls and chat messages, you get threads pinned to the exact spot in the design they are about.

What it solves

The usual round without Pinfolio goes like this: you export the design, e-mail it, the client replies "the menu sits a bit high and I'm not sure about the blue button", you guess which one, they send a screenshot with a red arrow, and you lose track of what is done and what is not.

Pinfolio turns that into one place:

• The client sees the design in a browser and pins a comment to a specific point.
• Each comment shows who wrote it and where exactly it points — a pin with a marker, the numbered disc.
• You get an e-mail about every new comment from the client — if you have set a notification address — and the administration shows you how many are still open.
• When you rework the design you upload a new version. The old version stays with its whole history, so a comment never points at an image that no longer exists.
• When the client is happy with a screen, they approve it. An approval carries a name and a time.

Who it is for

Who	What they do in Pinfolio
Client	Opens the link, enters the project password and their name, browses the designs and comments on them. They have no account and create none.
Agency member	Creates projects, uploads screens and versions, reads feedback and marks it resolved.
Agency owner	Also manages the team and invitations, branding, domains, and sees which plan the agency is on.
Operator	Runs the Pinfolio installation: the server and its configuration, creates agencies and changes their plans. Signs in to the administration as the super admin.
Super admin	The operator's account in the administration — the same person, not another role. Manages every agency; works with an agency's projects on that agency's host. Not a member of your agency.

Two worlds that do not mix

Pinfolio has two halves and it helps to keep them apart.

The administration at /admin

This is where the agency works. Sign in with an e-mail and password, see the projects, upload screens, read the comment list, change settings. There is one administration for the whole agency — you do not set up an installation per client, you create a project.

The administration is English-only for now

Labels, buttons and hints in /admin are in English. The client-facing pages exist in Czech and English and the visitor can switch language on them.

The review page at /review/{slug}

This is where the client works. No sign-in, no registration: they enter the project password, type their name, and they are in. The name holds for that one project and appears on every comment and approval they leave in it. The client can change it later with the Change name link; earlier comments keep the name they were written under and stay theirs — Pinfolio recognises them by the browser, not by the typed name.

Two consequences worth telling a client up front:

• Anyone who has the link and the password gets into the project — and sees all comments and the names of their authors, not only their own.
• A password covers one project. Another project has another password, even for the same client.

More in security and privacy.

How the pieces fit together

agency (one administration, one plan, one set of branding)
└── project           link + password for one client, /review/{slug}
    └── screen        one page of the design, for example "Homepage"
        └── version   v1, v2, v3 … the image of one design round
            ├── thread     a comment pinned to a point in the image + replies
            └── approval   the client's sign-off on this version

Four things follow from that:

1. A screen is a name, a version is an image. The screen "Homepage" lives on even if its design is redrawn three times.
2. Only the latest version can be commented on. Older versions are read-only — they are a record, not a workspace.
3. A thread is one level deep. You reply to a comment, never to a reply.
4. An approval belongs to a version, not to a screen. A new version starts unapproved, because the client signed off an image that is no longer current.

What Pinfolio deliberately does not do

This is not a list of plans. It is what the tool does not do today, so it does not surprise you halfway through a project.

• Static images only. You upload PNG, JPEG and WebP. Pinfolio does not show live HTML prototypes, iframes or links to Figma. A page captured from a URL is an image too — a snapshot of one moment, not the live site.
• Clients have no accounts. There is no client sign-in that would show them all their projects in one place. A password always covers one project.
• There is no self-service signup. The operator creates your agency for you. There is no "Sign up" anywhere.
• Notifications by e-mail only. No Slack, no webhooks, no browser notifications. Mail about a new comment, an approval and a withdrawn approval goes to one address you set, in the agency's language.
• Billing is not built. Plans are changed by the operator, so a plan change is an e-mail rather than a button — see plans and limits.
• The export feature is only a promise so far. It is listed on the Agency plan, but nothing in the application reads it; there is no file to download from it.

Glossary

The whole site uses these terms in this one sense.

Term	What it means
agency	One workspace: its own users, projects, branding, plan and address. Agencies cannot see each other.
administration	The interface at /admin where the agency works.
Dashboard notice	The block at the top of the Dashboard (the administration's start page) that warns about an empty Notification e-mail or a plan that is ending or has ended, and shows how much of the plan's limits the agency uses.
review page	The client-facing page at /review/{slug} where designs are browsed and commented on.
project	One engagement for one client: client name, slug, password and a set of screens.
slug	The project's short identifier in the URL; it makes the review URL /review/{slug}. After a rename, old addresses redirect to the new one.
project password	The password that gets a client to the designs. One per project. Changed with the Change password action, which signs every client out.
screen	One page or view of the design, for example "Homepage" or "Contact". It has a label and a position.
version	One design round of one screen: v1, v2, … Each version has an image for each of its views and its own comments.
variant (view)	The desktop or mobile picture of the same version. Each view has its own comments; the version is approved as a whole.
URL capture	A picture of a whole web page that Pinfolio takes from its address and stores as a version of a screen — instead of an uploaded file. Each view captured counts against the plan's monthly limit. See Screens from a URL.
comment	Text someone wrote about the design. It either starts a thread or is a reply inside one.
thread	A comment pinned to a point in the image, plus its replies. It is resolved as a whole, together with its copies on other versions.
pin	The pinned point: the exact spot in the image a thread points at. Stored as percentages, so it holds at any display size.
marker	The numbered disc that draws a pin on the image. In the agency's brand colour (rust by default) while the thread is open, grey once it is resolved.
drawing	An optional freehand stroke or highlighted area that can be drawn with a comment.
carry over	Copying the open threads of the current version onto a newly uploaded version (the Carry over open comments option). The copies stay linked to the original thread, so they are resolved together.
resolved	The state of a thread nobody is waiting on any more. It belongs to the thread as a whole (replies have no state of their own) and to every copy of it carried onto later versions — resolving it on one version resolves it on all. Resolved threads drop out of the unresolved counts, which only look at the latest version of each screen.
approval	The client's confirmation that one version is fine. It carries a name and a time and can be withdrawn — a client's withdrawal is e-mailed to the agency.
plan	Free, Studio or Agency. It decides an agency's features and limits.
feature	One capability a plan unlocks — custom branding or a custom domain, for instance.
limit	A numeric ceiling of a plan: the number of users, of non-archived projects, the length of the portfolio archive window, and the number of URL captures a month.
owner	An agency user who manages the team, branding and domains.
member	An agency user who works on projects and comments.
super admin	The operator's account in the administration. Manages every agency; works with an agency's projects on that agency's host, and on a host that serves no agency sees only the list of agencies. It is not a member of any agency.
operator	Whoever runs the Pinfolio installation: the server, its configuration and the agencies' plans. In the administration they sign in as the super admin — the same person, not another role.
client	The person who browses designs through a link and comments on them. They have no account.
invitation	A link valid for seven days with which an owner invites a new member to the team.
subdomain	The address {slug}.{platform host}, which an agency has from the start and which needs no DNS work.
custom domain	An agency's own domain, which can be pointed at Pinfolio and verified.
portfolio	A user's public page at /@{username} with the approved work of the projects they picked themselves, in their order, each under an optional public title and address. Unapproved versions show only for an entry with Show unapproved work on. Set up on the Portfolio page, and switched off for the whole agency by Allow public portfolios on the Branding page.
agency portfolio	The whole agency's public portfolio on the homepage of its host: logo, name, intro, cards of the projects an owner picked and a Team section with the members' public portfolios; the projects live at /work/{slug}. The same rules apply as to a personal portfolio. Switched on and managed by an owner on the Agency portfolio page; Allow public portfolios does not affect it.
archive window	How long an archived project stays on a portfolio after it was archived. Its length depends on the plan; when it runs out the project leaves the portfolio, but nothing is deleted.
MCP token	The secret token with which an AI assistant gets read access to the agency's designs and feedback.

Where to next

• Quick start — from signing in to your client's first comment.
• Guide for clients — the page you can send to a client.
• Projects and screens — day-to-day work in the administration.
• Plans and limits — what each plan includes.
• Documentation home