Profiles
Profiles let you use multiple accounts or servers for one provider (media servers, trackers, others)
For most users
Use the default profile for each provider.
Set up a provider in Settings → Connections.
Choose the profile on each sync pair or Watcher route.
You do not need profile IDs or configuration files.
When to add a profile
Add a profile when one provider needs separate connections.
Common examples:
A Plex server at home and another remotely.
A Trakt account for you and another for a partner.
Jellyfin servers for separate libraries or households.
Set up profiles in the UI
1. Add the connection
Each profile stores its own connection details in Settings → Connections.

Select Profile to create another connection.
Set its credentials, server URL, user, and provider options.
2. Select profiles for sync pairs
Each side of a pair can use its own profile.

3. Select profiles for Watcher routes
Choose a profile for both the provider and the sink.

Pairs and Watcher routes can reference profiles directly.
Before deleting a profile, update each pair or route using it.
Otherwise runs can fail or use the wrong account or server.
This section covers profile IDs, config.json, and API fields.
Profile IDs
defaultis reserved.Extra profiles use
PROVIDER-P##.Examples:
PLEX-P01,TRAKT-P01,SIMKL-P02.
The Profile button always creates the next free ID.
If PLEX-P01 already exists, the next profile is PLEX-P02.
Config and API field names
Use these fields when you edit config.json or call the API.
Each provider can define extra profiles in an instances map.
Pairs use:
source_instancetarget_instance
Both default to default.
Watcher routes use provider_instance and sink_instance.
Each route is:
provider(profile) → sink(profile)
Related topics
Connect providers: Connections
Configure sync pairs: Configure Pairs
Configure real-time scrobbling: Watcher
Scope media-server libraries per profile: Library Whitelisting
Delegate dedicated provider profiles to users: Managed users
Last updated
Was this helpful?