WeSyn
WESYN BASIC · BUYER GUIDE & HELP

Set up, protect, and support your own workspace.

A practical public English reference aligned with the current U.S. English WeSyn Basic delivery candidate.

Access and delivery. Immediately after payment, download the WeSyn Basic 28-1 ZIP and installation guide from Gumroad. WeSyn sends a secure link to your order email to collect the official license certificate PDF with your signed activation key by 18:00 KST on the second Korean business day after payment. The payment date, Korean weekends and public holidays do not count. This guide is informational only: it explains the buyer setup path and does not collect or display account, billing, configuration, credential, or license values.

Buyer-owned cloud

Your team controls its Firebase project, Google account, and usage charges.

Supported path

Use the buyer package and install/START_INSTALL_WINDOWS.cmd, which opens the Setup Assistant, rather than recreating a global CLI workflow.

Safe support

Share redacted symptoms only. Keep credentials, billing, and configuration values private.

01

Start here

Purpose. Prepare a clean, buyer-owned foundation before you begin. Keep the original buyer package unchanged and work from an extracted copy.

Before you begin

You need a Google account you control, a dedicated Firebase project for this workspace, an active Blaze plan with Google Cloud Billing, and a reliable internet connection.

Expected result

You have an untouched original package, an extracted working copy, and the accounts required for deployment.

  1. Keep the original buyer package in a safe place, then extract a working copy to a normal folder.
  2. Use a dedicated Firebase project for this workspace. Do not reuse a project that belongs to another product or team.
  3. Confirm that your team controls its Google account, Firebase project, and Google Cloud Billing account.
  4. Review the Setup Guide before making changes in Firebase.

Common errors

Do not start from inside a compressed archive. Do not begin with a personal or shared project that your team cannot administer.

Security note

A WeSyn Basic license is a one-time software license. Firebase and Google Cloud usage charges are managed directly by your team and remain separate from WeSyn.

Next step. Continue with the Firebase, OWNER, and Invite reference flow.

Open Setup Guide →
02

Set up WeSyn

Purpose. Follow the approved deployment order without recreating a manual global CLI workflow.

Before you begin

Have your dedicated Firebase project and active Blaze/Billing ready. Storage is optional and is not part of the default path.

Expected result

Installation and web Setup are preparation only. OWNER project activation must return ACTIVATED or ALREADY_ACTIVATED before workspace access.

  1. Extract the buyer package to a normal folder and run install/START_INSTALL_WINDOWS.cmd.
  2. In the Setup Assistant, enter the dedicated Firebase Project ID and confirm the intended project before installation.
  3. Open your deployed https://<projectId>.web.app address, enter your own Firebase Web Config and complete initial web Setup.
  4. Complete the first OWNER account setup, or sign in with the existing OWNER account.
  5. Enter the license key and continue to the displayed Firebase project confirmation.
  6. Check the actual project ID shown, then confirm activation for that project as OWNER.
  7. Only ACTIVATED or ALREADY_ACTIVATED permits entry to the workspace; sign-in and key verification alone are not activation.

Common errors

If a browser prompt shows the wrong Google account or project, stop and correct the account before approving it. Do not paste configuration values into support messages.

Security note

Do not run copied npm, gcloud, or global Firebase CLI commands from a capture. The buyer installer is the supported deployment path.

Next step. Use the existing Setup Guide for each Firebase action.

Review captured setup →
03

project activation

Purpose. Complete the installation and initial web Setup, then complete first-time OWNER account setup or sign in as the existing OWNER. Enter the license key, review the actual Firebase project ID shown and confirm activation for that project before members use the workspace.

Before you begin

Deployment and sign-in do not activate the license. Complete project confirmation as OWNER using the signed key. The practice below is from an earlier release.

Expected result

