How LynxProfile works.

Once you are set up, this is the shape of an ordinary day.

Where you spend your time

Start at Dashboard to see where things stand. Most days you move between Pages, Leads and Help.

When something is not covered here, use the help in the app, or ask support.

Check it worked

Refresh the page and check your change is still there, in the workspace you expect. Anything involving money, publishing, deleting, or a message going out to someone else: wait for the confirmation before you leave the page.

Troubleshooting

See troubleshooting. Note the screen you were on, the record, the time, and the exact error. Never include passwords, card numbers, or private financial documents.

Where is Learning content managed?

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

Does LynxProfile 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 page, time, expected result, actual result, and a redacted screenshot if useful.

Every screen this product provides. Where a screen opens one specific record, open it from its list rather than typing an address.

Public pages

• the home page
• /[slug]
• Pricing
• Templates
• Help

Authenticated pages

• Dashboard
• Pages
• the page editor
• page analytics
• Leads
• Settings
• /api/support/ask
• /api/support/thread

Help and support

Where this lives in the app

• apps/lynxprofile

Related

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

LynxProfile is a page-building product for publishing links, collecting leads, and reviewing page analytics. This guide gets you to a first useful result.

What you'll need

• A LynxProfile account.
• Access to the correct organization or workspace.
• A current browser, or the app where there is one.

Step 1: Sign in

Open the home page and sign in, then check the workspace shown is yours.

Step 2: Create an account

Open Signup and fill in the fields. Opening the page is not enough: the step is done when the record is saved.

Step 3: Create a page

Open Onboarding. Save it, so the work is there when you come back.

What you now have

Your LynxProfile account is set up and your first work is saved. Continue with initial setup, then use features as the reference.

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 page.
• The correct organization, company, venue, workspace, or project selected.

Steps

1. Create an account. Open Signup. Completion source: record using lynxprofile.account.created.
2. Create a page. Open Onboarding. Completion source: record using lynxprofile.page.created.
3. Add and arrange links. Open the page editor. Completion source: event using lynxprofile.links.published.
4. Review domain and sharing settings. Open Settings. Completion source: record using lynxprofile.sharing.configured.

Check it worked

Return to the product Learning page on the Help page. 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 page opened.

What is known to be incomplete or still being checked, so none of it comes as a surprise.

Still being checked

• Exact appearance on each device, message delivery, live payments, and behaviour for every role are checked by hand, so they can lag behind the rest.

2026-08-23

• Added a partner programme application form under Settings, Partner. Apply once, and referrals you send are tracked against your account.
• Arriving from a partner's referral link is now remembered while you sign up, so the person who referred you is credited.
• Affected surfaces: Settings, sign-up.
• Affected roles: account owners.

2026-08-22

• Reduced owner/admin/native startup data transfer by selecting explicit page fields, capping page-list reads, and using the dashboard analytics summary instead of downloading recent raw analytics events for native widgets.
• The sitemap now emits the most recently updated published/indexable pages within a bounded query.
• Affected surfaces: native bootstrap, owner page lists, admin overview, and sitemap generation.
• Affected roles: account owners, creators, and internal operators.

2026-08-16

• Prepared the iOS App Store submission handoff with external domain/Apple/TestFlight/App Store checklist updates, screenshot-source guidance, and privacy-answer alignment.
• Updated the privacy policy to describe web-managed Pro billing from lynxprofile.com and native feature permissions for camera, Contacts, NFC, photos, microphone, Wallet, and share actions.
• Affected surfaces: Privacy, App Store listing assets, and release operations.
• Affected roles: account owners, creators, and internal release operators.

2026-08-16

• Updated the login screen to present the shared Cre84ever account-access order: Face ID/passkey, SMS code, email code, then password.
• Added email-code sign-in for existing accounts so users can enter a 6-digit code in the app without relying on a browser magic link.
• Kept password sign-in and password reset available for recovery and new-device access.
• Affected surfaces: Login.
• Affected roles: account owners and creators signing in.
• Note: SMS and passkey-first account authentication remain setup-dependent until provider configuration and phone/passkey enrollment are completed.

2026-08-15

• Added the Android Capacitor project so LynxProfile has a Play Store packaging path alongside the existing iOS shell.
• Added Android native sync/open/debug-build/release-bundle package scripts.
• Verified both Android debug APK and release bundle generation.
• Added optional Play Store upload-key signing from release-machine environment variables.
• Added a signing readiness check and explicit keystore git ignores.
• Affected surfaces: native Android packaging and release operations.
• Affected roles: internal release operators.
• Note: local Android compilation still requires a Java runtime and the Play Store upload key details on the release machine for signed bundles.

2026-08-15

• Prepared the iOS App Store submission path by making Pro billing web-managed from the installed app.
• Affected pages: Pricing and Billing.
• Affected roles: account owners reviewing or managing Pro.

2026-08-02

Authentication or wrong workspace

1. Return to the home page.
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. Clear page-specific filters and search again.
2. Some articles are published only for certain roles.
3. Use Help if approved content is still missing.

Escalation checklist

Tell us the screen, your role, roughly when it happened, what you did, what you expected, and what happened instead. A screenshot helps. Blank out anything private first.