# Assign an organizational restriction

> Narrow a user's inventory and production work to selected warehouses and work centers.

URL: https://erpdocs.corexlogic.com/en/yonetim/islemler/organizasyon-kisitlamasi-verme

- **Type:** Task
- **Module:** Administration
- **Menu path:** Yönetim › Kullanıcı ve Roller › Kullanıcılar (Administration › Users and Roles › Users)
- **Screen route:** `/users`
- **Required permission:** `users.edit`
- **Prerequisites:**
  - The user's role contains the relevant write permissions (a restriction does not grant permissions; it only narrows them).

Use this to tie a warehouse supervisor to their own warehouse only, or an operator to their own line only.

## Steps

1. On the **Yönetim › Kullanıcı ve Roller › Kullanıcılar** (Administration › Users and Roles › Users) screen, select **İşlemler › Organizasyon Kısıtlaması** (Actions › Organizational Restriction) on the user's row.
   <!-- action: navigate · target: "/users" · expect: "The Organizasyon Kısıtlaması — <email> (Organizational Restriction) window, Depolar (Warehouses) tab" -->
2. On the **Depolar** (Warehouses) tab, check the warehouses the user will work in. You can search with the **Depo kodu ya da adı…** (Warehouse code or name…) box.
   <!-- action: choose · target: "Depolar" -->

   ![Organization Restriction — warehouses and work centers](https://erpdocs.corexlogic.com/en/en/img/screens/yonetim/organizasyon-kisitlamasi.png)
   1. Warehouses and Work Centers tabs
   2. No selection = no restriction; selection narrows rights
   3. Tick the allowed warehouses
   4. Clears the selection of this type

3. If a restriction is also needed in production, check the work centers on the **İş Merkezleri** (Work Centers) tab.
   <!-- action: open · target: "İş Merkezleri" -->
4. Click **Kaydet** (Save).
   <!-- action: click · target: "Kaydet" · expect: "Below the Roller (Roles) column in the list: "Kısıtlı: N depo · N iş merkezi" (Restricted: N warehouses · N work centers)" -->

**Result:** The user posts stock only in the selected warehouses and sees only those in the work queues; they enter confirmations, consumption and output only at the selected work centers. The change takes effect on the next request.

## Effect of the restriction

| Type | The restricted user… | Rejection message |
|---|---|---|
| Warehouse | cannot post stock to a warehouse they are not permitted for; cannot open physical inventory counts, warehouse tasks, waves, transfers or reservations there; sees only the selected warehouses in the work queues | `'<depo kodu>' deposunda işlem yetkiniz yok.` (You are not authorized to perform transactions in warehouse '…'.) |
| Work center | cannot post confirmations, consumption, output, capacity scheduling or backflush at a work center they are not permitted for; a restriction on a parent work center covers its child work centers | `'<iş merkezi kodu>' iş merkezinde işlem yetkiniz yok.` (You are not authorized to perform transactions at work center '…'.) |

## What you need to know

- If nothing is selected for a type, there is **no restriction** for that type — the user works in all warehouses (or
  work centers). To remove a restriction, use **Bu Türdeki Kısıtı Kaldır** (Remove the Restriction for This Type) and
  **Kaydet** (Save).
- The restriction is independent of the role and specific to the person; two people with the same role can be
  restricted to different warehouses.
- A warehouse or work center that becomes inactive appears in the saved restriction with a "pasif" (inactive) note.
- There is no company- or organization-level restriction for sales, purchasing and finance documents; visibility of
  sales documents is narrowed through sales channel membership.

## Related

- [Permission model — data restrictions](https://erpdocs.corexlogic.com/en/yonetim/yetki-modeli)
- [Role examples — warehouse supervisor](https://erpdocs.corexlogic.com/en/yonetim/rol-ornekleri)