> For the complete documentation index, see [llms.txt](https://swu-forge.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://swu-forge.gitbook.io/docs/account/profiles.md). # Profiles Profiles let you run multiple isolated workspaces under a single SWU Forge account — similar to Chrome profiles. Each profile owns its own decks, trilogies, team memberships, battle log, and replays. Switching profiles changes what you see across the app without signing in and out. Use profiles when you want to keep different "selves" cleanly separated: a competitive build pile vs. a casual brewing pile, or a teaching profile you share with a friend. ## Default profile Every account starts with one profile — the **default profile** — automatically created with the name and avatar you signed up with. The default profile is permanent: you can rename it or change its avatar at any time, but it can't be deleted. All of your existing decks, trilogies, team memberships, and battle log entries live in the default profile. ## Creating a profile 1. Open **Settings** from the avatar menu in the upper right. 2. Scroll to the **Profiles** section. 3. Type a name in the "Add a profile" field (e.g. `Competitive`, `Brewing`). 4. Click **Create**. The new profile starts empty. Decks, trilogies, and team memberships you create from this point on are owned by whichever profile is currently active. You can have up to **5 profiles** per account. ## Switching the active profile There are two ways: * **Avatar menu (quick switch).** Click your avatar in the upper right. Each profile that isn't currently active shows as a button — click it to switch. * **Settings → Profiles.** Click **Switch to this profile** on any non-active profile card. The active profile syncs across devices. Switching on your phone changes the active profile on your laptop the next time it reloads. ## What's separated between profiles | Lives on the profile (isolated) | Lives on the account (shared) | | ------------------------------- | -------------------------------------------------------------------------------- | | Decks | Display name (account-level) and email | | Trilogies | Subscription tier and billing | | Team memberships | Display preferences (grid density, search mode, replay speed, card-art variants) | | Battle log + replays | Subscription email, promo code | | Profile name + avatar | Account role and feature flags | | Karabast username | | ## Karabast username per profile The Karabast username drives **auto-record** — when a Karabast game finishes, SWU Forge identifies "which player is you" and fingerprints the deck you played to find the matching deck in your inventory. With profiles, the Karabast username is **per profile**. This means: * You can wire different karabast.net accounts to different profiles (e.g., one karabast handle for competitive testing, another for casual play). * When you arm auto-record, the **active profile at that moment** is locked into the recording session. The session keeps recording onto that profile's decks even if you switch profiles later in the app. Re-arm auto-record after switching if you want new games to land on a different profile. * The fingerprint match only considers the active profile's decks plus team decks accessible to that profile. Two profiles with similar decks never bleed into each other's recordings. If your Karabast username field is empty on a profile, auto-record won't arm for that profile — you'll see a prompt to set it in Settings. ## Public deck links When you flip on **Public link** for a deck, the public page shows the **owning profile's** name and avatar — not your account name. This is so each profile can present a distinct persona (a competitive profile and a casual profile can look like different people). ## Team membership Team membership is per profile. If you join a team, only the profile that accepted the invite sees the team's shared folders and battle log. Switching to a different profile of yours will hide the team — that profile isn't a member. When you accept a team invite, the accept screen lets you pick which of your profiles should join (it defaults to your currently active profile). If you only have one profile, the picker is skipped. If you're invited by email and create a SWU Forge account just to accept, the invite is auto-attached to your default profile at signup. You can leave and re-invite yourself if you'd rather have a different profile hold the membership. ## Deleting a profile Open Settings → Profiles, find the profile, and click **Delete**. Rules: * The **default profile cannot be deleted**. * A profile that **owns a team** can't be deleted — you have to transfer ownership of that team first. * Otherwise, deleting a profile permanently removes its decks, trilogies, team memberships (as a non-owner), battle log, and replays. There's no undo. If the profile you're deleting is the currently active one, you'll automatically switch back to your default profile. ## Cross-profile reorganization In this release, profiles are **fully isolated** — there's no UI to move decks or trilogies between two of your profiles. If you want to "promote" a deck from one profile to another, the workaround today is to export the deck list and re-import it under the target profile. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://swu-forge.gitbook.io/docs/account/profiles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.