Summary and recommendation
Returnly user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Returnly is a returns management platform that was acquired by Affirm in 2021. It is sold as part of Affirm's merchant offerings, and enterprise features - including user management, roles, and permissions - are not publicly documented.
Admins needing to provision or deprovision users should contact Affirm enterprise sales directly for current capabilities.
Quick facts
| Admin console path | Public documentation does not expose a Returnly merchant admin path for managing internal users. Operational access appears to be tenant-specific and vendor-managed after the Affirm acquisition. |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Unknown |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
Permission model
- Model type: role-based (public details not documented)
- Description: Public Returnly and Affirm documentation do not describe the internal user-role model for merchant admins. Treat permissions as tenant-specific and vendor-confirmed rather than publicly documented.
- Custom roles: No
- Custom roles plan: Not publicly documented
- Granularity: Not publicly documented
How to add users
- Public documentation does not provide a self-serve internal user-invite workflow for Returnly merchant admins.
- Use the merchant portal or account-team process defined in your tenant, and validate the exact onboarding path with Affirm/Returnly support.
- If SSO or identity integrations are part of your contract, confirm those settings directly with the vendor because no public setup guide is available.
Required fields: Tenant-specific merchant admin details as defined by Returnly/Affirm
Watch out for:
- Because public docs do not expose user-management procedures, do not automate Returnly onboarding from assumptions alone.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public Returnly documentation does not describe whether merchant admins can deactivate or permanently delete internal users.
- Follow the tenant-specific merchant admin process documented internally by your Returnly/Affirm team.
- If the user authenticates through a federated identity provider, disable access there first.
- Confirm data-retention and historical-record behavior with the vendor because no public offboarding guide is available.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- Delete semantics, restore behavior, and asset reassignment are not publicly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Custom contract | Returnly pricing and user-seat structure are not publicly published after the Affirm acquisition. | Custom (contact Affirm) |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: Returnly is sold as part of Affirm's merchant offerings. Pricing is custom and not publicly listed. Contact Affirm sales for seat and billing details.
The cost of manual management
Because no self-serve admin console path, user types, or permission model are publicly documented for Returnly, the true overhead of manual user management is difficult to quantify.
Every app without documented provisioning workflows creates friction at onboarding and offboarding - access may persist after an employee departs simply because there is no published removal process to follow. Until Affirm clarifies the admin surface, teams should treat Returnly as a manually audited app with no reliable self-service controls.
The decision
If your organization uses Returnly today, the immediate action is to contact Affirm enterprise sales to establish what admin controls, seat management, and offboarding workflows are available. Do not assume that SSO or automated deprovisioning exists - neither is publicly documented.
Every app in your stack without a confirmed offboarding path is a standing access risk, and Returnly should be flagged accordingly in any access review.
Bottom line
Returnly's user management capabilities are opaque following its 2021 acquisition by Affirm. No public documentation exists for admin console paths, permission models, SCIM support, or offboarding procedures.
Until Affirm publishes or directly confirms enterprise identity features, Returnly should be treated as a manually governed app requiring direct vendor engagement for any provisioning or deprovisioning work.
Automate Returnly workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
