Security: Difference between revisions
Sturlington (talk | contribs) No edit summary |
Sturlington (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
Sometimes instead of restricting users by action, you may want to restrict by record-level data, specifically [[Configuring Restricted Access by Facility or Geography|by the facility or geographical location]] where the person works. | Sometimes instead of restricting users by action, you may want to restrict by record-level data, specifically [[Configuring Restricted Access by Facility or Geography|by the facility or geographical location]] where the person works. | ||
[[Category:Developer Resources]][[Category:Review2013]] | [[Category:Developer Resources]][[Category:Implementer Resources]][[Category:Review2013]] | ||
Latest revision as of 12:40, 12 November 2013
This documentation reinforces security procedures on iHRIS software. We are currently reviewing and updating this documentation.
iHRIS uses a task- and role-based security mechanism to limit access to various parts of the system. A user is assigned a role, and a role is a collection of tasks that the role can perform. This article describes how roles and tasks are defined in Magic Data and used by the iHRIS system.
This article collects together the various user authentication modules that utilize the pluggable authentication available with version 4.0.3 of the iHRIS Suite.
Sometimes instead of restricting users by action, you may want to restrict by record-level data, specifically by the facility or geographical location where the person works.
