> 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/the-admin-panel/users/user-tags/limit-networking-visibility-with-user-tags.md).
# Limit networking visibility with user tags
During certain events, high-profile attendees (e.g. CEOs) may need limited visibility to avoid unwanted contact from the general audience. Use user tags to restrict who can initiate networking with specific people, helping protect their privacy and reduce unsolicited outreach.
This person can only be directly networked with by users tagged VIP or CEO.
### How it works
Create a user tag and specify in the Advanced tab which tags are permitted to initiate contact. This lets organisers curate the experience for high-profile attendees.
Anyone without a permitted tag cannot initiate networking with a restricted user. However, if a restricted user reaches out first — by sending a message or scheduling an appointment — the recipient can respond. They cannot, however, schedule a follow-up appointment themselves.
If a restricted user accepts a networking request, the other person gains access to all networking options for as long as they remain connected.
Restricted users can network with anyone freely, unless the other person has their own networking limitations in place.
---
# 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/the-admin-panel/users/user-tags/limit-networking-visibility-with-user-tags.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.
