> 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/main-dashboard/navigation/profile.md).

# Profile

View your CrossWatch activity and manage your account, security, and preferences.

The **Profile** page is your personal CrossWatch home and account-management area. Open it from the profile icon at the end of the navigation, or visit `/profile`.

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FBesNskHpiVfF4mwM54Rp%2Fimage.png?alt=media&amp;token=5a6c63ba-9551-4838-a289-fc56b5d0c40a" alt=""><figcaption></figcaption></figure>

## Overview

The Overview tab is the landing page for your CrossWatch profile. It combines account information with a compact view of your recent media activity. The content shown here is scoped to the signed in CrossWatch profile. Available cards can depend on your permissions and connected services.

### Profile summary

At the top of the page you can see your profile picture, display name, username, role and membership information.

CrossWatch also shows a few quick profile statistics:

* Days tracked
* Items watched
* Services connected

### Now Playing and Last Watched

When CrossWatch detects an active playback session, the Overview can show a **Now Playing** card.\
When nothing is currently playing, CrossWatch uses your latest available playback activity to show **Last Watched** instead.

Selecting the media item opens its details.

### Continue Watching

The **Continue Watching** card shows recent unfinished playback from your connected players.

Select **View all** to open the Progress tab.

### Recent Watchlist

The **Recent Watchlist** card shows the latest titles currently available in your synced watchlists.

Select **View all** to open the Watchlist tab.

### Recent Activity

The **Recent Activity** card gives a compact view of recent CrossWatch activity, such as sync, watcher, webhook, scheduler and playlist events.

### Watcher

The **Watcher** section manages real-time scrobbling routes and their runtime state.

### Playback

The **Playback** section shows and manages unfinished playback progress from connected providers.

### Quick Stats

The **Quick Stats** card summarizes recent profile activity.

Depending on your data, the Overview can also show widgets for recent history, ratings, scrobbles, progress and playlists.

### Related pages

* [Watchlist](/crosswatch/main-dashboard/navigation/profile/watchlist.md)
* [History](/crosswatch/main-dashboard/navigation/profile/history.md)
* [Playback](/crosswatch/main-dashboard/navigation/profile/playback.md)
* [Watcher](/crosswatch/settings/scrobbler/watcher.md)
* [Settings](/crosswatch/main-dashboard/navigation/profile/settings.md)


---

# 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/main-dashboard/navigation/profile.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.
