> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/connections/profiles.md).

# Profiles

Create separate CrossWatch views and optional logins for people or households.

Profiles group instances, sync pairs, watcher routes, and webhooks for one person or view.

{% tabs %}
{% tab title="End users" %}

### Create a profile

1. Open **Settings → Connections**.
2. Go to **Profiles**.
3. Select **Add profile** or **New profile**.
4. Complete **Name**, **Accounts**, **Pairs and routes**, **Sign-in**, and **Review**.
5. Select **Create profile**.

**Accounts** selects the instances belonging to the Profile.

**Pairs and routes** selects its sync pairs, watcher routes, and webhooks.

**Sign-in** is optional. Enter a username and password, or use **Generate a strong one**. If sign-in is off, the wizard requests administrator credentials and turns it on.

Edit an existing Profile with the same wizard and select **Save changes**. **Remove login** deletes only its login. **Delete profile** deletes the Profile.

### Why use profiles

Use Profiles without logins to keep separate views for yourself or a household.

A Profile can hold several instances of the same provider. For example, one person can use two Emby servers.

### View a profile

Administrators can select **View as** for every Profile.

Settings then shows only that Profile's connections, pairs, routes, webhooks, and schedule. It displays **Viewing as** with **Stop viewing as**.

Overview, UI settings, and Maintenance are hidden. New pairs, routes, and webhooks are assigned to that Profile automatically.

The only difference for a Profile with a login is that the person can sign in.
{% endtab %}

{% tab title="Power users" %}

### Configuration

Profiles are stored in the `user_profiles` configuration key.

Every Profile is available through **View as** to the administrator.

An instance shared by two Profiles is admin-only for reconnect and webhooks.
{% endtab %}
{% endtabs %}


---

# 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://wiki.crosswatch.app/crosswatch/settings/connections/profiles.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.
