Use the Lenso client area for one studio job

The client area keeps the client-facing parts of a product photo job together. The exact tabs and actions depend on the job's brief, billing mode, review state, invoice settings, and final-file release state.

• Brief
• Deliverables
• Timeline
• Invoices, when Lenso invoicing or per-photo payment applies
• Messages

The client area is not a permanent cross-project asset library, a contract system, or a self-service repeat-order store.

When a client has more than one active job with the same studio, the projects list can show those jobs after secure access is confirmed. Access to another studio remains separate.

1. The studio grants access to the client's email
2. Lenso sends a project-specific link
3. The client opens the link
4. Lenso validates the job, email, token, expiry, and access state
5. The current browser session keeps the authorized access
6. The studio can revoke or replace the link

The email link is an access credential. Do not post it publicly or forward it to another reviewer.

Most links expire according to the job's current access policy. The invitation email or client area should show the relevant expiry when available.

After the page loads, Lenso removes the access values from the address bar and keeps them for the current browser session.

On a shared device, use a private window when practical and close the window when finished. A client should not rely on closing one tab as a universal sign-out from every browser session.

A replacement link can invalidate an earlier active link. Use the newest message from the studio.

Self-service resend is available only for access the studio already granted. It must not create access to a draft or intentionally revoked job.

A client can see only the client-facing information and files available for the invited job.

• Review or complete the current brief
• Open references shared with the client
• View current proof sets
• Leave comments
• Request changes
• Approve a named proof or set
• View client-visible timeline activity
• Send a message to the studio
• View and pay an optional invoice
• Download released final files
• Download a current delivery ZIP or manifest when available

An action can be hidden when it does not apply to the current job. The client cannot see the studio's private workspace, internal notes, unrelated jobs, or another studio's records.

The Brief tab can show the current job-level information, products, SKUs, variants, shot rows, references, deadlines, and output requirements selected for client review.

• Complete requested fields
• Upload permitted references
• Submit the current brief
• Respond to a studio changes request
• Confirm the current requirements when asked

The working brief can change. Use the current version and recorded decision rather than an old email or screenshot.

The client agreement defines the legal effect of brief confirmation and changed scope.

• Read briefs, project requests, and shot-list intake

In project billing, the client reviews the current proof or set and records a decision for the named version.

1. Open each required proof
2. Check the product or SKU context
3. Leave an asset-specific comment when needed
4. Choose Request changes or Approve
5. When requesting changes, identify Revision or Reshoot when the current studio process uses that distinction
6. Submit the completed feedback

Request changes

Request changes means the current proof or set is not approved. Name what should change and which asset or version the request applies to.

Revision

Use Revision for a change that the studio can make through the current production or post-production process.

Reshoot

Use Reshoot when a new capture or replacement production step is required.

Approve

Approve records a decision for the current proof or set.

Approval does not automatically prove payment or release final files. The job's invoice and release settings remain separate.

The client agreement defines the legal effect of approval, silence, delivery, and acceptance.

A per-photo job uses a different decision path. The client selects individual photos, continues to payment, and unlocks purchased originals after the current payment is confirmed.

1. Review eligible photos
2. Select the photos to purchase
3. Use comments for asset-specific questions or feedback
4. Continue to payment
5. Pay the selection invoice
6. Return to the job after payment
7. Download purchased originals

Per-photo selection does not use the same project-level approval step as project billing.

Selected, awaiting-payment, purchased, and unselected photos are separate states.

An unpaid selection invoice can be canceled only within the current cancellation window and after Lenso confirms the latest payment state. Canceling returns eligible photos to selection.

After payment, contact the studio about a service refund or selection correction. Do not try to cancel the paid invoice as though it were still a draft.

Comment

A comment can be a question, observation, reference, or instruction. It is not automatically a requested change or approval.

Requested change

A requested change records that the current proof or set is not approved and names the expected change.

Approval

Approval records the client's decision for the current version.

