Create a role
Module
Administration
Menu path
Yönetim › Kullanıcı ve Roller › Roller (Administration › Users and Roles › Roles)
Screen route
/rolesRequired permission
roles.createPrerequisites
- It is clear which tasks the role will perform. Predefined roles and recipes: Role examples.
A role is the name of a set of permissions that are granted to users together. You design the role once and assign it to many people; when the role's permissions change, everyone who holds the role is affected.
Steps
- Open the Yönetim › Kullanıcı ve Roller › Roller (Administration › Users and Roles › Roles) screen and click the Yeni Rol (New Role) button.
- Enter the role's name in the Rol adı (Role name) field. The name cannot be changed later.
- If you want to start from a predefined role, select the template from the Rol şablonu (Role template) list (e.g. Satış Temsilcisi · Eleman (Sales Representative · Staff)). The permissions and screens are filled from the template; Kapsam (yazma) (Scope (write)) shows the write modules. To start from scratch, leave Şablonsuz — yetkileri elle seç (No template — select permissions manually).
New Role — properties and template - 1Role name — cannot be changed later
- 2Role template — starting permissions
- 3Scope — modules the role writes in
- 4Permissions and Screens tabs
- 5Create Role
- Switch to the Yetkiler (Permissions) tab. Type a fragment without Turkish characters in the search box (Ara… (modül, sayfa ya da işlem) — Search… (module, page or action)), e.g.
siparis; the matching branches open. - Check the boxes of the permissions to be granted and uncheck those not to be granted. A module or page box selects all the permissions below it together. Example: uncheck Satış Siparişleri · Kapat (Sales Orders · Close).
Role — permission tree - 1Granted / total permissions
- 2Search — module, page or action
- 3Module — ticks all at once
- 4Action — a single permission
- 5Permission not granted in this role
- 6Read Only — keeps only View permissions
- On the Ekranlar (Screens) tab, check the screens that will appear in the menu. The screens of the resources you granted write permission for are checked automatically; if any are missing, click Yazdığı Ekranları İşaretle (Mark the Screens It Writes To).
Role — Screens (menu catalog) - 1All screens — every permitted screen in the menu
- 2Adds screens the role writes to
- 3Area › section › screen — shown in the menu
- 4Selected / total screens
- Click Rolü Oluştur (Create Role).
Result
The role is saved and appears in the Roller (Roles) list (the permission count in the İzin (Permissions) column). To assign the role to users: Assign a role to a user.
What you need to know
- A role created from a template is not bound to the template. All of its permissions can be changed; a release upgrade does not add permissions to this role. The predefined role itself, however, is bound to the template, and the template's permissions are locked.
- Starting from an existing role: the role's İşlemler › Kopyala (Actions › Copy) in the list opens the new role window with the role's permissions and screens ("… rolünün N izniyle başlar; ad verip izinleri daraltın." — Starts with the N permissions of the … role; give it a name and narrow the permissions.).
- The Salt Okunur (Read-Only) button reduces the selection to Görüntüle (View) permissions only; it is a quick start for a read-only role.
- If the role was created but the permissions could not be saved: "'…' rolü oluşturuldu ancak izinleri kaydedilemedi. Rolü listeden açıp izinleri yeniden deneyebilirsiniz." (The role '…' was created but its permissions could not be saved. You can open the role from the list and try the permissions again.)
- If a role with the same name exists: "'…' adında bir rol zaten var." (A role named '…' already exists.) If the name is empty: "Rol adı zorunlu." (Role name is required.)
- The Screens tab does not grant permissions: a screen without permission does not appear in the menu even if it is checked in the catalog.
- In this release, the search in the tree does not match terms with Turkish characters ("sipariş" → "Eşleşen izin yok." — No matching permission.); use a fragment without such characters.