Inbound
SSO / SAML
Enterprise sign-in (enterprise tier).
Read the specSolutions · Administrative · Admin
Sustain360 for Admin
The Admin operates a tenant — typically an aggregator or a dismantler group. The role lives in user provisioning, role assignment, and workflow customisation: who can do what, on which yards, against which workflows. Sustain360 puts the controls in a UI so the role does not need an engineer in the loop.
Where this role sits:Tenant administrators at aggregators and dismantler groups
A day in the life
How a admin works with Sustain360
A new yard manager joins the group. The admin provisions the user, assigns roles, and scopes the user to the right yards. A new dismantling state is added to one yard's workflow — without engineering touching the platform. A SAML group mapping is updated; SCIM keeps the rest of the lifecycle aligned.
USP · Manual vs Sustain360
What this changes for an Admin
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.
- MetricUser provisioning per new joinerManual / legacy1–2 hours across toolsWith Sustain360Under 5 minutes, one screenDelta≈ −95%
- MetricRole assignmentManual / legacyPer-tool, drifts over timeWith Sustain360Tenant-level, one modelDeltaUnified
- MetricWorkflow customisation lead timeManual / legacyEngineering ticket, weeksWith Sustain360Admin self-serve, same dayDelta≈ −95%
- MetricPermissions auditManual / legacyQuarterly, manualWith Sustain360Live, exportableDeltaLive
- MetricOff-boarding completenessManual / legacyOften partialWith Sustain360One revoke, all surfacesDeltaComplete
| Metric | Manual / legacy | With Sustain360 | Delta |
|---|---|---|---|
| User provisioning per new joiner | 1–2 hours across tools | Under 5 minutes, one screen | ≈ −95% |
| Role assignment | Per-tool, drifts over time | Tenant-level, one model | Unified |
| Workflow customisation lead time | Engineering ticket, weeks | Admin self-serve, same day | ≈ −95% |
| Permissions audit | Quarterly, manual | Live, exportable | Live |
| Off-boarding completeness | Often partial | One revoke, all surfaces | Complete |
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 |
|---|---|
| User provisioning needs an engineer. | UI-driven provisioning at the tenant level. |
| Role assignment is a spreadsheet. | Roles configured per user, per yard, with an audit trail. |
| Workflow changes mean a vendor ticket. | Workflow customisation in the tenant UI. |
| SAML group mappings drift. | SCIM keeps the user lifecycle aligned with the IdP. |
Placeholder · Customer voice
“I add a state, assign a role, finish my coffee.”
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.
Outbound
CSV / Excel export
Every grid in the product exports to CSV.
Read the specBi-directional
REST API
Public, versioned, documented (Swagger / OpenAPI).
Read the specFAQ