Skip to content
Troubleshooting

Account and shared inbox access

Troubleshoot Qubeforms sign-in, missing forms, and shared inbox permissions. Verify account ownership, team membership, plan features, and account synchronization.

1. Confirm the customer account

Sign in through Account with the username or email and password used for your Qubeforms billing account. If credentials are rejected, use Forgot password? rather than repeated guesses. The default login throttle allows eight attempts per 15-minute window, checked by source IP and account identity. Wait before trying again. See Profile and password for the reset workflow.

2. Find a missing owned form

Check the customer identity shown in Profile and return to Forms. Similar email addresses or a second billing account can lead to a different workspace. Paused and archived forms remain listed, although their public endpoints reject submissions. Ask support through the site to investigate ownership if the correct account is missing a form; creating a replacement gives your website a different endpoint.

3. Check shared inbox membership

Ask the owner to confirm that your existing Qubeforms customer email was added to that specific form and that the owner’s plan still includes team inboxes. Shared access requires Pro or Business. Viewer access permits reading and exporting; Triage also permits inbox organization, assignments, and private notes. Neither grants form settings or key rotation. A notification recipient is not automatically a team member.

4. Resolve unavailable settings or stale pages

Check that you own the selected form and that its current plan includes the feature. For stale or rejected dashboard actions, preserve unsaved input, reload, and sign in again if the session expired. Do not bypass the dashboard’s session or form protections by copying its requests into public API calls. Read keys authorize reading only.

5. Get help with synchronization

If a completed purchase is not reflected in the workspace, follow Billing, invoices, and cancellation. For unresolved access issues, provide support with your account email, form identifier, UTC time, and the action and error you see. Exclude passwords, cookies, bearer keys, and reset links from the report.

Keep private credentials private

Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.