> 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-and-followers/viewing-profiles.md).
# Viewing Profiles
## Tap a Name
Tap **More** in the navigation bar, then **Sharing**, and tap anyone you follow (or tap any Member on an Org's profile) to open their profile. You'll see their photo and name, how many Followers and Following they have, their Orgs, and whatever their Sharing Preferences let you see, like their contact information and their **Certifications**.
## View Their Certs
Under **Certifications**, tap any Cert to view it, including its document and renewal progress. You can look, but only its owner can make changes. If you don't see any, they haven't shared their Certs with you, and you'll see **No certs shared with you.**
## Block Someone
If you'd rather someone couldn't see your profile at all, tap **Block** on their profile and confirm with **Block**. To undo it, tap **Unblock** on their profile, or find them under **Blocked Users** in [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-and-followers/viewing-profiles.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.