ACTIVATED or ALREADY_ACTIVATED confirms activation for the actual project; the current OFF service is not a successful activation.

  1. ACTIVATED or ALREADY_ACTIVATED allows workspace access. LICENSE_BOUND_ELSEWHERE requires seller transfer review; LICENSE_INVALID requires checking the entered key. For ACTIVATION_RETRYABLE or an unclear response, use activation status confirmation or retry in the same project. Do not change projects, obtain a replacement key or reset data to bypass activation.
  2. An authorized repeat download and reinstalling in the same Firebase project are recovery steps, not a new project transfer. If the first confirmation response is lost, use the supported same-project retry to recover the recorded result.
  3. Sign-in and a valid key alone do not confirm project activation. A platform access error is not proof that a duplicate project was blocked. If a request fails or its result is unclear, check the recorded activation status before retrying the same project; do not obtain another key, switch projects or reset workspace data to bypass the problem.
  4. Moving to a different Firebase project requires manual review. A backup restore does not authorize that move. Issuing a replacement proof cannot automatically revoke a permanent proof already held by the old project.

Common errors

An existing valid project proof can be verified locally during a central activation outage. New activation waits for service recovery; do not reset workspace data to resolve it.

Security note

For download or activation trouble, contact support@getwesyn.com with the version, failed step and a redacted error. Support routes order, refund and transfer decisions to sales, and technical activation issues to the app team. Do not send a full key, token, service-account file or certificate PDF.

Next step. Keep historic captures separate from the confirmed instructions.

Review setup references →
04

Google Drive backup

Purpose. Enable a buyer-managed backup path for the supported workspace data, then store backup files safely.

Before you begin

You need access to the Google Cloud project connected to your deployed workspace and permission to configure OAuth consent and credentials.

Expected result

Authorization completes for the intended user and a backup can be created without exposing secrets.

  1. Enable the Google Drive API in your Google Cloud project.
  2. Complete the OAuth branding information required by Google for your organization.
  3. For an External app in Testing, add only the necessary test users before testing authorization.
  4. Create a Web application OAuth Client ID and register the exact deployed WeSyn origin as an authorized JavaScript origin.
  5. Save the new Client ID in WeSyn settings, run a backup, and store the resulting file in a controlled location.

Common errors

For 401 invalid_client, confirm the client type and Client ID. For origin_mismatch, compare the exact deployed origin with the registered JavaScript origin. For 403 access_denied, review audience and test-user access.

Security note

Backups do not include passwords, authentication sessions, Firebase configuration, OAuth tokens, Slack Webhooks, or license signatures. Keep backup files private even when they contain only workspace data.

Next step. Understand which recovery path applies before you need it.

Read restore guidance →
04A

Choose the right recovery path

Use this quick comparison before restoring anything.

SituationSupported approachImportant boundary
Same Firebase projectReconnect to the existing buyer-managed project, then use the supported backup and restore flow.Firebase Authentication passwords remain with Firebase.
PC reformatReinstall from an extracted buyer-package copy and reconnect to the same Firebase project first.Review browser, OAuth, and local setup prerequisites again.
New Firebase projectRequest manual transfer review before deployment and reconfigure project-dependent resources.A backup does not authorize transfer; an old permanent proof cannot be automatically revoked.
05

Restore WeSyn

Purpose. Choose a recovery path that matches your Firebase project instead of treating a backup as a complete migration tool.

Before you begin

Identify whether you are keeping the same Firebase project, rebuilding a computer, or moving to a new Firebase project.

Expected result

The workspace data is restored in the intended environment and project-specific settings are reviewed separately.

  1. For the same Firebase project, use the backup and restore process with the existing project under your team’s control.
  2. After a PC reformat, reinstall from the buyer package and reconnect to the same Firebase project before restoring workspace data.
  3. For a different Firebase project, request manual transfer review before a new deployment; a backup restore does not approve the transfer.
  4. After any restore, review members, permissions, integrations, and the workspace data before returning the team to normal work.

Common errors

Do not assume a backup can move every Firebase resource to another project. A wrong project connection can make the workspace appear empty or incomplete.

Security note

Firebase Authentication passwords remain managed by Firebase and are not in a WeSyn backup. Google OAuth Client IDs and other project-dependent resources may require reconfiguration.

Next step. Use the focused checks if a restore does not look right.

Open troubleshooting →
06

Slack integration

Purpose. Optionally relay task notifications to Slack without turning Slack into a task-control surface.

Before you begin

