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. Public profile, billing contact, VAT details, storage quota, package context, display defaults and integration surfaces 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
/settings/organization-profile is the tenant’s public card: legal name, support e-mail, general phone number, street, city, postal code, country and website. That information can appear on external-facing places such as widgets, trade-in flows, support context and customer communication. Keep it plain and recognizable. “Support Ninjas” is charming in a meeting and less charming on a compliance document. The legal and invoicing side — billing e-mail, legal name, VAT number and invoice address — sits on the billing page, next to the package it pays for.
Package and billing context
/settings/billing explains what the tenant pays ReVend for platform access; it has nothing to do with Core invoices, pickup charges, escrow or deal money. It shows the current package, subscription status, billing cycle, price and current period; included and excluded modules; live usage for team members, assets, auctions, storage and API calls against the package limits; the billing contact and VAT data tenant admins can edit; a read-only payment method; and the ReVend SaaS invoice history with any open, pending, failed or expired subscription payments. Arriving from a gated module via /settings/billing?upgrade=... shows which package context was in play — Market, Sourcing, API access, Auction publishing — as an explanation, not a checkout. Package changes and payment-method management are read-only on this page; Mollie is used for ReVend’s own subscription billing and nothing else.
Storage
Tenant storage quota is tracked against Supabase Storage usage for documents, photos, signatures and evidence. Approaching the limit triggers warnings; exceeding it blocks new uploads on guarded paths until the quota or package changes. Better a blocked upload than a silent evidence gap with a dramatic soundtrack.
Team, display and language
/settings/users is where the team is invited and roles are assigned. /settings/display holds the tenant-wide list and display defaults, /settings/core/costs the cost settings Core uses. The app language is not an organization setting at all: it is one account preference, changeable under Settings, in the trade-in portal profile and on the mobile screens, and every surface writes the same preference. Choose Dutch on the phone in the warehouse and the desktop follows.
Integrations
/settings/integrations is the setup area for connectors, while live system-to-system access sits under /settings/api for keys, docs, usage and webhooks, and audit-tool setup lives under /settings/core/audit-tools. Carbontrace is the live connector, with its own page at /settings/integrations/carbontrace for the tenant’s API key, base URL, an on/off switch and the connection status. Accounting providers show a card that says so honestly and points to the manual route that works today; there is no secret input field anywhere until something is actually stored. A complete-looking form that saves nothing is worse than no form.
The starter kit
A new tenant does not land in an empty shell. Signup seeds 44 system services, 24 certifications, 22 market categories, market filters, a fee setting, 21 saved views and 7 pallet types, so the first afternoon goes to receiving a pallet rather than building catalogs. An empty environment is not a neutral starting point; it is the moment a tester leaves.