Summary and recommendation
ShipStation 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.
ShipStation uses a flat permission model: one Account Owner plus any number of standard users, each configured with individual permission toggles across orders, shipments, products, reporting, store visibility, and account settings.
There are no saved role templates - every app access configuration is set per user at the time of creation with no shortcuts.
Seat limits are enforced per plan tier, so adding users beyond the cap requires upgrading to the next shipment-volume tier, not purchasing individual add-on seats.
Quick facts
| Admin console path | Account Settings > Users |
| 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 |
|---|---|---|---|---|---|
| Account Owner | Full access to all account settings, billing, integrations, stores, users, and shipping operations. Cannot be removed or demoted via the UI. | Cannot transfer ownership to another user through self-service UI. | All plans | Included in plan; counts as one user seat. | Only one Account Owner per account. If the owner leaves the organization, ownership transfer requires contacting ShipStation support. |
| User (standard) | Access is determined by granular permission toggles set by the Account Owner or an admin-level user. Can be granted access to specific stores, order management, shipment creation, reporting, and settings areas selectively. | Cannot access billing or account-level settings unless explicitly granted. Cannot manage other users unless the Users permission is enabled. | All paid plans; number of included seats varies by plan tier. | Included up to the plan seat limit; additional seats may require a plan upgrade. | Each user consumes one seat. Plans have hard seat caps (e.g., Starter plan allows 1 user, higher tiers allow more). Exceeding the seat limit requires upgrading the plan. |
Permission model
- Model type: permission-sets
- Description: ShipStation uses a flat user model with granular per-user permission toggles rather than named roles. The Account Owner configures individual permission checkboxes for each user across categories including Orders, Shipments, Products, Reports, Account Settings, and Store access. There are no saved role templates; permissions are set per user.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Per-user toggle-level permissions across functional areas: order management, shipment creation, product management, reporting, store visibility, and account settings sub-sections.
How to add users
- Log in as Account Owner or a user with Users permission enabled.
- Navigate to Account Settings > Users.
- Click 'Add User' (or 'Invite User').
- Enter the new user's name and email address.
- Set a password or allow the user to set their own via invitation email.
- Configure granular permission toggles for the user.
- Select which stores the user can access.
- Save the new user record.
Required fields: Full name, Email address, Password (or invitation-based setup)
Watch out for:
- The number of users you can add is capped by your plan tier. Attempting to add a user beyond the seat limit will prompt a plan upgrade.
- Permissions must be configured at the time of creation; newly added users have no permissions by default until toggles are enabled.
- Store access must be explicitly granted per user; new stores added to the account are not automatically visible to existing users.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Not documented |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: ShipStation's official help documentation describes the ability to delete users from Account Settings > Users. Deleted users lose access immediately. Historical shipment and order records created by the user are retained in the account.
- Navigate to Account Settings > Users.
- Locate the user to be removed.
- Click the delete or remove option associated with that user.
- Confirm the action when prompted.
| Data impact | Behavior |
|---|---|
| Owned records | Shipments, orders, and other records created by the deleted user remain in the account and are not removed. |
| Shared content | Shared resources such as automation rules, product records, and store configurations are unaffected by user deletion. |
| Integrations | No documented impact on store or carrier integrations from removing a user. |
| License freed | Deleting a user frees the seat, making it available for a new user within the same plan tier. |
Watch out for:
- If the Account Owner needs to be removed, this cannot be done via self-service; ShipStation support must be contacted.
- There is no documented 'deactivate without delete' (suspend) option in the standard UI; removal is a deletion action.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| User seat | One named user with configurable permissions. All seats are the same type; differentiation is by permissions assigned, not seat class. | Included up to plan seat limit. Additional seats require upgrading to a higher plan tier rather than purchasing individual add-on seats. |
- Where to check usage: Account Settings > Users - displays all current users and the total count against the plan limit.
- How to identify unused seats: No built-in last-login reporting is documented in official help articles. Admins must manually review the user list and cross-reference activity.
- Billing notes: ShipStation plans are priced primarily by monthly shipment volume, not by seat count. Seat limits are a secondary constraint per plan tier. Starter (1 user), through higher tiers which allow progressively more users up to unlimited on the highest tier. Upgrading for seats requires moving to the next shipment-volume tier.
The cost of manual management
ShipStation has no SCIM and no user-management API, which pushes provisioning and deprovisioning entirely into manual UI workflows. That means navigating to Account Settings > Users for every joiner, mover, or leaver - and manually toggling each permission checkbox with no role templates to speed up the process.
There is no last-login or activity audit log in the UI, so identifying inactive users for cleanup requires cross-referencing the user list against external records. When an Account Owner leaves the organization, access recovery is blocked until ShipStation support completes an ownership transfer, creating a hard dependency on vendor response time.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Every app in your stack that lacks automated provisioning adds manual overhead to your IT workflows - ShipStation is no exception, and its per-user toggle model means that overhead compounds with each new hire or role change.
The tool is appropriate for small to mid-size e-commerce operations where user counts are low and provisioning frequency is minimal. Teams with frequent onboarding cycles, strict access-review requirements, or multi-IdP environments will encounter meaningful administrative overhead.
The Account Owner single-point-of-failure is a concrete risk that should be mitigated by documenting the support escalation path before it is needed.
Bottom line
ShipStation's user management is functional for small teams but is entirely manual and UI-bound. There is no SCIM, no role templates, no activity audit log, and no self-service ownership transfer - meaning every access change requires direct admin intervention in the ShipStation UI.
Organizations managing more than a handful of users, or those with compliance-driven access review requirements, should plan for the operational overhead this model creates and establish a documented process for the Account Owner succession scenario before it becomes urgent.
Automate ShipStation 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.
