From 7030817bf218f95df4615c32a773961b8922a5ba Mon Sep 17 00:00:00 2001 From: Kenneth Sequeira <33246109+kennethsequeira@users.noreply.github.com> Date: Wed, 17 Jan 2018 16:13:28 +0530 Subject: [PATCH] fixed image links in role based permissions and user permisissions. Fixed a spelling mistake in user permissions (#12500) --- .../users-and-permissions/role-based-permissions.md | 4 ++-- .../en/setting-up/users-and-permissions/user-permissions.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/erpnext/docs/user/manual/en/setting-up/users-and-permissions/role-based-permissions.md b/erpnext/docs/user/manual/en/setting-up/users-and-permissions/role-based-permissions.md index 6f11ecb563..a65a295cbe 100644 --- a/erpnext/docs/user/manual/en/setting-up/users-and-permissions/role-based-permissions.md +++ b/erpnext/docs/user/manual/en/setting-up/users-and-permissions/role-based-permissions.md @@ -48,7 +48,7 @@ Leave Application is a good **example** that encompasses all areas of Permission 1. **An Employee should only be able to access his/her Leave Application.** Hence, Apply User Permissions should be enabled for Employee Role, and a User Permission record should be created for each User Employee combination. (This effort is reduced for Employee Document Type, by programmatically creating User Permission records.) -Limiting access to Leave Applications for a user with Employee Role via User Permissions Manager +Limiting access to Leave Applications for a user with Employee Role via User Permissions Manager 1. **HR Manager should be able to see all Leave Applications.** Create a Permission Rule for HR Manager at Level 0, with Read permissions. Apply User Permissions should be disabled. @@ -63,7 +63,7 @@ Leave Application is a good **example** that encompasses all areas of Permission 3. **It should be Approved / Rejected only by HR User or Leave Approver.** The Status field of Leave Application is set at Level 1. HR User and Leave Approver are given Read and Write permissions for Level 1, while everyone else (All) are given Read permission for Level 1. -Limiting read access for a set of fields to certain Roles +Limiting read access for a set of fields to certain Roles 4. **HR User should be able to delegate Leave Applications to his/her subordinates** diff --git a/erpnext/docs/user/manual/en/setting-up/users-and-permissions/user-permissions.md b/erpnext/docs/user/manual/en/setting-up/users-and-permissions/user-permissions.md index 896fd85479..2bf4f3f1a6 100644 --- a/erpnext/docs/user/manual/en/setting-up/users-and-permissions/user-permissions.md +++ b/erpnext/docs/user/manual/en/setting-up/users-and-permissions/user-permissions.md @@ -37,9 +37,9 @@ Another way of allowing documents to be seen that have been restricited by User For example you don't want Assets to be restricited for any user, then select **Asset** in **Customize Form** and in the Company field, check on "Ignore User Permissions" -Ignore User Permissions on specific properties +Ignore User Permissions on specific properties -### Strict Permisssions +### Strict Permissions Since User Permissions are applied via Roles, there may be many users belonging to a particular Role. Suppose you have three users belonging to Role "Accounts User" and you have applied **User Permissions** to only one user, then the permissions will only be restricted to that user.