> 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/media-clients/kodi/kodi-add-on/identify-viewers.md).

# Identify viewers

Configure viewers, playlists, profiles, and remembered answers.

### How viewer detection works

Kodi does not identify who pressed play. The add-on stops at the first match:

1. A viewer's smart playlist contains the show or film.
2. The active Kodi profile belongs to a viewer.
3. Kodi asks when playback stops. It remembers the answer for shows.

With one configured viewer, all playback belongs to them. Kodi never asks. With no match, playback is sent without a viewer. Only a route with no profile or username whitelist accepts it.

### Smart playlists

Give each person playlists for the shows or films they watch. Episodes match the show's playlist. Films match their own playlist.

Use fixed lists or rules on stable fields, such as genre, tag, or studio. Avoid playlists based on progress, play count, last played, or “Continue Watching”. Those lists can credit the next episode to the wrong person.

The add-on refreshes memberships every hour by default. It also refreshes after a library scan, clean, or viewer change. It never refreshes during playback.

If a playlist cannot be read, none of that viewer's playlists count. The add-on falls back to profile matching and the question.

### Kodi profiles

Credit playback to a viewer when the active Kodi profile belongs to them. This works only when household members use separate profiles.

{% hint style="info" %}
Kodi stores add-on settings per profile. Pair the add-on and configure viewers in every profile that should report playback.
{% endhint %}

### Who watched question

When no playlist or profile identifies someone, Kodi asks after playback stops. It never interrupts playback.

* Select each person who watched, then select **Done**.
* **Everyone** selects or clears every viewer.
* **Skip**, **Back**, or **Done** with nobody selected sends playback without a viewer.

The window closes after two minutes, or when playback resumes. For a show, the answer is remembered and used from the next episode's start. Films are never remembered.

Kodi does not ask with fewer than two viewers. It also skips the question when a film setting disables it, playback ends before three minutes, autoplay starts another item, another dialog is open, or Kodi is shutting down.

### Add and manage viewers

Open **Viewers** → **Configure viewers and playlists**. Add one viewer per person. Assign playlists, profiles, or neither.

If CrossWatch has user profiles assigned to routes for this Kodi, **Add viewer** lists them. Select people from that list when possible. The name is then linked to CrossWatch and follows later profile renames.

Otherwise select **Type a name**. The name must match the route's **Username whitelist**, or the user profile assigned to a route without a whitelist. CrossWatch ignores case, spaces, and punctuation when comparing names. Accents remain distinct.

#### Playlists and profiles

Select **Playlists** to choose Kodi smart playlists for TV shows and films. Other playlist types cannot be used. Shared playlists credit every viewer using them.

Select **Profiles** to choose existing Kodi profiles. A profile assigned to another viewer shows the other viewer's name.

#### Rename and remove

A manually entered viewer can be renamed. Update the route's username whitelist as well. Linked viewers must be renamed in CrossWatch.

Removing a viewer also removes them from remembered answers. A show remembered only for that viewer is asked again after its next episode.

#### Warnings

| You see                  | Meaning                               | What to do                                       |
| ------------------------ | ------------------------------------- | ------------------------------------------------ |
| No CrossWatch route      | No route accepts this name.           | Check the route, profile, or username whitelist. |
| Playlist marked missing  | The playlist was renamed or deleted.  | Remove it and select its replacement.            |
| Playlist marked unusable | It is not a TV-show or film playlist. | Remove it, or change its Kodi type.              |
| Profile marked missing   | Kodi no longer has that profile.      | Remove it from the viewer.                       |

Routes refresh within five minutes. Adding or renaming a viewer triggers an immediate check-in.

### Remembered answers

Open **Viewers** → **Remembered answers** to review answers stored for shows. Search by show title or viewer. Use **Viewer** to filter by a person or shows that will ask again.

* **Change** opens the viewer picker with the existing answer selected.
* **Forget** removes one answer after confirmation.
* **Forget all** removes every listed answer. With a filter, it removes only shown answers.

Playlists and profiles override remembered answers. A show marked **Covered by** matches a playlist. Fix the playlist when it credits the wrong person.

**Not in library** means the show was removed. **Not stable** means Kodi could not keep a stable scraper ID. Forget that answer so Kodi asks again.


---

# 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/media-clients/kodi/kodi-add-on/identify-viewers.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.
