> 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/invite-to-view.md).
# Invite to View
Share one Cert with exactly the right people.
Want a particular person in CertLocker to see one of your Certs, without changing your Sharing Preferences for everything else? Invite them to it.
## Tap to Open & Share
When looking at your Locker, **Tap a Cert** to open it, tap the **Share Icon** in the top right corner, then tap **Invite to view**. (You can also open **Cert details** and tap **Invite to use this cert** under **Sharing**.)
## Find & Invite
The **Invite to use this cert** sheet opens with a search bar. Start typing a name, and when you see the right person, tap to select them. Select as many people as you need, then tap **Invite**.
They can see the Cert right away, with no invitation to accept, and it stays visible to them even if you mark the Cert private.
## Remove Someone
To take back access, open **Cert details**, find the person under **Sharing**, and tap **Remove**. This only removes that invitation: if they can also see the Cert as your Follower or through an Org, they'll keep that access (see [Sharing Preferences](/sharing-and-followers/sharing-preferences.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/invite-to-view.md?ask=&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.
