Connections
Connections are relationship maps for your muses — an ever-growing web of how each character knows friends, family, rivals, castmates, and NPCs. Build and arrange maps in the MultiMuse dashboard (Studio). View and share them on the web or inside Discord as an Activity.
Support: https://discord.gg/nd6FUaBpaV
What is a connection cloud?
Each muse can have its own connections cloud: a graph with that muse at the center and links radiating outward. Each link can have:
-
A label — free text like older sister, scene partner, or nemesis
-
A kind — Friend, Family, Rival, Romantic, or Other (with optional custom name and color)
You can link:
-
Your muses and muses shared with you
-
Other players’ muses (by name search)
-
Name-only cards — characters who are not muses, just a label on a blank card
Until you publish a cloud, it stays private to you in the builder. Publishing adds a share link and a View connections button on that muse’s Discord card.
Open the dashboard
-
Go to multimuse.app/dashboard and sign in with Discord.
-
Open Connections in the dashboard nav, or click Connections cloud on a muse in the Muse Editor.
From the Connections page you can also use Publish all clouds to make every muse you own public at once.
Each muse’s publish settings (public toggle, custom slug, extended map) also live under Connections cloud in the Muse Editor.
Build a cloud
When you open a muse’s cloud, that muse sits in the center of a canvas. Use the builder to map everyone they know.
Canvas basics
-
Double-click empty space, click + Add connection, or use Add here on the canvas to add a link.
-
Drag muse cards to arrange the layout. Positions save automatically.
-
Double-click a connection line to edit its label and kind.
-
Double-click an owned muse (yours or shared with you) to open their cloud and keep building.
-
Dashed cards are name-only placeholders, not full muses.
Navigation buttons
Four buttons along the top of the canvas control side panels:
-
Hide or show the muses list (left)
-
Hide or show the details panel (right)
-
Toggle both panels at once
On smaller screens, panels collapse into overlays — the canvas buttons are all you need.
First-time walkthrough
The first time you open Connections, a short onboarding guides you through:
-
Center a muse — pick who the map is about
-
Add a link — connect someone to them
-
Publish your cloud — turn on the public viewer and Discord Activity button
You can dismiss this and return anytime; publishing can wait until you are ready.
Add a connection
The Add connection picker shows muses grouped by source:
| Section | What it shows |
|---|---|
| Your muses | Muses you own |
| Shared with you | Muses other players shared with your account |
| Public muses | Published muses from the community (when searching) |
| Suggested by tags | Muses that share tags with the center muse |
Search filters
Use the search bar at the top of the picker:
-
#tag— filter by a muse tag (your tags, or server tags your muses use). Type#and pick from suggestions, or type a tag and press Enter to lock it as a pill. -
@user— find muses owned by a specific player. Type@followed by their Discord user ID (Developer Mode → right-click user → Copy User ID). Press Enter to lock the user pill, then browse their public muses. -
Name — type a muse or player name to search without filters.
You can combine pills and free text. Tag and user suggestions are recommendations; your own and shared muses always appear in their sections below.
Name-only cards
For characters who are not muses, add a name-only card from the picker (enter a name when prompted). These show as dashed cards on the canvas. You can edit the name and relationship label like any other link.
Labels, kinds, and custom types
Select a connection in the details panel to edit it.
Label
The label is the relationship text shown on the line — e.g. childhood friend, captain, unknown. Labels are optional but help viewers understand the map.
You can use both a kind and a label. Example: kind Romantic with label rivals to lovers.
Kind
Choose from Friend, Family, Rival, Romantic, Other, or None.
When kind is Other, you can set:
-
A custom type name (e.g. Mentor, Concord member)
-
A custom color via the color picker
-
Save type — stores that name and color for reuse on future links
Saved custom types appear in the Connection types section of the details panel. Picking one applies its name and color to the current link. Deleting a saved type removes it from the quick-pick list only — it does not remove it from connections already using it.
Kind colors
The Connection types panel (below the connection editor) lets you set default colors for Friend, Family, Rival, Romantic, and Other across all your clouds.
Links between your own muses (mirror)
When both muses in a link are yours, enable Also add reverse connection on [their] cloud to create a mirrored link on the other muse’s map automatically.
-
Set a reverse label for how the other muse describes yours (optional — defaults to the same label).
-
Deleting a mirrored link on one cloud removes it on the other.
-
Editing reverse labels updates both sides.
Double-click the other muse’s card to confirm the reciprocal label appears on their cloud.
Links to someone else’s muses (reciprocal requests)
When the target muse belongs to another player, you cannot mirror automatically. Instead, request a reciprocal link so your muse also appears on their cloud.
-
Add the connection on your side with your label and kind.
-
Check Request reciprocal link on [their] cloud.
-
Choose scope:
-
This connection only — one approval for this muse pair. You can set Label on their cloud (how your muse should appear on their map).
-
All muses (standing trust) — one approval links every current and future connection between your Discord accounts. Best if you roleplay together often with many characters.
- Click Send reciprocal link request or Send standing trust request.
The other player receives a Discord DM and can also respond from Dashboard → Connections → Link settings (incoming requests).
Until they approve:
-
Your link shows on your map
-
It does not auto-appear on theirs
After approval, each side can have its own label for the relationship (two-way link).
Standing trust
Once standing trust is active between two accounts, new reciprocal links can connect automatically without per-pair approval. You still set labels on your side; they set labels on theirs.
Safety controls
-
Decline — rejects the request
-
Block — stops future requests from that account (they cannot spam you)
-
Revoke trust — in Link settings, remove standing trust or shared access you no longer want
Blocked users appear under Link settings where you can unblock them later.
Publish and share
Publishing makes a cloud viewable outside the private builder.
Per-muse settings
In the details panel Publish section (also under Connections cloud in the Muse Editor):
| Setting | What it does |
|---|---|
| Publish connections cloud | Turns on the public viewer URL and View connections on the Discord muse card |
| Allow extended map | Lets viewers see this muse’s connections when someone pivots here from another map (friends-of-friends) |
| Custom slug | Short URL path, e.g. multimuse.app/connections/s/lyra-connections |
| Preview extended map | Builder-only preview of how the extended map looks |
Copy the public URL from the publish panel to share anywhere.
NOTE
Only published muses can be pivoted into from someone else’s map. Private muses stay hidden in the viewer.
Publish all clouds
On the main Connections page, Publish all clouds publishes every muse you own in one step (with extended map enabled). You can unpublish individual clouds later.
Default privacy
New clouds follow your muse card’s privacy: if the muse card is private, the cloud starts private. Beta testers may have had clouds set private by default regardless — check each muse if unsure.
View a map (web viewer)
Open a published cloud via its share link or from Discord. Viewer controls (gear button, bottom-right):
| Option | What it does |
|---|---|
| Connection types | Hide specific kinds from the map |
| Shared connections | Draw links between muses on the map who also know each other |
| Extended map | Show connections from connected muses (when they allow it) |
| Map depth | How many hops from center (1 = direct links only). Saved in your browser. |
| Reduce motion | Disables pivot fades and hover animations |
Click a connected muse to pivot — jump to their cloud and keep exploring. Extended maps can grow large quickly; adjust depth if the graph feels overwhelming.
Scene connections
Scene connections use MultiMuse thread tracking to suggest links when you and another player’s muses appear in the same tracked RP thread.
Open Scene connections on the Connections page:
-
Enable Suggest scene connections from shared threads
-
Set a Custom kind label (default: Scene partner) — used for new scene links and updates existing scene-style connections
-
Optionally enable Auto-add to my clouds (no prompt) — automatically adds links without asking
When a match is found, you can Add or Dismiss each suggestion. Scene links only change your clouds unless the other player enables the same feature.
This is a easy way to keep maps growing as you roleplay — start with acquaintance and refine the relationship later in the builder.
Discord integration
Connections work in Discord even when you are not in the dashboard — though arranging, colors, and custom types are best done in Studio.
View connections (Activity)
When a muse’s cloud is published, its Discord profile card shows a View connections button. Clicking it launches the Connections Activity — an embedded map viewer inside Discord. You can pivot through links and use connection trailing the same as on the web.
WARNING
View connections uses two Discord card components. If your muse card is at the component limit (Layout View cards), the button may not appear. Unpublish connections, remove another component, or simplify the card to make room.
Activities must be launched from a server text or voice channel, not a thread.
Slash commands
| Command | Description |
|---|---|
/connections open | Open a muse’s connection cloud as a Discord Activity |
/connections add | Add a link from your muse to another muse |
/connections remove | Remove a link from your muse’s cloud |
/connections add options:
-
muse— your muse (the map owner) -
target— the muse to connect to -
label— relationship label on your cloud -
reciprocal— mirror on the target’s cloud when you own that muse -
request— ask the other owner for a reciprocal link when you do not own the target
Use reciprocal for your own characters; use request for someone else’s. You cannot use both on the same command.
TIP
If a slash command shows an “unknown integration” error right after a bot restart, run it again — it usually resolves on the second attempt.
What others can see
A published map shows:
-
The center muse and connection labels
-
Avatars for linked muses that are also public
-
Extended connections only through muses that opted in (Allow extended map)
Private muses and unpublished clouds stay hidden. Name-only cards show the name you entered.
The Discord Activity is primarily a viewer. Building and editing graphs is intended for the dashboard.
Quick reference
| I want to… | Do this |
|---|---|
| Map a muse’s relationships | Dashboard → Connections or Connections cloud on the muse |
| Link my two characters | Add connection → enable mirror reverse |
| Link a friend’s muse | Add connection → Request reciprocal link |
| Link many characters with one player | Request All muses (standing trust) |
| Share a map | Publish connections cloud + copy URL |
| Grow maps from RP | Enable Scene connections |
| View in Discord | View connections on the muse card or /connections open |
| Manage trust and blocks | Connections → Link settings |
Related
-
Tracker and archive — thread tracking (powers scene connections)