Introduction

Client Role-based access in the OMS is designed to provide access controls and functionalities of OMS to users based on their roles, particularly focusing on client-specific operations. The Client Role-based access in OMS aims to enhance security, streamline user interactions, and provide tailored functionalities to meet the specific needs of clients.

The primary goal is to enable 3PLs (third-party logistics providers) to offer their clients a portal for order creation, tracking, and inventory management. Moreover, This enables client-specific data views in the same staging environment for testing purposes and reduces the number of staging environments.

Here are the key points:

Client-Specific Access: Users can be granted access to specific clients within the OMS. This is managed by assigning roles for client resources to users, allowing them to access data and perform actions only for those clients.

Role Assignment: Admin users with special roles (app.admin and resource.admin) can add clients to the resource. Additionally, users with the app.admin role can grant access to specific client resources to other users.

Giving a user access to the specific client(s)

Giving a user access to the specific client(s) requires certain steps to be followed:

1. Set up different Client IDs in omni-client resource domain.

   1. Give a user resource.admin access

   2. Add clientId to omni-client resource

2. Finally, Giving a user access to the specific client(s)

Add client IDs to the omni-client resource domain

, a Mandatory One-Time Setup (Managed by Increff Success Team)

In order to give client level access to users, the one-time step would be to set up different Client IDs in omni-client resource.

Client IDs can be added to the omni-client resource only by the user having app.admin as well as resource.admin access. Only the Client IDs added to omni-client are eligible for giving individual client access to any users.

Steps to give a user resource.admin access

Only app.admin user can grant resource.admin access to himself/ herself or to any other app.admin user. Below steps should be followed.

Steps to add clientId to omni-client resource

A user having both app.admin and resource.admin roles can only add client IDs to omni-client resource.

Giving a user access to the specific client(s)(Managed by Client Admin user)

Any app.admin user can grant the specific client(s) access to a user. Follow the below steps.

3PL aims to provide its clients with a comprehensive portal that facilitates order creation, order tracking, inventory management, and reporting.

Each user will now have the ability to access data for one client at a time.

User interaction and design

In OMS view itself give a client selection drop down at the top.

Remove the dropdowns for client selection from other places. Keep sending the values in APIs

Client user should be able to open OMS, and perform basic functionalities.

As a client user, I want to see/use the following screens :

1. Upload new order, inward and outward,

2. Search and view orders

3. Upload return expectations

4. Cancel order, line items etc

5. Upload SKU masters, update SKU masters

Client user should be able to open OMS, and perform advanced functionalities.

1. Create new suppliers, customers, address etc.

2. Edit suppliers, customers etc.

3. Add new product attributes, manage , virtual sku definition

Client user should be able to open CIMS and perform basic functionalities

1. Create ASN

2. Manage ASN

Out of Scope

Client users can perform both basic and advanced functionalities within the OMS. Basic functionalities include uploading orders, searching and viewing orders, and managing SKU masters. Advanced functionalities involve creating and editing suppliers, customers, and product attributes.

Screens Accessible to Users with specific client(s) Access

The dropdowns for client selection have been removed from all the screens listed below. These screens will now be accessed based on the client selected in OMS. Only clients for which the user has access will appear in the selection options.

Image Added

1. Outward Orders

   1. Upload Invoice Tax Information

   2. Order Attributes Configuration

   3. Sub-Order Cancellation

   4. Map Return Expectation To Received Return

2. Inward Orders

   1. Order Attributes Configuration

   2. Upload Invoice Tax Information

3. Inventory

   1. Create Inventory Pool

   2. Reservations

   3. Configure Manufacturable Inventory

   4. Return Inventory Pool Allocation

4. Master Settings

   1. Suppliers

   2. Customers

   3. Fulfillment Locations

   4. Partner Locations

5. Product Settings

   1. Attributes Configuration

   2. Products

   3. Capture SKU Dimensions

   4. Batch Details

   5. Missing Images

   6. Pack Box Master

6. Split / Route Settings

   1. Clusters

   2. Cluster Definition

   3. Area Cluster Mapping

7. Other Settings

   1. Client Fulfillment Location Mapping

   2. QC Fail Reasons

8. Audits

   1. Audit Log