Inbound
SSO / SAML
Enterprise sign-in (enterprise tier).
Read the specSolutions · Administrative · SuperAdmin
Sustain360 for SuperAdmin
The SuperAdmin operates the Sustain360 platform itself — onboarding new aggregators, configuring tenancy isolation, and stewarding the security posture. The role lives in the controls that decide where an aggregator's data starts and where it ends.
Where this role sits:Sustain360 platform operators
A day in the life
How a superadmin works with Sustain360
Most days look like configuration: a new aggregator's tenancy stamped out against the multi-tenant template, role-scoped database connection pools wired, audit visibility confirmed. Less common: a security review against the existing tenants. The platform is a single instance; the tenants are independent — and the SuperAdmin keeps the line clean.
USP · Manual vs Sustain360
What this changes for a SuperAdmin
A side-by-side view of the legacy / manual way of working against the Sustain360 way — with concrete, illustrative numbers from typical customer-development scenarios.
- MetricTenant onboarding timeManual / legacy4–8 weeks setupWith Sustain360Days, scriptedDelta≈ −90%
- MetricTenancy isolation guaranteeManual / legacyShared DB, manual partitioningWith Sustain360Role-scoped connection poolsDeltaEnforced
- MetricPer-tenant audit visibilityManual / legacyEach tenant reports upWith Sustain360Platform-level audit feedDeltaLive
- MetricSecurity posture review cadenceManual / legacyAnnual scrambleWith Sustain360Continuous, event-loggedDeltaContinuous
- MetricAggregator provisioning stepsManual / legacy20+ manual stepsWith Sustain360Templated, under 5 stepsDelta≈ −75%
| Metric | Manual / legacy | With Sustain360 | Delta |
|---|---|---|---|
| Tenant onboarding time | 4–8 weeks setup | Days, scripted | ≈ −90% |
| Tenancy isolation guarantee | Shared DB, manual partitioning | Role-scoped connection pools | Enforced |
| Per-tenant audit visibility | Each tenant reports up | Platform-level audit feed | Live |
| Security posture review cadence | Annual scramble | Continuous, event-logged | Continuous |
| Aggregator provisioning steps | 20+ manual steps | Templated, under 5 steps | ≈ −75% |
Illustrative — based on customer-development scenarios in the dismantling, salvage, and parts-resale industry. Real outcomes vary by yard size, workflow maturity, and integration scope. Reference contacts available on request.
Pain → Outcome
Pain today, outcome with Sustain360
Five to seven concrete pains this role lives with today, paired with the specific Sustain360 outcome that removes each one.
| Pain today | With Sustain360 |
|---|---|
| Onboarding a new aggregator is bespoke every time. | Multi-tenant template stamps out a new aggregator in a known shape. |
| Tenancy isolation is hard to verify. | Role-scoped database connection pools enforced at the data layer. |
| Cross-tenant audit needs a separate tool. | Platform-level audit visibility across tenants without crossing data boundaries. |
| Security posture changes don't propagate cleanly. | Platform-level controls applied with versioned configuration. |
Placeholder · Customer voice
“Tenants are independent at the data layer. That's the only way to run a multi-tenant platform.”
Workflow stages
Workflow stages most relevant to this role
The stages this role touches most often. Each stage is a page in its own right with capabilities, integrations, and FAQs.
Integrations
Integrations most relevant to this role
Connectors that matter to this role in practice. Browse every integration in the integrations directory.
Bi-directional
REST API
Public, versioned, documented (Swagger / OpenAPI).
Read the specOutbound
Webhooks
Outbound event delivery for order, stock, and state-change events.
Read the specFAQ