Summary and recommendation
ShipBob 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.
ShipBob's merchant dashboard provides a role-based user management system accessible at Settings > Users (app.shipbob.com).
Only Admin-level users can invite or remove other users - non-admins have no access to user management controls.
The permission model is coarse: predefined roles only, with no documented support for granular per-feature toggles or custom role creation.
Quick facts
| Admin console path | Settings > Users (within the ShipBob merchant dashboard) |
| 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 |
|---|---|---|---|---|---|
| Admin | Full access to all account settings, billing, order management, inventory, analytics, and user management including inviting and removing users. | Only the account owner or existing Admin can invite new users or modify roles. | |||
| Viewer / Read-Only | Can view orders, inventory, and analytics dashboards. Cannot make changes to orders, settings, or user accounts. | Cannot create or edit orders, manage inventory, change account settings, or manage users. | Exact role name and permission boundaries not fully enumerated in publicly available documentation; details may vary. |
Permission model
- Model type: role-based
- Description: ShipBob uses a role-based access model. Users are assigned a predefined role (e.g., Admin, Viewer) when invited. Granular custom role creation is not publicly documented.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Coarse - predefined roles only; no documented per-feature permission toggles.
How to add users
- Log in to the ShipBob merchant dashboard at app.shipbob.com.
- Navigate to Settings.
- Select the Users section.
- Click 'Invite User' or equivalent button.
- Enter the invitee's email address.
- Select the appropriate role for the user.
- Send the invitation. The invitee receives an email to accept and set up their access.
Required fields: Email address, Role selection
Watch out for:
- Inviting user requires Admin-level access; non-admin users cannot invite others.
- Invitee must accept the email invitation before gaining access.
- Number of permitted users per account is not publicly documented; no stated seat cap found in official sources.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official documentation does not explicitly describe whether user accounts are deleted or deactivated. The remove/revoke flow is not fully detailed in publicly available help center articles as of research date.
- Log in to the ShipBob merchant dashboard at app.shipbob.com.
- Navigate to Settings > Users.
- Locate the user to be removed.
- Select the option to remove or revoke access for that user.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- Official documentation does not detail what happens to orders or records associated with a removed user.
- The account owner role cannot be removed via the Users settings panel; ownership transfer process is not publicly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Merchant User Seat | Access to ShipBob merchant dashboard. Software access is included at no additional per-seat charge per publicly available pricing information. | No documented per-seat fee; ShipBob pricing is usage-based (fulfillment, storage, receiving). |
- Where to check usage: Settings > Users within the ShipBob merchant dashboard.
- How to identify unused seats: No documented automated tool for identifying inactive users; Admin must manually review the Users list and last-login data if available.
- Billing notes: ShipBob's pricing model is usage-based (fulfillment fees, storage, receiving). No per-seat software licensing fee is publicly documented. Adding users does not appear to incur additional subscription cost based on available pricing information.
The cost of manual management
ShipBob's pricing is usage-based - fulfillment fees, storage, and receiving - with no documented per-seat software charge. Adding users to the merchant dashboard does not appear to incur additional subscription cost based on available pricing information. No seat cap is publicly documented, and there is no automated tool for identifying inactive users;
Admins must manually audit the Users list.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
For teams managing every app in their stack through a centralized identity workflow, ShipBob's manual-only user management introduces friction at both onboarding and offboarding. There is no SSO, no IdP provisioning, and no documented ownership-transfer path.
Removal steps exist in the dashboard, but what happens to records tied to a removed user is not publicly documented - a meaningful gap for audit and compliance purposes.
Bottom line
ShipBob covers basic access control for small merchant teams: invite by email, assign Admin or Viewer, revoke when done.
The model breaks down at scale - no SCIM, no SSO, no custom roles, and no automated inactive-user detection mean that every app access review and offboarding action requires a manual dashboard visit by an Admin.
Teams with compliance requirements or frequent staff turnover should account for this operational overhead.
Automate ShipBob 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.
