Desktop and support
Troubleshooting PartPack
Recover from sign-in, source connection, delivery and billing problems and collect safe support evidence.
Recover sign-in and email access
If the security check cannot load or has expired, use Retry security check on the sign-in or recovery form. Check the email address and spam folder when a verification or reset message is missing, and wait for the displayed resend countdown before requesting another. If a reset link is unavailable or expired, request a new one from the sign-in page. Never share passwords, email links or verification codes.
Check the selected Organisation and access
A successful LEVRTEK sign-in does not grant membership in every product or Organisation. Confirm the selected Organisation. Ask its administrator to review your invitation, membership and role if an action is unavailable or permission is denied. Creating another identity does not restore Organisation permissions.
Check a waiting or disconnected source
Open Integrations to review the source or Device state. For local or network sources, keep PartPack Desktop open and signed in, and check that your Windows identity can access the approved source. Retry the affected governed action after the connection recovers. Review ambiguous, missing or mismatched document evidence before continuing; do not treat a connection recovery as approval of those documents.
Check delivery evidence before sending again
Inspect the Package delivery result and recipient evidence. Provider acceptance does not prove that a message was read. A bounce, complaint or suppressed recipient needs review. If an outcome is unknown, do not create another send to work around it: preserve the correlation ID and ask for reconciliation through Help & support. Confirm the frozen Package Version and recipients again before any permitted retry.
Check plan access after checkout
Open Plans & billing to inspect the current Organisation access state. A return from Stripe alone does not confirm a plan change; PartPack reconciles billing evidence before changing access. If checkout and the app disagree, keep the correlation ID and use the billing problem category in Help & support rather than paying again to try to force access.
Review the exact support fields
Record the correlation ID shown with the problem. In Help & support, choose the category and impact, select only the relevant diagnostic categories, and inspect the exact Support Ticket preview before confirming. Keep files, filenames, part numbers, Supplier identities, email bodies, local paths and credentials out of support fields. If submission is unavailable, keep the correlation ID and ask your Organisation administrator to check the service configuration before trying again.

