...
Expand | |||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||
Key Terms and Concepts
Some system functions require high-level access permission because performing those functions can have system-wide implications. A student should never be granted permission to run any such high-level functions, and should only ever be able to change their own login details, and no one else's details. A student should only ever be assigned an access level of STUDENT ACCESS LEVEL. When the student record is loaded, the access level appears as STUDENT in the Security Group column of the ASSIGNED SECURITY FOR USER LOGIN section. Many records can appear in the list for this student, each with a From Date and a Thru Date for historical records that may have expired. If a student record shows any access level rows for any Security Group other than STUDENT, those rows should be removed.
The current password policy is customised per institution so you will need to contact your "nominated contact person" or other Paradigm experts for details of the current password policy. An example password policy is that a password must contain:
NOTE: Refer to this article on how to Search, Add and Edit Content (e.g. Email Templates) as a Provider. Sample student password reset email template For users who can read HTML, the default email template code is described below. Note that the template uses a number of additional labels that may be edited as a normal label within Paradigm.
The template also includes a form field (
|
...