Connecting Your Account
Sweet Tea works as a local tool without an account. Link Studio to a Sweet Tea web account when you want a consistent publishing identity, web Library access, connected-device continuity, or account-managed Agent Access.
This chapter covers the browser link, the identity and session checks that follow it, and what to inspect when the connection is not working.
Linking Your Account
The link process connects your local Studio installation to your Sweet Tea web identity through a browser-based handshake:
- Open Settings in Studio and find the account linking section.
- Click Link Account. Studio opens your browser to the Sweet Tea web login page.
- Sign in to your web account, or create one if you do not have one yet.
- The browser completes the relay handshake and sends the approved session back to Studio.
- Return to Studio and confirm that the expected account is shown as linked.
Tip: If the browser handshake does not complete automatically, the link page may show a code or status you can enter manually in Studio. This handles cases where browser-to-app communication is blocked by a firewall or privacy setting.
What to Verify After Linking
Check these items before relying on connected features:
- Identity — Studio shows the username or email for the account you intended to link.
- Session health — The account session is current rather than expired or disconnected.
- Sync status — If sync is enabled, its status indicator shows a healthy baseline.
- No stale identity — A previously linked account is fully cleared.
The account does not change whether local generation is available. Authentication still applies to work that needs an owner, including publishing, private account data, and connected-device operations.
Refreshing a Stale Session
If an account-backed feature is unavailable:
- Open Settings and check the linked identity and session status.
- Use the refresh or reconnect action if the session is expired.
- Confirm that the web account opens normally in the browser.
- If Studio still shows the wrong identity or stale state, unlink and link the account again.
Troubleshooting Account Links
| Symptom | Likely cause | What to try |
|---|---|---|
| "Not linked" after a previous connection | Session expired or local link state was cleared | Link again from Settings |
| Connected feature reports an expired session | Account token is stale | Refresh the session or reconnect |
| Link handshake times out | Browser or network is blocking the relay | Try another browser and check firewall or proxy rules |
| Wrong account appears in Studio | Previous identity was not fully cleared | Unlink, then link with the intended account |
| Identity verification fails | Session-key rotation or network failure | Refresh; if it persists, reconnect the account |
Sync Readiness
Before relying on sync across devices, verify:
- the intended account is linked and current;
- the sync status indicator is not reporting an error;
- a small non-destructive test change reaches the expected account; and
- you understand which data is connected and which remains local.
Warning: Do not delete local Pipes, snippets, or presets as a way to reset a sync problem. Confirm the connected copy first. Studio-Web Continuity and Sync covers reconciliation in detail.