> For the complete documentation index, see [llms.txt](https://docs.tuplo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/social.md).

# Social

Enhance brand visibility and customer engagement.

<figure><img src="https://3633098189-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV0nc9z5ERStcxnY8SDZS%2Fuploads%2FPef30ffBZloogIEa8VqG%2Fdashboard-pref-social.webp?alt=media&amp;token=26ca6f65-40e6-48a6-92e8-b076be78d24d" alt=""><figcaption><p>Social preferences.</p></figcaption></figure>

## Link Accounts

By entering your social media URLs into these fields, you can link those accounts to the appropriate icons in your email correspondence.

To do this:

1. **Enter** the appropriate URL into the entries.
2. **Toggle** the associated switch to activate the link.
3. **Click** Update Social to apply the changes.

{% hint style="info" %}
**Quick Tips!**

While these settings only link your social accounts to your emails, connecting your social media pages to the icons on your website requires some manual code adjustments.&#x20;

If you can access your Tuplo website's code, you can find the location to enter your URLs in your Footer; otherwise, contact support for help connecting those icons.
{% 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.tuplo.com/tuplo-account-management-guide/your-tuplo-dashboard/preferences/social.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.
