fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Introduction
  • Functionalities
  • Creating users
  • Editing and deleting users
  • Permissions
  • Permissions within the platform
  • Permissions within the Backoffice
Edit on GitHub
  1. Core

User management

Last updated 4 months ago

Introduction

The user management feature allows a multi client workflow. This ensures that there are no mutual interference between users and that processes can be conducted simultaneously.

Furthermore, every user has a role which is connected to certain permissions in the fulfillmentools platform. Due to that, authorizations and process approvals in the different facilities can be mapped accordingly.

More information on managing users in the Backoffice can be found under . There is an available.

Functionalities

Creating users

Only users with the right are allowed to create other users.

  • The username has to be unique. Umlauts are converted automatically to their character-friendly equivalents, e.g., “ö” becomes “oe” and “ß” becomes “ss”.

  • The password must be at least 6 characters long.

  • When creating or editing a user, the primary language for the user can be defined.

Editing and deleting users

Users can be deleted. Users can also delete themselves.

If a user loses the permission to perform an action (due to a role change, a facility change or deletion of the user itself) the user gets logged out of the app or the Backoffice. If there are still jobs such as pick jobs assigned to the user, the jobs are set back to open status and all data is reset.

Permissions

There are no functionalities within the apps that require a certain role.

Permissions within the platform

Action
Fulfiller
Supervisor
Administrator

Create user

✕

Can create “fulfillers” and “supervisors”

✔

Assign facilities

✕

When creating a user, this user inherits the facility of the supervisor.

✔

Change own role

✕

✔

✔

Access to multiple facilities

bound to one facility

bound to one facility

✔

Access to administrative features

✕

access to certain administrative features on facility level

access to all features available within the platform

Permissions within the Backoffice

Section

Fulfiller

Supervisor

Administrator

Cockpit

✔

✔

✔

Tasks

✔

✔

✔

Facility

✕

✔

✔

Listings

✕

✔

✔

Storage locations

✕

✔

✔

Users

✕

A supervisor only sees users that are assigned to her facility.

✔

Settings

✕

A supervisor can only change facility-specific settings.

An administrator can change settings that affect the complete tenant.

user management REST API documentation
permissions
Apps & Clients – User