How to use PRIFLOW - Primordial Oneness
A quick reference for reviewing artwork, managing proofs, and running your team's workspace.
The basics
A proof is a package of artwork or PDFs you want feedback on. Anyone in your
organisation can create one, upload files to it, and share a review link so people can
leave feedback — no account needed for the reviewer beyond being signed in to your org.
An amend is a single piece of feedback: click anywhere on the artwork to drop a numbered
pin and describe what needs to change. Amends have their own reply thread, and the creator
marks each one resolved once it's addressed.
Signing in
Accounts are invite-only — an admin adds you, or invites you by email from Team
(/users). If you don't have an account yet, ask your admin for an invite.
Forgot your password? Use "Forgot your password?" on the sign-in page — it emails you a
reset link.
Your dashboard
After signing in you land on /dashboard, split into three sections:
- My proofs — proofs you created.
- Admin of — proofs someone tagged you as an admin on (see below).
- Reviewing — proofs you've left feedback on, or been tagged in to review, even before you've added anything yet.
Each row shows status, file count, version count, amend counts, and reviewer count, with quick
links to open or copy the review link. Admins get an extra "Everyone" toggle to see every
proof in the organisation, not just their own.
Creating a proof
From "+ New", give it a title and an optional description, then upload images or PDFs
(drag-and-drop or browse — up to the size limit shown on the page). You land on the manage
view, which only you (and anyone you tag as admin) can reach.
Two links matter here:
- Review link — share this freely. Anyone signed in to your organisation can open it and leave feedback.
- Manage link — keep this private. It's how you (and admins) get back into the proof to manage it.
Reviewing artwork
Open a review link, click anywhere on the image or PDF page to drop a pin, and describe the
change needed. You can reply on any existing amend's thread too. Filter the amends list by
All / Open / Done.
Who can review: any signed-in member of your organisation can review *any* proof via its
link — you don't need to be tagged or invited first. Tagging someone (see below) is just a
courtesy notification, not a requirement.
Versions
If a file needs revising, the creator uploads a new version of it from the toolbar
("+ New version") rather than starting a new proof. Versions of the same file share one
tab, with a dropdown to switch between them — the viewer defaults to the latest, and older
versions show a banner reminding you they're historical.
Closing a file
Once every amend on a file is resolved, its creator (or an admin) can Close file from the
side panel. This:
- Blocks new amends being added to *that file* until it's reopened.
- Only affects that one file — other files in the same proof are untouched.
- Reopens automatically if a new version of that file is uploaded, or can be reopened manually.
A proof's overall status shows Closed once *every* file in it is closed. It only upgrades
to Approved when every file has also been through a final approval (see below).
Final approval
Closing a file says "the amends are dealt with" — final approval adds a formal sign-off on
top of that. Once a file is closed, the creator (or an admin) can pick an organisation member
in the side panel and Send for final approval:
- The approver gets an email, opens the proof signed in, and chooses Approve or Amends needed, with optional notes either way.
- Amends needed reopens the file (the notes show in the side panel) so the normal resolve → close → re-request cycle can run again.
- The request is pinned to the version it was made against — uploading a new version, or reopening the file, cancels a pending request automatically. The creator can also Withdraw request at any time.
- File tabs show ⏳ while a sign-off is pending and ★ once it's approved; the proof's pill reads Awaiting approval when every file is closed but a decision is still due.
- If a request sits unanswered for a few days, the approver gets one reminder email.
Every request, withdrawal and decision is recorded in the proof's activity log.
Proof admins vs. tagging someone to review
These are two different things, both managed from the People tab on a proof:
- Proof admins — give someone the same management rights you have on that one proof: replying, resolving amends, uploading versions, closing files, tagging others. Only organisation members can be made admins.
- Organisation admins manage everything automatically — no tagging needed. Opening any proof's review link takes an org admin (or the proof's creator, or its proof admins) straight to the manage view, with their own name on the audit trail. Add
?as=reviewerto the link to see the plain reviewer view instead; and if a proof is waiting on *your* final approval, the link keeps you in the reviewer view until you've decided. - Tag someone in to review — sends them an email ("you've been tagged to review…") and puts the proof on their dashboard under Reviewing, even before they've added anything. It does not grant extra access — they could already review via the link regardless.
- External reviewers — invite an outside client by email to review just this proof. They accept the emailed invite (expires in 7 days), set a name and password, and get a guest account: they can add amends and replies on that one proof, but see no team names, no activity log, no approver identities or notes, and no other proofs. Revoke cuts their access instantly (their amends stay, attributed); Restore brings it back. The review link alone never grants an outsider access — only an accepted invite does.
Your account
From /account (click your name in the top bar) you can change your display name and
password at any time.
Team & admin
Admins manage the organisation from Team (/users): invite people by email, add them
directly, promote/demote, disable, reset a password, or remove someone. The **organisation
name** can be renamed from the same page.
Something not covered here, or not working the way you'd expect? Ask whoever manages your
workspace, or check the Changelog for what's recently changed.