Scylla
Sign InDownload

Support

Desktop Team Activation

Activate Scylla Team on the desktop using your Scylla Account and assigned organization seat.

Scylla Team desktop activation is account-based.

A normal Team user does not need a shared organization license key. The desktop signs into the user's Scylla Account and verifies the Team entitlement associated with that account.

Before activation

Confirm all three conditions:

1. You are a member of the correct Scylla organization.
2. A Team seat is assigned to your member account.
3. Scylla is installed on the Windows machine you want to use.

If any of these are missing, desktop Team activation may not complete.

Activate

  1. Launch Scylla.
  2. Open the account/license area if Scylla is not already prompting you to sign in.
  3. Choose Sign in with Scylla.
  4. Your browser opens the Scylla Workbench sign-in flow.
  5. Sign in with the Scylla Account that belongs to the Team organization.
  6. Approve/complete the browser flow.
  7. Return to Scylla.
  8. Let the desktop refresh and verify the signed Team entitlement.
  9. Confirm the desktop now reports the expected Team state.

What activation does

Team activation establishes Scylla account/entitlement state on the desktop.

It can enable access to Team-level Scylla services associated with the organization, such as managed Policy and Team Memory where configured.

It does not:

  • sign you into OpenAI, Claude, Cursor, GitHub, or other Agent Providers;
  • grant an Agent unrestricted access to project folders;
  • bypass Scylla Policy;
  • expose organization credentials;
  • create a database/SSH/MCP Connection automatically.

Provider authentication remains separate

After Team activation, connect your Agent Providers normally.

A Team seat pays for/authorizes the Scylla Team product. It does not include AI inference or replace provider subscriptions.

Offline entitlement behavior

Scylla uses signed entitlement state so the desktop can verify licensing independently from raw browser state.

The exact refresh/grace behavior is product-managed.

If the desktop temporarily cannot reach Scylla Workbench, do not assume the organization account has been deleted. Check the current local entitlement message and retry account refresh when connectivity returns.

Installation tracking

The Team console can track desktop installations separately from seat assignment.

An organization administrator may be able to revoke an installation that should no longer remain active.

Revoking an installation is not the same as deleting the member or changing purchased seat quantity.

Moving to a new machine

On a new Windows machine:

  1. Install the current Scylla build.
  2. Sign into the same Scylla Account.
  3. Complete Team activation.
  4. Reconnect local Agent Providers as needed.
  5. Recreate or restore local project scope and local Keyring configuration as appropriate.

Do not assume local encrypted Keyring contents migrate automatically with the Team account.

Wrong account

If the browser is already signed into a different Scylla Account, the desktop may return with the wrong organization context.

Sign out of the incorrect account in the appropriate place, then repeat desktop sign-in with the account that actually has the Team membership/seat.

Common problems

Sign-in succeeds but Team is not active

Check Team membership and seat assignment.

Seat is assigned, but desktop still shows Community/Professional

Refresh account state or sign out/in. Confirm the desktop and Team console are using the same Scylla Account.

Activation worked, but Agent Provider is unavailable

Authenticate the provider separately.

Team Memory is still unavailable

Team Memory also requires its own organization/project service state. See Team Memory.

Old machine still appears under Installations

An authorized Team administrator can review/revoke installations from the Team console where supported.