> 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/followers-and-following.md).
# Followers & Following
Tap **More** in the navigation bar, then tap **Sharing**.
## Following
**Following** lists the people you follow. Tap someone to view their profile (see [Viewing Profiles](/sharing-and-followers/viewing-profiles.md)), or tap **Unfollow** to stop following them.
## Followers
**Followers** lists the people who follow you. Tap **Remove** to take someone off your list, and they'll no longer see what you share with Followers.
## Pending Requests
When someone asks to follow you, their request appears under **Pending requests** on your **Followers** tab, and you'll get a notice in your [Inbox](/more/inbox.md). Tap **Grant** to let them follow you, or **Deny** to turn them down. Requests you've sent are listed here too, with **Revoke** to cancel them.
{% hint style="info" %}
**Removing a Follower doesn't undo other sharing.** If you've invited them to a specific Cert, or sent them a share link, that access continues until you remove it (see [Invite to View](/sharing-certs/invite-to-view.md) and [Share Links](/sharing-certs/share-links.md)).
{% endhint %}
---
# 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/followers-and-following.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.
