You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@cebe This is to allow some changes to how users work.
Having a warehouse_id on the order table will allow, in the future, for orders that changed or deleted to be updated or deleted upstream at the warehouse level.
Users will have a type assigned to them "Warehouse" user or "Ecommerce" user. A warehouse user can be assigned to warehouse identifiers. This will control what orders they can see. (maybe this needs to be a role??)
I'd like to have an API key that works for all orders associated with a user. For example, if a warehouse user requests for an order assigned to a different warehouse they should receive a 404 or other error. We are seeing more users that are using different warehouses. The different warehouses should not see orders that do not pertain to them.
Orders that do not have a warehouse ID associated with it should not be visible to the warehouse.
Adding a warehouse_id on orders will be easier to assign warehouse users to customers to see orders.
The text was updated successfully, but these errors were encountered: