> For the complete documentation index, see [llms.txt](https://docs.firecal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.firecal.app/sharing-certs/opening-a-share-link.md).

# Opening a Share Link

What the people you share with will see.

When someone sends you a CertLocker share link, open it in any web browser. You don't need a CertLocker account.

## View the Certs

The page opens to **Shared certs**, showing who shared them with you (**Shared by**, followed by their name) and each Cert's details with a preview of its document. Tap **View attachment** to see a document full size, and if the owner allowed it, tap **Download** to save a copy.

What you see is always current: if the owner renews a Cert or replaces its document, you'll see the new version through the same link.

## If the Link Doesn't Work

If the owner has revoked the link, you'll see **This share link was revoked by its owner.**, and if it has passed its end date, **This share link has expired.** Ask the person who sent it for a new link.

## Want a Locker of Your Own?

At the bottom of the page, tap **Create a free CertLocker account** to start keeping your own Certs (see [Create an Account](/getting-started/create-an-account.md)).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.firecal.app/sharing-certs/opening-a-share-link.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
