mirror of
https://github.com/erpnext/foundation.git
synced 2026-10-16 18:00:47 +02:00
Replace outdated screenshot
This commit is contained in:
BIN
foundation/www/docs/assets/img/users-and-permissions/setting-up-permissions-employee-user-permissions.png
Executable file → Normal file
BIN
foundation/www/docs/assets/img/users-and-permissions/setting-up-permissions-employee-user-permissions.png
Executable file → Normal file
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB After Width: | Height: | Size: 156 KiB |
@@ -55,7 +55,7 @@ Leave Application is a good **example** that encompasses all areas of Permission
|
||||
<img class="screenshot" alt="Giving Submit and Cancel permissions to HR Manager for Leave Applications. 'Apply User Permissions' is unchecked to give full access." src="{{docs_base_url}}/assets/img/users-and-permissions/setting-up-permissions-hr-manager-role.png">
|
||||
|
||||
2. **Leave Approver should be able to see and update Leave Applications applicable to him/her.**
|
||||
Leave Approver is given Read and Write access at Level 0, with Apply User Permissions enabled. Relevant Employee Documents should be enlisted in the User Permissions of Leave Approvers. (This effort is reduced for Leave Approvers mentioned in Employee Documents, by programmatically creating User Permission records.)
|
||||
Leave Approver is given Read and Write access at Level 0. Relevant Employee Documents should be enlisted in the User Permissions of Leave Approvers. (This effort is reduced for Leave Approvers mentioned in Employee Documents, by programmatically creating User Permission records.)
|
||||
|
||||
<img class="screenshot" alt="Giving Read, Write and Submit permissions to Leave Approver for Leave Applications.'Apply User Permissions' is checked to limit access based on Employee." src="{{docs_base_url}}/assets/img/users-and-permissions/setting-up-permissions-leave-approver-role.png">
|
||||
|
||||
|
||||
Reference in New Issue
Block a user