Differences

This shows you the differences between two versions of the page.

--- user_management [2022/03/07 16:27] – yves
+++ user_management [2023/11/21 16:32] (current) – chris
@@ Line 3: / Line 3: @@
 PMA.core works with user accounts. Users can be marked as "Administrative", in which case they can log into PMA.core directly and administer settings for themselves and for others.
-Users that do not have the "Administrative" flag checked, cannot access PMA.core directly; they interface with [[rootdir|root-directories]] and other PMA.core content via [[https://www.pathomation.com/products|downstream applications]] like [[https://www.pathomation.com/pma.slidebox|PMA.slidebox]], [[https://www.pathomation.com/pma.studio|PMA.studio]], or [[https://www.pathomation.com/pma.control|PMA.control]]. In specific scenarios, you can use these to [[user_service_accounts|emulate service accounts]].
+Users that do not have the "Administrative" flag checked cannot access PMA.core directly; they interface with [[rootdir|root-directories]] and other PMA.core content via [[https://www.pathomation.com/products|downstream applications]] like [[https://www.pathomation.com/pma.slidebox|PMA.slidebox]], [[https://www.pathomation.com/pma.studio|PMA.studio]], or [[https://www.pathomation.com/pma.control|PMA.control]]. In specific scenarios, you can use these to [[user_service_accounts|emulate service accounts]].
-This section discusses how users can be managed within
+This section discusses how users can be managed within PMA.core.
 System users can be managed by selecting the "Users" option from the left menu.
@@ Line 28: / Line 28: @@
 See our [[user_monitoring|separate section on user monitoring]] to for more information on the different parameters.
-==== Tracking ====
+==== Modifying ====
-User activities are tracked in PMA.core, so you can retrospectively find out who look at what slides when.
+Through the user management, you can [[user_config|add, modify and delete user accounts]].
-Similarly, we keep track of what happens with an account itself. This is called audit trailing. It means that we don't only know when you logged into PMA.core, but also when you changed your password or email address.
+We also built in a couple of special features with respect to [[user_config|password management and handling]].
-Scary? Perhaps a little bit. In practice, we find all this surveillance mostly used for troubleshooting and helping users, as in //"we think you had caps lock on when you were trying to log in earlier today"// or "//you didn't get an email because you typed in @pathommation.com instead of @pathomation.com"//.
+==== Tracking ====
-See our [[user_monitoring|separate section on user monitoring]] to for more information on the different parameters.
+User activities are tracked in PMA.core, so you can retrospectively find out who looked at which slides and when.
-==== Manipulation ====
+Similarly, we keep track of what happens with an account itself. This is called audit trailing. It means that you don't only know when a user logged into PMA.core, but also when they changed their password or email address.
-Now that you know that all of your activities are safeguarded through various monitoring mechanisms, we feel it's safe enough to tell you about the account modification options as well.
+Scary? Perhaps a little bit. In practice, all this surveillance is mostly used for troubleshooting and helping users, as in //"we think you had caps lock on when you were trying to log in earlier today"// or "//you didn't get an email because you typed in @patho**mm**ation.com instead of @patho*m*ation.com"//.
-Through the user management, you can add, modify and delete user accounts. We also built in a couple of special features with respect to password management and handling.
+See our [[user_monitoring|separate section on user monitoring]] to for more information on the different parameters.
 ==== External user directories ====
-Are you deploying PMA.core in a large organization? Do your users fluctuate frequently? In that case it's useful to look into our coupling with external user directories, including LDAP and OAuth 2.0 protocols.
+Are you deploying PMA.core in a large organization? Does your userbase fluctuate frequently? In that case it's useful to look into our [[settings_server|coupling with external user directories]], including LDAP and OAuth 2.0 protocols.
-  * The "Last login" column displays each user's last successful login date.
-  * The "Local" column indicates whether or not a user is managed by PMA.core or LDAP.
-  * The "Administrator" column indicates whether or not a user can access PMA.core. Non administrator users cannot perform system management tasks within PMA.core.
-  * The "Can Annotate" column indicates whether or not a user is allowed to create and edit annotations.
-  * The "Suspended" column indicates whether or not a user is currently allowed to login to either PMA.core or downstream applications. A suspended login is treated as invalid by the system.
-  * The "Locked out" column indicates whether or not a user is currently locked out due to consecutive invalid log in attempts.
-  * Clicking on a user's email address launches your default email client.
-  * Clicking on a user's login name displays a summary of the user's activity.
-Next to each entry the following buttons appear:
-{{ :user2.png?nolink&600 |}}
-To add a user click on the "Add" button on the top right of the table.
-{{ :user3.png?nolink&400 |}}
-The following fields can be defined for each user:
-{{ :user4.png?nolink&400 |}}
-{{ :user5.png?nolink&600 |}}