How to Use LinkInBio Day to Day

Use this operating loop after setup.

Daily loop

1. Open /dashboard and review the current workspace state.
2. Open /pages for the next product-specific task.
3. Open /editor/[pageId] for the next product-specific task.
4. Open /analytics/[pageId] for the next product-specific task.
5. Open /leads for the next product-specific task.
6. Use /help for approved guidance tied to the current route.
7. Use /help when the documented recovery steps do not solve the issue.

Verification

Confirm each change persists after refresh and remains inside the same organization or workspace. For money, publishing, deletion, or external communication, verify the final confirmation state before leaving the route.

Troubleshooting

See troubleshooting. Preserve the route, record identifier, time, and visible error when escalating. Never include passwords, API keys, full payment data, or private financial documents.

LinkInBio FAQ

Where is Learning content managed?

Cre84ever HQ is the management source. LinkInBio receives approved, published content filtered to product key linkinbio.

Does LinkInBio have a separate Learning Center?

No. The product surface uses the shared @cre84ever/learning contract and product configuration.

Why can I not see an article?

The article may be draft, assigned to another role, internal-only, scoped to another product, or unavailable for the current organization.

Does opening a setup page complete the checklist?

Not when a saved record or completion event exists. See initial setup for each completion source.

Can Ask AI use every document?

No. AI eligibility is a separate opt-in after human approval and publication. Draft and internal material is excluded by default.

How do I contact support?

Use /help. Include the route, time, expected result, actual result, and a redacted screenshot if useful.

LinkInBio Features and Routes

This reference lists the current product surfaces used for route-aware Learning suggestions. Route parameters in brackets must be replaced by a real record identifier.

Public routes

• /
• /[slug]
• /pricing
• /templates
• /help

Authenticated routes

• /dashboard
• /pages
• /editor/[pageId]
• /analytics/[pageId]
• /leads
• /settings

Help and support

• Product Learning route: /help
• Support escalation route: /help

Application surfaces

• apps/linkinbio

Related

• getting started
• initial setup
• features
• roles
• daily use
• faq
• troubleshooting
• known issues
• release notes

Getting Started with LinkInBio

LinkInBio is a page-building product for publishing links, collecting leads, and reviewing page analytics. This tutorial gets you to a first useful result without exposing another product's content.

What you'll need

• An authorized LinkInBio account.
• Access to the correct organization or workspace.
• A supported browser or the native app where listed.

Step 1: Open the product

Open / and sign in. After authentication, confirm that the organization or workspace shown belongs to you.

Step 2: Create an account

Open /signup and complete the requested fields. The Learning checklist uses the real completion signal linkinbio.account.created; opening the page alone does not complete the step.

Step 3: Create a page

Open /onboarding. Save or submit the underlying record so the result persists.

What you built

You now have an authenticated LinkInBio workspace and a persisted first-use state. Continue with initial setup, then use features as the route reference.

How to Set Up LinkInBio

Complete these steps in order. Setup progress must come from a saved record or product event when one exists, not from a page visit.

Prerequisites

• An authenticated account with the role required for each route.
• The correct organization, company, venue, workspace, or project selected.

Steps

1. Create an account. Open /signup. Completion source: record using linkinbio.account.created.
2. Create a page. Open /onboarding. Completion source: record using linkinbio.page.created.
3. Add and arrange links. Open /editor/[pageId]. Completion source: event using linkinbio.links.published.
4. Review domain and sharing settings. Open /settings. Completion source: record using linkinbio.sharing.configured.

Verification

Return to the product Learning page at /help. Confirm completed steps reflect saved product state. If a manual item is used, record who verified it and when.

Troubleshooting

If progress does not update, reload the authenticated workspace, confirm the saved record exists, and check troubleshooting. Do not mark the item complete only because its route opened.

LinkInBio Known Issues and Verification Notes

This file separates implemented behavior from claims that still require a human acceptance pass. It is not a promise that placeholder, provider-gated, or unverified behavior is complete.

Current verification boundaries

• Route and configuration claims are sourced from the current monorepo.
• Exact visual placement, device behavior, provider delivery, production credentials, live payments, and role-by-role click-through remain manual where the app's release evidence says so.
• Product Learning UI installation must be verified in the running app; documentation availability alone does not prove the persistent Help control is rendered.
• Product content remains draft and AI-ineligible until an authorized reviewer approves it.

Product-specific cautions

• Canonical Learning key: linkinbio.
• Help route: /help.
• Support route: /help.
• Do not expose internal content, unrelated product content, or cross-organization records.
• Preserve existing help and onboarding behavior until its replacement is mapped and tested.

LinkInBio Learning Release Notes

2026-08-06

• The Help center now shows published guides alongside the written sections. Nothing appears until a guide is approved and published in HQ.

2026-08-04

• Added native identity QR, event lead capture, NFC handoff, Wallet identity pass, contacts, widget, App Intent, and share-extension foundations.
• Added authenticated offline identity and lead hydration/replay plus browser-safe fallbacks for native actions.
• NFC hardware behavior, Wallet signing, push delivery, and App Store signing remain external acceptance gates.

2026-08-02

• Converted LinkInBio styling to explicit cascade layers so marketing, editor, application, and public-page rules resolve in a controlled order.
• Preserved the existing customer routes and workflows; this was visual-system maintenance rather than a new customer task.
• Updated CSS coverage and layer-order tests. No Learning role, setup, route, publication, or AI-eligibility change was required.
• Added the standardized product documentation set.
• Registered canonical Learning key linkinbio.
• Recorded public and authenticated route groups for contextual matching.
• Added role-aware visibility guidance.
• Added event/record-aware setup definitions.
• Kept every proposed content version in draft with AI eligibility disabled.

Publishing policy

Future entries must identify the product version or change, affected roles and routes, reviewer, publication state, and whether AI eligibility was separately approved.

LinkInBio Roles and Learning Visibility

Learning content is product-scoped first, then filtered by authentication, organization membership, role, audience, and publication state. A role name here is a documentation audience; authorization remains enforced by the product and database.

Roles

• page_owner: show only tasks and routes this role can perform.
• workspace_member: show only tasks and routes this role can perform.
• admin: show only tasks and routes this role can perform.
• public_visitor: show only tasks and routes this role can perform.

Visibility rules

• Public: may be shown without a session only when explicitly published for the public audience.
• Customer: requires authenticated product access and the correct organization context.
• Internal: restricted to authorized Cre84ever operators and never returned by customer search.
• Draft, in-review, or approved-but-unpublished content is not customer content.
• LinkInBio requests must include product key linkinbio; another product's content is rejected rather than blended.

How to Troubleshoot LinkInBio

Authentication or wrong workspace

1. Return to /.
2. Sign in again.
3. Confirm the organization, company, venue, project, or workspace is correct before changing data.

A save or action did not persist

1. Keep a copy of unsaved text.
2. Check the visible validation message.
3. Retry once on a stable connection.
4. Refresh and verify the underlying record exists.

Learning shows no results

1. Confirm the request uses product key linkinbio.
2. Clear route-specific filters and search again.
3. Confirm the article is published for your audience and role.
4. Use /help if approved content is still missing.

Escalation checklist

Provide the route, role, approximate time, organization context, steps taken, expected result, actual result, and a redacted screenshot. Do not send secrets or unredacted sensitive records.