> For the complete documentation index, see [llms.txt](https://docs.sigrex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sigrex.io/social/friends.md).

# Friends

Managing Your Friends and Sharing Access

On the Friends page, users can manage their friend connections, which are essential for **sharing webhooks and assets** across accounts.

***

## 🔧 **What You Can Do Here**

* **Send** friend requests to other users
* **Accept** or **ignore** incoming requests
* **Delete** or **cancel** existing connections

Friendship is **required** to share webhooks and other connected resources between users.

***

## 🚫 **Rules & Limitations**

* If a **friend connection is deleted**, both users will **lose access** to any previously shared assets or webhooks.
* If a user **cancels a friend request**, the other user will **not be able to send another** request again unless the canceling user **removes them from the "Rejected Requests" list**.
* You can **block new friend requests** from your account settings—but by default, **this setting is enabled**.

***

## 🔐 **Privacy & Control**

* You’re always in control of your friend list.
* All connection actions are **mutual and respect user consent**.
* Friend connections are one-to-one and private—**only friends can share resources** with each other.


---

# 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.sigrex.io/social/friends.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.
