-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
eabf6d0
commit 472abfc
Showing
1 changed file
with
9 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,12 @@ | ||
# Default Permissions and Workflow | ||
|
||
It's strongly recommended that you set system permissions to limit which users can see and execute a check run. The only permission the application enforces is that a user must have a permission level in ERPNext to create payment entries in order to perform a check run. Additionally, only the first user to access a draft check run doctype can edit it. | ||
|
||
|
||
See the [ERPNext documentation page](https://docs.erpnext.com/docs/v13/user/manual/en/setting-up/users-and-permissions) for more information about user and role permissions. | ||
|
||
TODO: add functionality in settings: | ||
- Only first user in doctype can edit it can be modified in Check Run Settings | ||
- Approval/ Submit Role can be added in Check Run Settings | ||
|
||
- Only first user on doctype can edit. Can be modified in Check Run Settings | ||
- Approval/ Submit Role can be added in Check Run Settings | ||
- | ||
|
||
|
||
|
||
Note that a user must have a permission level in ERPNext to create payment entries in order to perform a check run. please see the permissions. |