# Grant extra permissions

> Grant a user person-specific permissions beyond their role, or show all permitted screens in their menu.

URL: https://erpdocs.corexlogic.com/en/yonetim/islemler/ekstra-yetki-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 is active.

An extra permission is the way to grant a single person a permission above their role: it opens up a temporary or
exceptional task for a user without changing the role.

## Steps

1. On the **Yönetim › Kullanıcı ve Roller › Kullanıcılar** (Administration › Users and Roles › Users) screen, select **İşlemler › Ekstra Yetkiler** (Actions › Extra Permissions) on the user's row.
   <!-- action: navigate · target: "/users" · expect: "The Ekstra Yetkiler — <email> (Extra Permissions) window; permissions that come from roles are locked and checked" -->
2. Find the permission with the **Ara… (modül, sayfa ya da işlem)** (Search… (module, page or action)) box (type a fragment without Turkish characters, e.g. `teklif`).
   <!-- action: fill · target: "Ara… (modül, sayfa ya da işlem)" · value: "teklif" -->
3. Check the permission you want to grant. Locked permissions (those that come from roles) cannot be changed.
   <!-- action: choose · target: "Satış Teklifleri · Onayla" -->

   ![Extra Permissions — personal grants](https://erpdocs.corexlogic.com/en/en/img/screens/yonetim/ekstra-yetkiler.png)
   1. All screens in menu — grants nothing
   2. Search permissions
   3. Locked — from a role, cannot be removed here
   4. Grant a permission the role lacks
   5. Reduce extra grants to read-only

4. If you want all permitted screens to appear in the person's menu regardless of their role's catalog, check **Bütün ekranları göster** (Show all screens); this does not grant any permission.
   <!-- action: choose · target: "Bütün ekranları göster" -->
5. Click **Kaydet** (Save).
   <!-- action: click · target: "Kaydet" -->

**Result:** The additional permission takes effect on the user's next request. The permission stays with this person only; other users who hold the role are not affected.

## What you need to know

- Extra permissions **only add**. To take a permission that comes from a role away from a person, give them a narrower role.
- **Ek İzinleri Salt Okunur Yap** (Make Additional Permissions Read-Only) reduces only the additional permissions granted
  directly in this window to view permissions; it does not touch those that come from roles.
- Additional permissions are tied to the person and do not appear in the Users list; review the exceptions in this
  window at regular intervals.
- The `users.import` permission can be granted only by an administrator who holds this permission.
- Approval permissions such as **Onayla** (Approve) are not sufficient on their own: if a step of the approval template
  requires a specific role, the user must also hold that role.

## Related

- [Users screen](https://erpdocs.corexlogic.com/en/yonetim/ekranlar/kullanicilar)
- [Permission model](https://erpdocs.corexlogic.com/en/yonetim/yetki-modeli)