Direct answer
No for the logo without written permission. The fix is one permission line captured on the delivery record at acceptance time.
The work is done, you are proud of it, and your portfolio is where the next client comes from, so the finished piece goes up with the client's logo beside it. That order, publish first and think later, is where the trouble starts. A client's logo is their brand mark, not a decoration your delivery entitles you to reuse, and never being given permission is not a grey area to lean on: it is simply a no that was never asked about. The name, the work itself, screenshots, and results numbers each sit at a different level of risk, and this page separates them. The lasting fix is not a braver reading of the rules. It is moving the ask to the one moment it is almost always granted: acceptance time, when the client has just approved the work and is happiest with it, captured in writing on the delivery record itself, with the scope stated. This page gives you the risk ladder, what counts as permission, the exact ask and clause, and what to do with work already published and with clients who say no.
Updated November 19, 2026. First published November 19, 2026. The records quoted below are real and public, read back from the live service on November 19, 2026.
Step 1. Climb the risk ladder in order: name, work, screenshots, logo, results
Not everything in a portfolio entry carries the same risk, and treating it as one question is the first mistake. A factual name mention, I provided design services to a company in the legal sector, or naming the client in a plain client list where your agreement allows it, sits lowest, though a confidentiality clause can bar even this. The work itself sits next: showing the piece you made is often covered by portfolio custom and sometimes by contract, but a contract can reserve it, and work made under a white label or agency arrangement usually cannot be shown as yours at all. Screenshots of their internal systems, dashboards, or documents sit higher, because they can carry their data and their customers' data. The logo sits near the top: it is a brand mark, using it implies an endorsement relationship, and no permission means no use is the only safe reading. Results numbers, revenue lifted, hours saved, sit at the top alongside the logo, because they publish the client's business facts, not yours. The ladder gives you the working rule: the further up you climb, the more explicit the written permission needs to be, and the logo never rides on implication.
Step 2. Check the agreement you already have before you ask anyone anything
Permission questions are often already answered in the paperwork, in both directions. Read the agreement, the terms you issued, and any document the client issued that you signed, looking for four shapes: a portfolio or publicity clause granting you display rights, which settles it in your favour within its stated scope; a confidentiality clause covering the client's identity itself, which bars even the name until it lifts; a white label or work for hire arrangement, which commonly bars showing the work as yours; and silence, which is the commonest shape and means exactly what this page's question says, permission was never given, so the ladder in step 1 governs and the ask in step 4 is the route. Check purchase order terms and platform terms too if the job came through either, since small print there sometimes carries a publicity line. Whatever you find, work from the document and not from the relationship: a warm client and a barring clause is a bar, and a distant client and a granting clause is a grant.
Step 3. Know what counts as permission, and what only feels like it
Permission that protects you is written, scoped, and kept. Written: an email, a signed clause, or a recorded line on the delivery record, never a verbal yes recalled later by one side. Scoped: it says what may be shown, the logo, the name, the work, screenshots, results, where it may be shown, your portfolio site, your profiles, a printed deck, and for how long or until withdrawn. Kept: it lives with the job records, findable on the day a client, a new brand manager at the client, or a platform ever asks. What only feels like permission: they never objected to someone else's portfolio, they shared your launch post, they are a big company that surely does not mind, the work is already public on their own site. Each of those is a fact about the world and none of them is a grant to you. The standard is simple enough to state to a client without embarrassment: if it is not written down with its scope, I treat it as not given, which is the same standard that protects your own work when clients use it.
Step 4. Capture the permission on the delivery record at acceptance time
Acceptance is the moment the whole arrangement works best. The client has just checked the work and said yes, goodwill is at its highest point in the entire job, and the delivery record is open in front of both of you. One line added there, permission to show this work, your name, and your logo in my portfolio, agreed as part of the acceptance, turns a future awkward ask into a closing formality already settled. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the acceptance states that line attaches to:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record as the moment in its natural habitat: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. A permission captured beside that decision carries the date, the decider, and the job it belongs to, which is exactly what a scope question needs years later. The pending record, 5 steps checked and on hold, shows the state before the ask: nothing is accepted yet, so nothing is publishable yet either. Run deliveries this way and the portfolio question stops recurring job by job, because the answer for each piece sits on its own record, granted or not, in writing, before you ever build the portfolio entry.
Step 5. Use this ask for past work, and this clause for the next agreement
For work already done, the ask is one short message, sent once, with silence treated as a no: I am updating my portfolio and would like to include the work I did for you, showing the finished piece with your name and logo, on my portfolio site. Happy to show you the entry before it goes live, and equally happy to leave it out if you prefer. May I? The preview offer and the easy no are what make the yes cheap to give. For the next agreement, the clause shape: On acceptance of the delivery, the client grants the provider permission to display the delivered work, the client name, and the client logo in the provider portfolio, profiles, and proposals, unless the client withdraws the permission in writing or the agreement states otherwise. Screenshots of internal systems and any results figures are shown only with separate written agreement. If a client says no, or never answers, the alternatives keep the portfolio strong without the mark: describe the work by sector and problem with no name, show your process and your own mock material, or use a testimonial the client does approve. A no honoured gracefully is also a reference preserved.
Honest limits
This page is general information about portfolio permission, not legal advice: brand marks are protected as trademarks, the rules differ by place and by industry, regulated and confidential work carries stricter duties, and a signed agreement governs over the defaults described here. If you have already published a logo and are now unsure, the conservative move is to take it down while you ask, since asking with the entry live reads as pressure rather than permission seeking. A verifiable receipt proves the saved result was not changed since it was saved; it does not create a permission, which is why the permission itself is a written line from the client, kept on the record, and never inferred from the receipt or the relationship.
Step 6. Make the permission line a standard closing step, so the question never recurs
The pattern underneath this page is the same one underneath most end of job disputes: a small thing that is free to settle at closing becomes expensive to reconstruct later. Add the permission line to your acceptance step the way you add the final invoice: same moment, same record, every job. Your portfolio then grows only from granted material, each entry traceable to the line that allows it, and the audit a nervous future client might run on your claims passes in minutes. Clients read the habit itself as a signal, too. The provider who asks, in writing, at the professional moment, is the provider whose portfolio a prospect trusts, because every logo on it is there with its owner's knowledge. That trust is worth more than any single entry published on a hope.
Frequently asked questions
Can I show a client's logo and name in my portfolio if they never gave permission?
The logo, no: it is the client's brand mark, using it in your portfolio implies an endorsement relationship, and permission that was never given is a no, not a grey area. The name sits lower on the risk ladder: a plain factual mention is commonly lower risk, but a confidentiality clause in your agreement can bar even naming the client, so the agreement is checked first. The work itself and screenshots sit between the two, with internal screenshots higher because they can carry the client's data. The route out is not a braver reading of the rules: it is written, scoped permission, asked at acceptance time and kept with the job record, plus a graceful set of alternatives, sector description with no name, process material, an approved testimonial, for any client who declines or never answers.
Can I at least name the client in words without using the logo?
Usually the lowest risk item on the ladder, and still conditional. A factual statement of the engagement, the client's name in a plain list or a sentence describing work you provided, is a different act from displaying their mark, and it is the display that carries the endorsement implication. The conditions are in your paperwork: a confidentiality clause that covers the client's identity, an NDA, or a white label arrangement each bar the name as surely as they bar the logo, and none of them is lifted by the job going well. Read the agreement first; if it is silent on identity, a plain factual mention is the rung most providers use, and if you want the name beside the work and the logo in a portfolio entry, that fuller use is what the written permission ask is for.
What if my contract says nothing about portfolio use?
Silence means permission was never given, and the risk ladder governs: factual name mention at the low end, the work and screenshots in the middle subject to any confidentiality terms, the logo and results figures at the top requiring an explicit grant. Silence is also the easiest state to fix, because nothing has to be undone: send the short ask for work already done, offering a preview of the entry and an easy no, and add the permission clause to your standard agreement so every future job settles the question at acceptance. Do not read silence as consent because the client is friendly, large, or unlikely to notice: the day the question is asked is usually the day their brand team, not your friendly contact, is doing the asking.
My client said yes verbally. Is that enough?
Treat it as a yes worth confirming in writing, not as a permission you hold. A verbal grant has no scope either side can check later: it does not settle whether the logo was included, whether profiles and decks count as the portfolio, or whether results figures were agreed, and the person who said it may not be the person who owns the brand decision. The fix takes one line and costs no goodwill: reply in the thread, or record it on the delivery record at acceptance, thanks, confirming I can show the finished work with your name and logo on my portfolio site, and let their written reply, or their acceptance carrying that line, be the permission. If confirming it feels awkward, that feeling is the information: a grant that cannot survive being written down was never solid enough to publish on.
How does a job record help with portfolio permission?
It captures the permission at the moment it is most freely given and keeps it with the job it belongs to. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the acceptance shows its date and its decider, and the permission line agreed at that acceptance sits on the same record, scoped to that job, findable years later when a portfolio entry is ever questioned. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next delivery on one record, so the portfolio permission is settled in writing at acceptance instead of reconstructed from memory later: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- My client wants me to give up my portfolio rights. What should I do?
- My client wants me to transfer the copyright before they pay in full. Should I agree?
- My client is using my work without paying. What can I do?
- My client will only pay me after their own client pays them. Should I agree?
- A subcontractor I hired let me down and my client is waiting for the work. What do I do?
- Start with your problem: every problem in this directory, routed to its page