README
Maintained DivisionDesk documentation · Updated 2026-08-31
# SCV Applications
SCV Applications adapts the existing SCV digital membership-application workflow to DivisionDesk. Installing the package provisions the public system page `/membership-application` and adds **Organization → Membership → Applications** plus **Application Settings** in administration.
The public page can start a self-service application or be used by an authorized member to prepare an application for another person. Applicant data is saved under secure short-code/token access. Reviewers can manage status, lineage, service records, signatures, follow-up and final PDF forwarding.
## First-use configuration
Open **Organization → Membership → Application Settings**. Set the client's default state and Camp API endpoint. The service-record search/image endpoints may remain at the supplied SCV service if that service is authorized for the client, or may be changed to another approved endpoint. Add the addresses that should receive completed applications.
## Publishing
The page itself is provisioned as published by Core. It is intentionally not auto-added to public navigation. In Navigation, add the registered **Join the SCV** destination to the desired menu, or link a button directly to `/membership-application`.
## PDF dependency
The PDF builder uses the same FPDF/FPDI dependencies as the supplied application. Before Store publication, run `composer install --no-dev --optimize-autoloader` in the package root so `vendor/autoload.php` is bundled in the final ZIP. Without the vendor directory the application workflow works, but PDF generation/forwarding will report that FPDI is unavailable.
SCV Applications adapts the existing SCV digital membership-application workflow to DivisionDesk. Installing the package provisions the public system page `/membership-application` and adds **Organization → Membership → Applications** plus **Application Settings** in administration.
The public page can start a self-service application or be used by an authorized member to prepare an application for another person. Applicant data is saved under secure short-code/token access. Reviewers can manage status, lineage, service records, signatures, follow-up and final PDF forwarding.
## First-use configuration
Open **Organization → Membership → Application Settings**. Set the client's default state and Camp API endpoint. The service-record search/image endpoints may remain at the supplied SCV service if that service is authorized for the client, or may be changed to another approved endpoint. Add the addresses that should receive completed applications.
## Publishing
The page itself is provisioned as published by Core. It is intentionally not auto-added to public navigation. In Navigation, add the registered **Join the SCV** destination to the desired menu, or link a button directly to `/membership-application`.
## PDF dependency
The PDF builder uses the same FPDF/FPDI dependencies as the supplied application. Before Store publication, run `composer install --no-dev --optimize-autoloader` in the package root so `vendor/autoload.php` is bundled in the final ZIP. Without the vendor directory the application workflow works, but PDF generation/forwarding will report that FPDI is unavailable.
Still need help? Search the Community for real-world discussion, or submit a Feature Request if the product itself needs to change.