Summary and recommendation
Blue Yonder 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.
Blue Yonder does not offer a self-service admin console path for user provisioning that is publicly documented.
User lifecycle management - adding, deactivating, and role-assigning - is handled through enterprise onboarding processes that are gated behind an authenticated support portal.
Admins should expect to work through an implementation partner or Blue Yonder professional services rather than a standalone admin UI.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant capabilities outside the features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: Blue Yonder appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required before the user can sign in.
| 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 docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations, service accounts, or credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Pricing is custom enterprise contract, reported to start around $100K/year. Seat and license details are negotiated per contract and not publicly documented.
The cost of manual management
Because provisioning workflows are not self-serve, every app access change - new hire, role shift, or offboarding - likely requires a support ticket or partner engagement rather than a direct admin action. This creates compounding overhead at scale: IT teams cannot audit, add, or remove users on demand without going through a mediated process.
License and seat details are negotiated per contract, so identifying unused access requires manual reconciliation against contract terms rather than a usage dashboard.
The decision
Blue Yonder is an enterprise supply chain platform with pricing reported to start around $100K/year on custom contracts; seat and license terms are not publicly disclosed. Given the absence of documented self-service provisioning, IT and security teams should explicitly negotiate access management SLAs and admin tooling access during the procurement process.
Every app in your stack that lacks self-serve provisioning increases the operational surface area for access drift - Blue Yonder is a high-risk candidate for that pattern.
Bottom line
Blue Yonder's user management posture is opaque by design: provisioning, role configuration, and license tracking are all mediated through professional services or partner channels rather than a self-service admin console.
For IT teams managing access at scale, this means offboarding and access reviews require manual coordination rather than automated workflows.
Organizations evaluating Blue Yonder should treat access management capability as a first-class procurement requirement and verify current tooling availability directly with their Blue Yonder account team.
Automate Blue Yonder 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.
