This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
pergamonmystic:linkedhelp:authentication [2021/07/31 09:03] admin |
pergamonmystic:linkedhelp:authentication [2021/07/31 09:10] admin |
||
---|---|---|---|
Line 7: | Line 7: | ||
* Users | * Users | ||
* Readers | * Readers | ||
+ | |||
+ | Logging in however, is performed using the same authentication form on the splash page of the Mystic application. This authentication form can be [[PergamonMystic:linkedhelp:startingmystic|configured]] to a limited extent. | ||
===== Users ===== | ===== Users ===== | ||
Line 42: | Line 44: | ||
==== Security Authorisation ==== | ==== Security Authorisation ==== | ||
- | Security Authorisations are required when additional security has been enabled on a particular feature of Mystic, such as the User Manager or Lookup Manager. In this case, when selecting the function Mystic will ask for the current user's login name and password a second time to ensure that the workstation has not simply been left unattended. | + | Security Authorisations are required when additional security has been enabled on a particular feature of Mystic, such as the User Manager or Lookup Manager. In this case, when selecting the function Mystic will ask for the current user's login name and password a second time to ensure that the workstation has not simply been left unattended. |
- | * Authorisation Overrides | + | |
+ | ==== Authorisation Overrides ==== | ||
+ | If a user attempts to perform an operation and it is refused (e.g. trying to issue an item which breaches current rules, such as too many items), it is sometimes possible to override the restriction. In this case, Mystic will ask for the username and password of a suitably authorised administrative users to allow the operation to proceed. | ||
---- | ---- |