|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
subramanya, the purpose of these two roles are as follows
1) Maker Checker super user: Has checker permissions throughout the system. When maker checker is enabled, every transaction would have two phases, the first being the making (a "maker" creates/updates data...Ex: client creation ) this is later verified (checking) by a user with "checker" privileges.
A Maker Checker super user has checker privileges for all system actions.
2) Reporting super user: A user who has access to all reports in the system
For any user with these two privileges, you would still have to give them permissions ofr other system activities (Ex: they need to do client search, client read permissions need to be provided etc)
Closing off this bug as invalid