Private customer workspaces
Customer access is authenticated and organization records are associated with the tenant and workspace that owns the funding work.
Funding Command is designed around authenticated workspaces, explicit customer control, auditable actions, and limited diagnostic collection. We describe the controls we actually use rather than claiming certifications we do not hold.
Customer access is authenticated and organization records are associated with the tenant and workspace that owns the funding work.
Sensitive operational tables use server-side access patterns rather than direct anonymous browser access. Support requests are stored behind authenticated APIs.
Funding Command prepares research, drafts, budgets, reviews, and files. Certifications, signatures, portal credentials, and the final submit action remain with the applicant.
Paid checkout and subscription management use Stripe. Funding Command verifies Stripe webhook signatures before subscription events are applied.
Important workflow events—including billing changes, support requests, research, and application actions—are recorded through the application audit layer.
Issue reports can include the current page, app version, workspace/user identifiers, browser information, and an error reference. Application text, private files, passwords, and payment details are not attached automatically.
Workspace owners can manage team access and billing from inside Funding Command. Individual users can request account deletion from Account & Billing. Shared organization records may require ownership review before deletion so one user cannot destroy another organization's work.
Signed-in customers can use the in-app support button to create a tracked support request with a reference number.