Loading documentation...
Preparing Ring content
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Preparing Ring content
Preparing Ring content
Preparing Ring content
Desk URL pattern: /admin/crm/orders/[id]?tab=secrets (admin) · /my-orders/[id]?tab=secrets (buyer). Same panel component: OwnerSecretsPanel.
The Secrets tab is the buyer-facing form for clone credentials that are not brand overlay fields. Values load masked; secrets save encrypted; public values store plaintext. Changes apply on the next deploy.
Open your order → Secrets. Use the outline buttons for guided docs (Firebase, Ring Filebase, WalletConnect, configuration hub).
Paste values from your provider consoles. Required owner keys show as tab status errors until set.
Click Save. Ask your integrator to deploy when ready — the panel reports appliedOnNextDeploy.
| Service | Doc |
|---|---|
| Firebase Admin + client | Firebase backend |
| Object storage | Ring Filebase |
| Mobile wallets | WalletConnect Project ID |
| Full catalog | Supported services |
Integrator-only keys (database passwords, AUTH_SECRET, WayForPay merchant secret) appear on the integrator Env tab — not on buyer Secrets. If something is missing, ask your integrator to Request update from the room.
Desk URL pattern: /admin/crm/orders/[id]?tab=secrets (admin) · /my-orders/[id]?tab=secrets (buyer). Same panel component: OwnerSecretsPanel.
The Secrets tab is the buyer-facing form for clone credentials that are not brand overlay fields. Values load masked; secrets save encrypted; public values store plaintext. Changes apply on the next deploy.
Open your order → Secrets. Use the outline buttons for guided docs (Firebase, Ring Filebase, WalletConnect, configuration hub).
Paste values from your provider consoles. Required owner keys show as tab status errors until set.
Click Save. Ask your integrator to deploy when ready — the panel reports appliedOnNextDeploy.
| Service | Doc |
|---|---|
| Firebase Admin + client | Firebase backend |
| Object storage | Ring Filebase |
| Mobile wallets | WalletConnect Project ID |
| Full catalog | Supported services |
Integrator-only keys (database passwords, AUTH_SECRET, WayForPay merchant secret) appear on the integrator Env tab — not on buyer Secrets. If something is missing, ask your integrator to Request update from the room.
Desk URL pattern: /admin/crm/orders/[id]?tab=secrets (admin) · /my-orders/[id]?tab=secrets (buyer). Same panel component: OwnerSecretsPanel.
The Secrets tab is the buyer-facing form for clone credentials that are not brand overlay fields. Values load masked; secrets save encrypted; public values store plaintext. Changes apply on the next deploy.
Open your order → Secrets. Use the outline buttons for guided docs (Firebase, Ring Filebase, WalletConnect, configuration hub).
Paste values from your provider consoles. Required owner keys show as tab status errors until set.
Click Save. Ask your integrator to deploy when ready — the panel reports appliedOnNextDeploy.
| Service | Doc |
|---|---|
| Firebase Admin + client | Firebase backend |
| Object storage | Ring Filebase |
| Mobile wallets | WalletConnect Project ID |
| Full catalog | Supported services |
Integrator-only keys (database passwords, AUTH_SECRET, WayForPay merchant secret) appear on the integrator Env tab — not on buyer Secrets. If something is missing, ask your integrator to Request update from the room.
GET /api/my-orders/[id]/env → masked envConfig + owner-filtered groups
PATCH /api/my-orders/[id]/env → assertEnvPatchAllowed(role) → saveEnvConfig
GET /api/my-orders/[id]/env → masked envConfig + owner-filtered groups
PATCH /api/my-orders/[id]/env → assertEnvPatchAllowed(role) → saveEnvConfig
GET /api/my-orders/[id]/env → masked envConfig + owner-filtered groups
PATCH /api/my-orders/[id]/env → assertEnvPatchAllowed(role) → saveEnvConfig