1. LandOffer
  2. Blog
  3. All articles
  4. Confidential Work in a Portfolio: Request Permission and Build a Shareable Case

Job search

Confidential Work in a Portfolio: Request Permission and Build a Shareable Case

A full unsent fictional permission request and an executed original independent demo show how to narrow a portfolio case without assuming disclosure rights.

9 min readLandOffer team

Identify which materials you are authorized to share, with whom and in what form before putting confidential work in a portfolio. Request approval for the specific case and version, then keep the presentation inside that scope. If permission is unavailable, use a separately built demonstration with new inputs rather than disguising restricted work.

This guide checks official public sources on October 21, 2026. Its permission request and employer decisions are entirely fictional and unsent. The independent demonstration is original AI-authored teaching material executed locally with newly declared synthetic data; no private employer files or implementation were accessed. LandOffer publishes this guide and offers job-search tools; browse recent roles to choose a skill worth demonstrating. This is general portfolio planning, not a determination of your contract, ownership or disclosure rights.

A portfolio maker keeps a restricted folder closed while selecting one specifically approved case summary

Separate permission to share from your contribution

You can have made a substantial contribution without being free to publish the resulting material. The U.S. Copyright Office's work-made-for-hire overview explains that certain work falls into that category and that the employer is its author. That general description does not decide the status of your particular project, employment arrangement or contract.

Confidentiality is another question. The USPTO's trade-secret overview describes information whose value relates to secrecy and reasonable efforts to maintain it. A portfolio review should not assume that material is shareable merely because it lacks a copyright notice, contains no customer names or was created partly by you.

Identify the applicable internal process and the person authorized to approve external use. A colleague's technical review can confirm that a diagram is accurate without authorizing its disclosure. A manager may need to involve a client, security reviewer or other rights holder. If the authority or scope is unclear, hold the material and ask through an approved channel rather than interpreting silence as consent.

The practical decision is about a specific artifact, not whether you are generally allowed to discuss your career. A screenshot, source file, architecture diagram, metric, customer quote and short narrative may each need a different decision. Do not treat approval for one as approval for the whole project folder.

Define what approval must cover: artifact, audience and version

Give the authorized reviewer a specific proposed use to evaluate. Name the exact draft, the materials it includes and the audience who would receive it. Distinguish a public website from a private interview presentation, an application attachment or an authorized live discussion. Include whether viewers could download the material and whether the case would identify the organization.

Ask which details must be excluded, whether a specified redacted version is acceptable and whether a future revision needs another review. If approval has a time limit or audience restriction, record it with the approved version. Do not quietly expand a two-person interview permission into a permanent public portfolio entry.

Academic portfolio guidance offers a useful, narrower reminder: Appalachian State's public-portfolio guidelines discuss permission for others' work and people referenced in public materials. Those are institutional student guidelines, not authorization to disclose an employer's work. Their password-protection recommendation should not be read as overriding a separate confidentiality obligation.

Keep the request itself safe. Do not email restricted attachments to a personal account simply to ask whether you may use them. Describe the proposed artifact through the organization's permitted review process. The fictional example below contains no real employer content and demonstrates the questions a bounded request can resolve.

Worked permission request: a narrow case survives while other materials stay out

Fictional candidate Kira wants to explain her coordination work on an internal queue-routing change at an invented company. No such employer request was sent. All materials, reviewers, dates and responses here are stipulated teaching inputs.

Her complete unsent request reads:

Subject: Review request for interview case summary v1

Hello designated portfolio reviewer,

I would like approval to use the proposed text-only case summary v1 in an interview with the two named interviewers recorded in our internal review request. I am requesting that limited use only, through November 15, 2026, rather than a public website or downloadable attachment.

The proposed summary describes my coordination, review and handoff responsibilities. It excludes source code, screenshots, architecture, customer details, internal identifiers, performance figures and the company's name. I would present only the exact reviewed text and would not distribute a copy.

Please confirm whether you have authority to approve this use or whether another reviewer is required. Please identify any wording to remove and whether a later revision, additional audience or different format would require further review. Until the required approval is recorded, I will keep the work out of my portfolio and use an independent demonstration instead.

Thank you, Kira

For this exercise only, assume the authorized process expressly approves the final text-only v1 for that limited interview audience and period. It does not approve any other artifact. That invented response produces the following completed decision matrix:

Proposed material Stipulated decision Kira's completed choice
Exact text-only v1, two named interviewers, within the approved period Approved for that presentation only Retain the exact reviewed wording; no copy distributed
Same text on a public portfolio website Outside the approved audience and format Hold; do not publish
Renamed dashboard screenshot with customer names covered Not included in approval Exclude; renaming and masking do not supply permission
Internal source file and raw support logs Not approved Exclude entirely
Revised narrative with a new performance figure Different version and detail Hold pending a separate review

The narrowed fictional case blurb is:

Coordinated review and handoff of an internal queue-routing change. I organized the issue record, collected reviewer feedback and documented unresolved questions for the implementation owner. The team retained responsibility for implementation and release. This account excludes the design, code, customers and operating results.

That blurb shows Kira's contribution without claiming ownership of the implementation or inventing business impact. Its shareability exists only inside the exercise's stipulated approval. It is not a ready-made declaration that similar wording about your employer is permissible.

When actual approval is pending or denied, keep the case out of the proposed sharing route. You can ask the authorized reviewer whether another scope is possible, or proceed with an independent sample. If a hiring deadline arrives before a decision, use the independent sample and keep the unanswered request pending.

Passwords and redaction solve different problems

A password controls an access route; it does not establish that the content may be disclosed to the people who receive it. Removing a company name can leave distinctive business rules, architecture, dates or customer patterns visible. A covered label can also leave other details outside the area you intended to conceal.

Do not treat a public URL as blanket reuse permission. An organization may have released a particular product page without releasing its internal implementation, unpublished metrics or source assets. Linking to an authorized public page and uploading your own copy of internal material are different actions. Confirm the proposed use instead of extending the existence of one public artifact to everything behind it.

For code portfolios, GitHub's visibility documentation explains that public repositories expose code and Actions history or logs, and that public forks remain public when the original becomes private. Do not rely on changing visibility later as a complete recall mechanism. This guide did not create or change a repository.

Review the exact version of the intended package: pages, downloads, attachments, file names, screenshots, metadata and linked destinations. If you cannot establish that a detail belongs in the authorized version, remove the artifact from the sharing plan until it is resolved. This is an editorial decision to hold disclosure, not a legal conclusion about what a contract permits.

Worked independent case: a new library demo with observable limits

An alternative can demonstrate the skill without reproducing the restricted system. This article created a small original library-allocation exercise from newly declared rules and synthetic book labels. It did not inspect, import or compare any employer/client code, data, screenshots or documents. That describes the exercise's actual process; it is not certification of legal ownership or a comparison against unknown proprietary implementations.

The new task is simple: accept a request for available copies of a known item, reject an invalid request and preserve a readable decision record. The initial local inventory contains two copies of book-sun and one of book-river. The declared policy permits positive integer quantities, rejects unknown items and refuses partial fulfillment when stock is insufficient.

The full completed case is:

Case component Original demonstration record
Problem A small fictional library needs understandable allocation decisions without negative stock
Personal contribution Defined the toy rules, wrote local Python dictionary logic and recorded each decision
New inputs Two invented item labels, three starting copies and four synthetic requests
Design choice Reject the entire request when remaining stock is insufficient; do not partially fulfill
Verification Execute four requests; check accepted/rejected counts, exact remaining inventory, nonnegative stock and unchanged input hash
Limit No real library, concurrent requests, persistent service, customer study or production deployment

The executed sequence accepted a request for one book-sun, rejected a second request for two because only one remained, rejected unknown book-moon, and rejected a zero-quantity book-river request. The final inventory was one book-sun and one book-river: one accepted request and three rejected requests.

The saved original Python fixture passed five local assertions. The original input-file SHA-256 hash remained unchanged, and the exercise used no external requests or packages. These checks demonstrate finite behavior of newly written teaching code. They do not establish real-system throughput, race-condition handling or that a hidden employer implementation is different.

A complete portfolio case summary would read:

Independent synthetic library-allocation demo. I defined a small inventory policy, implemented sequential request handling and recorded rejection reasons. Four requests produced one local allocation and three rejections; five assertions checked the result and preserved input data. This sample uses newly declared fictional inputs and does not represent a client system, deployed service or measured business improvement.

The trade-off is visible: refusing partial fulfillment makes each decision simple, but a real library might need reservation queues, partial allocations or concurrent updates. Those features were not built. Explain the next design question without claiming it already works.

A fresh library-allocation model uses new fictional inputs while an unrelated restricted archive remains closed

Keep the shareable case honest as it changes

Preserve a record of the approved version, audience, date and restrictions where applicable. Revisit the scope before adding another diagram, metric, screenshot or download. A small visual change can introduce material that was never reviewed. Keep your public presentation aligned with the exact approved package rather than relying on memory of a general conversation.

For an independent sample, describe what you actually made and tested. Identify synthetic data and limitations near the result. Do not retell a confidential implementation from memory and call it independent because its variable names changed. When uncertain about obligations or ownership, use the appropriate authorized internal or qualified legal review before disclosure.

A useful portfolio does not require showing everything you have touched. A bounded approved narrative can establish collaboration and reasoning; a clearly labeled new demo can show implementation choices. Neither needs invented customer results or a claim that an access control eliminates every sharing risk.

As you compare recent roles on LandOffer, choose the skill the role requires and the evidence your case can actually demonstrate. Use specifically permitted materials or build a new, accurately labeled example, then check the final version and sharing route before making it available.

Sources and Further Reading