Decide which team channel should receive notifications and use a webhook that your organization controls.

Expected result

Task alerts can reach Slack as a one-way notification relay.

  1. Configure the integration only from the verified WeSyn settings flow.
  2. Confirm that a test task event reaches the intended Slack channel.
  3. Keep notification scope limited to the people who should receive it.
  4. When disconnecting or changing a channel, reconfigure the webhook through the verified settings flow.

Common errors

If alerts do not arrive, check the selected workspace settings and your Slack channel configuration before creating a new webhook.

Security note

The webhook is protected in Secret Manager, is not included in WeSyn backups, and must be reconfigured when needed. Slack messages cannot create, change, or complete WeSyn tasks.

Next step. Continue to OWNER responsibilities and invitations.

Manage members →
07

Invite and manage members

Purpose. Give the OWNER a clear responsibility for access, roles, and the available team capacity.

Before you begin

Complete OWNER setup/sign-in and confirmed project activation first. Invite people only after the deployed workspace and Email/Password sign-in are ready.

Expected result

The right person can join with the appropriate role while the OWNER retains responsibility for team access.

  1. Use the workspace invitation flow to create an invitation link for the intended person.
  2. Choose the role that matches the person’s responsibility before sharing the invitation.
  3. Have the invited member open the link and complete Email/Password sign-in in the deployed workspace.
  4. If the team capacity is full, review your licensed capacity and existing member access before attempting another invitation.

Common errors

If sign-in or an invitation fails, verify the deployed URL, invitation status, and role settings. Do not share passwords, access tokens, or private invitation details in support requests.

Security note

Only the OWNER should manage access and roles. Use supported workspace controls instead of sharing an OWNER account.

Next step. See the everyday work sequence and supported references.

Use workspace features →
08

Use workspace features

Purpose. Keep the team’s work connected from project planning through a human-written completion review.

Before you begin

Start with a shared project context and agree who owns the task, conversation, and review.

Expected result

Projects, tasks, references, and completion reviews remain connected in the workspace.

  1. Create or select a project, then add the work as a task with its required context.
  2. Use task conversation and references to keep decisions, Figma links, and Drive links close to the work.
  3. Use Notes, KPI, calendar, and XLSX export only for their verified workspace purposes.
  4. When work is complete, record a human-written completion review so later related work can learn from it.
  5. Use Insights as a read-only view of completion reviews; it does not provide AI recommendations, employee ranking, or surveillance.

Common errors

Figma and Google Drive references are links or embeds, not full in-app editors or two-way integrations. If a link fails, verify the external file’s own sharing permissions.

Security note

PWA installation depends on the device and browser. Use normal device-browser controls; do not enter credentials or configuration values into a guide or support form.

Next step. Resolve common deployment, access, and browser issues.

Open help checks →
09

Troubleshooting

Purpose. Resolve common setup and access problems with minimal, safe evidence.

Before you begin

Record the visible error message, the approximate time, your device/browser, and the exact step you were completing. Remove sensitive details before sharing anything.

Expected result

You can identify the correct next check without exposing secrets or changing unrelated services.

  1. If the installer appears paused, wait for its visible progress message and complete any browser approval requested by your own account.
  2. If the wrong Google or Firebase account appears, stop before approval and switch to the account that owns the intended project.
  3. If Blaze or Billing is not ready, confirm the Firebase project is linked to active Google Cloud Billing before restarting the supported flow.
  4. For OAuth errors, check the registered origin, client type, audience/test-user access, and the Client ID saved in settings.
  5. For an old screen or unexpected behavior after an update, hard refresh or clear the browser or installed-app cache, then reopen the deployed URL.
  6. For sign-in, invitation, or permissions issues, ask the OWNER to review the relevant workspace access rather than sharing credentials.

Common errors

Do not send passwords, Firebase configuration, OAuth credentials, Slack Webhooks, license signatures, browser tokens, or account screenshots containing private identifiers to support.

Security note

Useful support evidence is a redacted error message, time, browser/device, and the guide step. Keep all account, billing, project, and credential values private.

Next step. Return to the captured action sequence when you are ready.

Back to Setup Guide →