> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/setting-up-client-connect.md).

# Setting Up Client Connect

## What this section covers

Client Connect gives your clients restricted access to your AgileCase system so they can view their own case and client details. This section covers the configuration side: inviting clients, enabling the cases they should be able to see, and choosing which custom field groups are visible to them.

## How access is controlled

Client access is driven by your system labels. Only elements marked "Public" are visible to a client, so you keep full control over what is exposed. Enabling Client Connect on a case does not, by itself, reveal anything you have not marked as public.

For that reason it is worth reviewing your labels before inviting your first client.

## What your clients will see

For the client's side of Client Connect, including what they can view and upload, see [Client Connect](/user-documentation/client-connect.md) in the user documentation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.agilecase.com/administrator-documentation/setting-up-client-connect.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.