SolidFish

Help centre

Get unstuck. Keep the handoff moving.

Practical guides for opening, creating and managing Solid Codes — with the privacy, access and expiry details that matter when something does not go to plan.

Help is not the FAQ

FAQ gives short answers to common questions. Help provides step-by-step task guidance, recovery journeys, and links into the relevant SolidFish action.

Still blocked?

Use Contact for product support, feedback, privacy requests, or abuse reports. Never include passwords or management keys.

Task guides

13 published guide(s)
Open a packageRecipient2 min

Open a Solid Code

Start at the landing page, complete any access check, and understand each availability state.

  1. Open the SolidFish landing page.
  2. Enter the complete Solid Code.
  3. Enter the recipient password if requested.
  4. Review the intro and one-time warning before continuing.
  5. View, follow, or download the available content.
Create a packageSender4 min

Create and share a package

Choose content, configure access, set expiry, and deliver the Solid Code.

  1. Choose files, a note, or links.
  2. Configure optional password, one-time access, or restricted viewing.
  3. Select expiry and optional recipient emails.
  4. Review the package and activate it.
  5. Share the Solid Code and store the management key separately.
Manage a packageSender2 min

Extend or delete a package

Use the Solid Code and management key for sender-only controls.

  1. Open Manage from the navigation.
  2. Enter the Solid Code.
  3. Enter the management key exactly as shown.
  4. Choose Extend expiry or Delete share.
  5. Review and confirm the sensitive action.
DeliverySender3 min

Resolve email delivery problems

Check the address list, delivery status, and manual-sharing fallback.

  1. Confirm each recipient email address.
  2. Check whether the activation result reports queued or failed delivery.
  3. Ask the recipient to check junk or quarantine folders.
  4. Share the Solid Code through another trusted channel when necessary.
  5. Never send the management key to recipients.
Access problemsSender and recipient3 min

Troubleshoot a password or lockout

Distinguish a recipient password from a management key and respond to temporary restrictions.

  1. Confirm which credential the screen requests.
  2. Check spelling, spacing, and capitalisation.
  3. Wait for a temporary lockout to end before retrying.
  4. Ask the sender to confirm the recipient password through a separate channel.
  5. Create a replacement package if the required management key is lost.
SafetyAnyone2 min

Report unsafe or abusive content

Send the minimum information needed for a safety review.

  1. Open Contact.
  2. Choose Unsafe or abusive content.
  3. Enter the Solid Code when available.
  4. Explain the safety concern without copying unnecessary private content.
  5. Submit the report and retain the confirmation reference.
Product principlesSender and recipient7 min

Why fleeting data deserves a better handoff

Not every exchange needs an account, a permanent folder, a long-lived link, or another copy kept forever.

Long-form help essay

Security basicsSender and recipient6 min

Passwords and management keys

Recipient access and sender authority solve different problems.

Long-form help essay

Recipient experienceSender and recipient5 min

Using one-time access carefully

One-time access is useful when the sender understands claim behaviour and communicates it clearly.

Long-form help essay

File handlingSender and recipient6 min

Original files and safe previews

A preview is useful, but it should never be confused with the original upload.

Long-form help essay

Practical guideSender and recipient4 min

Choosing an expiry

Match the package lifetime to the real handoff, not to a default that nobody revisits.

Long-form help essay

Design notesSender and recipient6 min

Why advanced controls come later

Progressive disclosure keeps the first decision focused on the content being shared.

Long-form help essay

DeliverySender and recipient4 min

Delivering to several recipients

Multiple recipient emails can simplify distribution without exposing sender controls.

Long-form help essay