> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/social-sharing.md).
# Social sharing
After filling in the registration form or through the exhibitor portal users can invite their network to the event and increase participation. Users can send a maximum of 5 invites at a time. To prevent spam, recipients can only receive an email every 48 hours.
It is possible to adjust this pop-up by completing the following steps:
1. From the admin panel --> Go to Settings → General settings → Social Sharing
2. Adjust how the Social sharing will be displayed for the user.
3. Save your changes to see the magic
Example social sharing
This share through setting can be turned off by completing the following steps:
1. From the admin panel → Go to Users → Registration form.
2. Click on the pencil icon at the registration form where you want to turn it off.
3. Click on Settings and de-activate the ”Share through Exhibitor portal” or/and “Share through pop-up after registration" settings.
\
---
# 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://knowledge-base.letsgetdigital.com/adding-users-and-ticketing/registration-forms/social-sharing.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.
