Organization Settings: Profile, Billing, Storage, Integrations
The tenant-level settings that affect documents, packages, limits, billing context and the parts of setup that should not hide inside a module.
Organization settings are the configuration layer that belongs to the tenant as a whole. Legal profile, billing contact, VAT details, storage quota, package context, integration surfaces and default identity information live here. If a setting affects the whole organization, hiding it three clicks inside a warehouse page is how future admins learn colorful language.
Profile
Legal name, VAT number, registration details, addresses, contact details and logo feed generated documents such as invoices, BOLs, packing slips and settlement reports. New documents use the current profile at generation time; older documents keep the historical output they were generated with.
Package and billing context
/settings/billing shows the current package, enabled modules, usage limits, storage context, billing contact and VAT data. The package engine gates modules, sub-features and quotas from the live catalog. Mollie subscription collection is the later payment rail; the package truth already lives in ReVend.
Storage
Tenant storage quota is tracked against Supabase Storage usage for documents, photos, signatures and evidence. Approaching the limit can trigger warnings; exceeding it can block new uploads until the quota or package changes. Better a blocked upload than a silent evidence gap with a dramatic soundtrack.
Integrations
/settings/integrations is the setup area for connector context, while live system-to-system access sits under /settings/api for keys, docs, usage and webhooks. Audit-tool setup lives under /settings/core/audit-tools. Each surface has a different job; putting every secret in one magic text box would be simpler only until the first incident.