Messages

Messages in Lenso stay with the current job. An email or conversation outside Lenso does not appear automatically.

Timeline

The client-visible timeline shows the product events marked for client access. It is not a complete internal audit log.

When a studio records approval on behalf of a client, the event should identify the studio actor. It is not the client's own click. The studio should retain separate evidence or authority.

A visible proof is not automatically a released original. Lenso applies the current job's review, release, and payment settings.

Not released

The studio has not released the final set.

Awaiting approval

The current release policy requires client approval before automatic release.

Awaiting payment

The current release policy requires a paid invoice before automatic release.

Awaiting studio release

The policy is manual, or the automatic condition is satisfied and the studio still needs to release the set.

Partially released

Some final sets are available and others remain blocked.

Released, payment required

The studio released the set, but the current full-payment download rule still blocks original files.

Released

The released files are available under the current download-size and access policy.

When originals are blocked, the client area can show a protected preview where the current job allows it.

When payment is handled outside Lenso, Lenso does not confirm whether the studio was paid. The studio controls the release under its current policy.

Not every job requires payment before download.

Delivery ZIP

A delivery ZIP packages the current released files using client-facing delivery names.

Delivery manifest

A delivery manifest can map each released file to product, SKU, view, status, and download information in CSV or XLSX form under the current product behavior.

Secure links

Manifest and file links remain access controlled. These secure links can expire or be revoked.

Source and delivery names

The original storage object name can remain different from the client-facing delivery filename. Lenso applies the delivery name at the current handoff without silently renaming the stored source object.

A studio can use Lenso without sending client invoices through the product.

• The Invoices tab shows client-visible invoices for the current job
• An open invoice can link to a Stripe-hosted payment page
• The client can refresh the local payment status after paying
• Paid, void, uncollectible, and refund states remain distinct

When the studio bills outside Lenso, the Invoices tab can be hidden for a normal project-billing job.

• Understand approvals, invoices, payments, and final-file release

• Open the link only on a device you trust
• Do not forward it to another reviewer
• Ask the studio to invite the correct email
• Use the newest replacement link
• Close private browsing when finished
• Ask the studio to revoke a link that reached the wrong person
• Do not paste the link into a public support ticket

• Read the Privacy Policy
• Read about current security controls and limits

The link is expired.

Use the supported resend path when it appears, or ask the studio for a new invitation. A new link can invalidate the older one.

The link was revoked.

Contact the studio. Self-service resend must not restore intentionally revoked access.

The link opens the wrong project or studio.

Stop and contact the studio. Do not continue when the project title, studio name, or client context is not the expected one.

I can see a project card but cannot open it.

Use the latest invitation for that specific job.

The Brief tab is incomplete or locked.

Check the current brief state and studio message. A brief can be locked after submission or can be waiting for a studio changes request.

I do not see proofs yet.

The studio may not have uploaded or shared the current set. Send a job message to the studio.

I cannot download the original files.

Read the visible delivery state. The files may be awaiting approval, payment, manual release, or final processing. Contact the studio when the state appears wrong.

I paid, but the invoice still looks open.

Use Refresh payment status once, then reload the job. If the status remains open, contact the studio with the invoice number and payment date. Do not send card details.

The invoice amount or line item is wrong.

Do not pay the invoice. Contact the studio, which owns the service description and amount.

A refund says pending.

Pending is not completed. The studio can review the current Stripe state. The bank decides when a completed refund appears.

Download all says a preview or archive is still processing.

Wait for the current processing state, refresh once, and try again. Contact the studio or Lenso support when the state does not advance.

I used a shared computer.

Close the browser session. Ask the studio to rotate the link when another person could have retained access.

• A permanent client account across every studio
• A universal cross-project asset library
• Client self-service repeat ordering
• A contract or e-signature system
• A marketplace
• A dispute mediator
• A guarantee that payment, approval, or delivery will succeed
• A guarantee that every message outside Lenso appears in the job