DOCSecurity model
What the plugin never does, what protects the site and what to trust people with.
Delegating an account is a serious decision. These are the limits the plugin puts around it and the ones that remain yours.
What the plugin never does
Section titled “What the plugin never does”- It never stores passwords and never creates accounts.
- It never opens an account by itself: it only decides whether Moodle’s Log in as may be used.
- It never lets a delegated account open another delegated account: the person must log out first.
What protects the site
Section titled “What protects the site”Administrators are protected
While Protect site administrator accounts is on, administrators cannot be delegated, and a delegation stops working if its account becomes an administrator.
Everything is recorded
Each event is in the site log under both names, and each delegation keeps who created, changed and revoked it.
Limits you set
Maximum delegations per person, maximum duration, no end date allowed or not, and a maximum of records per bulk action.
Access is re-checked
The permission and the delegation are checked on every page, so revoking is immediate.
What to trust people with
Section titled “What to trust people with”Session permissions narrow what a session may do, and the capabilities say who may manage each part.