Getting Support

CareNova is sold and supported through CodeCanyon. All support requests, bug reports, and questions go through the CodeCanyon item support system — not by email or social media.

What Is Included

Every purchase of CareNova includes 6 months of item support from the date of purchase. During this period support covers:

• Answering questions about how features work

• Helping with issues caused by a bug in the item

• Assistance with included third-party assets

• Help with installation if something is not working as documented

Support does not cover:

• Customization or feature additions beyond what is documented

• Issues caused by modifications you have made to the codebase

• Third-party service configuration (Supabase, Vercel, Resend) beyond what the documentation covers

• General Next.js, TypeScript, or PostgreSQL questions unrelated to CareNova specifically

If your 6 months of included support has expired, extended support can be purchased as an add-on from the CodeCanyon item page.

Registering Your Purchase

Before contacting support, confirm your purchase is registered so your license can be verified quickly.

1. Log in to your Envato / CodeCanyon account

2. Go to Downloads and locate CareNova in your purchase history

3. Your purchase code is listed under the item — copy and keep it somewhere accessible

4. Activate your installation at https://yourdomain.com/setup using this purchase code

Your purchase code is the identifier used to verify your license when you contact support. Have it ready when submitting a support request.

How to Contact Support

Support requests are submitted directly on the CodeCanyon item page:

1. Go to the CareNova item page on CodeCanyon

2. Click the Support tab

3. Click Ask a Question or Submit a Bug Report

4. Fill in the form with as much detail as possible (see below)

5. Submit — you will receive a response within the support SLA

Response times follow CodeCanyon's standard support SLA. You will receive a notification via email when a response is posted.

How to Report a Bug Effectively

A well-written bug report gets resolved faster. Include the following in every bug report:

What you were doing Describe the exact steps that led to the issue — which page you were on, what you clicked, what you submitted. The more specific the better.

What you expected to happen Describe what the correct behavior should have been.

What actually happened Describe what went wrong — error message, unexpected behavior, blank screen, etc.

Environment details

Screenshots or screen recordings A screenshot of the error or unexpected behavior is often worth more than a written description alone. If the issue involves a sequence of steps, a short screen recording is ideal.

Error messages Copy the full error message from the browser console or server logs — do not paraphrase it. The exact wording and stack trace is what allows the issue to be reproduced and diagnosed quickly.

Steps already tried Note anything you have already attempted to resolve the issue so the response does not repeat suggestions you have already ruled out.

Before Submitting a Support Request

Check these first — many common issues are resolved without needing to open a ticket:

• Read the relevant module article in this documentation — every module article has a Troubleshooting section at the bottom

• Check the FAQ collection for answers to common questions

• Confirm your environment variables are set correctly — see the Environment Variables guide

• Confirm the Supabase storage buckets exist and are set to Public — see the Supabase Setup guide

• Run npm run build locally and check for build errors in the output

• Check the browser console and server terminal for error messages

What to Do If Support Has Expired

If your 6 months of included support has expired you have two options:

Purchase extended support — available as an add-on from the CareNova item page on CodeCanyon. This extends your support period and gives you continued access to bug fixes and assistance.

Use the documentation — this documentation covers every module, the full architecture, database schema, deployment, security, and common questions in detail. Most issues that arise after the support period can be resolved by reading the relevant article.