> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/account-and-settings/client-settings-reference.md).

# Client settings reference

Client settings control profile, brand, assets, sources, integrations, portal access, reports, alerts, and Serena monitoring.

## Profile

* **General** — Client identity, website, and core details.
* **Brand & voice** — Brand context and writing guidance used by supported content workflows.

## Content

* **Assets** — Client visual and reusable content assets.
* **Sources** — Material Serena and supported workflows can use as client context.

## Connections

* **Integrations** — Google and other supported service connections.
* **Client portal** — Recurring outside access for the client.

## Performance

* **Reports** — Scheduled report delivery for the client.

## Monitoring

* **Alerts** — Which detector signals create alerts and where they are delivered.
* **Monitoring capabilities** — Which capabilities feed Serena and the client’s weekly brief.

## Safety

Confirm the selected client before changing sources, integrations, portal access, or delivery settings. These controls affect what Serena can use and what outside recipients can see.


---

# 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://help.rankability.com/account-and-settings/client-settings-reference.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.