Buyer-owned cloud
Your team controls its Firebase project, Google account, and usage charges.

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.
Your team controls its Firebase project, Google account, and usage charges.
Use the buyer package and install/START_INSTALL_WINDOWS.cmd, which opens the Setup Assistant, rather than recreating a global CLI workflow.
Share redacted symptoms only. Keep credentials, billing, and configuration values private.
Purpose. Prepare a clean, buyer-owned foundation before you begin. Keep the original buyer package unchanged and work from an extracted copy.
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.
You have an untouched original package, an extracted working copy, and the accounts required for deployment.
Do not start from inside a compressed archive. Do not begin with a personal or shared project that your team cannot administer.
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 →Purpose. Follow the approved deployment order without recreating a manual global CLI workflow.
Have your dedicated Firebase project and active Blaze/Billing ready. Storage is optional and is not part of the default path.
Installation and web Setup are preparation only. OWNER project activation must return ACTIVATED or ALREADY_ACTIVATED before workspace access.
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.
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 →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.
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.
ACTIVATED or ALREADY_ACTIVATED confirms activation for the actual project; the current OFF service is not a successful activation.
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.
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 →Purpose. Enable a buyer-managed backup path for the supported workspace data, then store backup files safely.
You need access to the Google Cloud project connected to your deployed workspace and permission to configure OAuth consent and credentials.
Authorization completes for the intended user and a backup can be created without exposing secrets.
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.
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 →Use this quick comparison before restoring anything.
| Situation | Supported approach | Important boundary |
|---|---|---|
| Same Firebase project | Reconnect to the existing buyer-managed project, then use the supported backup and restore flow. | Firebase Authentication passwords remain with Firebase. |
| PC reformat | Reinstall from an extracted buyer-package copy and reconnect to the same Firebase project first. | Review browser, OAuth, and local setup prerequisites again. |
| New Firebase project | Request manual transfer review before deployment and reconfigure project-dependent resources. | A backup does not authorize transfer; an old permanent proof cannot be automatically revoked. |
Purpose. Choose a recovery path that matches your Firebase project instead of treating a backup as a complete migration tool.
Identify whether you are keeping the same Firebase project, rebuilding a computer, or moving to a new Firebase project.
The workspace data is restored in the intended environment and project-specific settings are reviewed separately.
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.
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 →Purpose. Optionally relay task notifications to Slack without turning Slack into a task-control surface.
Decide which team channel should receive notifications and use a webhook that your organization controls.
Task alerts can reach Slack as a one-way notification relay.
If alerts do not arrive, check the selected workspace settings and your Slack channel configuration before creating a new webhook.
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 →Purpose. Give the OWNER a clear responsibility for access, roles, and the available team capacity.
Complete OWNER setup/sign-in and confirmed project activation first. Invite people only after the deployed workspace and Email/Password sign-in are ready.
The right person can join with the appropriate role while the OWNER retains responsibility for team access.
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.
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 →Purpose. Keep the team’s work connected from project planning through a human-written completion review.
Start with a shared project context and agree who owns the task, conversation, and review.
Projects, tasks, references, and completion reviews remain connected in the workspace.
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.
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 →Purpose. Resolve common setup and access problems with minimal, safe evidence.
Record the visible error message, the approximate time, your device/browser, and the exact step you were completing. Remove sensitive details before sharing anything.
You can identify the correct next check without exposing secrets or changing unrelated services.
Do not send passwords, Firebase configuration, OAuth credentials, Slack Webhooks, license signatures, browser tokens, or account screenshots containing private identifiers to support.
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 →