User Management: Difference between revisions

From VoIPmonitor.org
(Add User Restrictions in Database section with SQL queries for users table)
(Fix audit logging menu path, add can_transcribe permission, clarify transcription audit logging)
 
(5 intermediate revisions by the same user not shown)
Line 7: Line 7:
This page covers user account administration in VoIPmonitor GUI, including creating users, assigning permissions, and configuring access controls.
This page covers user account administration in VoIPmonitor GUI, including creating users, assigning permissions, and configuring access controls.


== Accessing User Management ==
'''Navigate to:''' '''Users & Audit > Users''' to manage user accounts.


Navigate to '''Users & Audit > Users''' in the GUI to manage user accounts.
== User Authentication Types ==


== User Types ==
<kroki lang="mermaid">
%%{init: {'flowchart': {'nodeSpacing': 15, 'rankSpacing': 30}}}%%
flowchart LR
    U[User Login] --> L{Auth Type?}
    L -->|Local| DB[(VoIPmonitor DB)]
    L -->|External| CS[custom_login.php]
    CS --> LDAP[LDAP/AD]
    CS --> OTHER[Other Systems]
    DB --> GUI[GUI Access]
    LDAP --> GUI
    OTHER --> GUI
</kroki>


=== Local Users ===
{| class="wikitable"
*  Default authentication method using VoIPmonitor's internal database.
|-
*  Passwords are stored securely (hashed).
! Type !! Description !! Configuration
*  Created and managed directly in the GUI.
|-
| '''Local''' || Default authentication using VoIPmonitor's internal database. Passwords stored as hashes. || Manage directly in GUI.
|-
| '''External (LDAP/Custom)''' || Integrate with LDAP/Active Directory via custom login script. || See [[WEB_API#Custom_Login|Custom Login (LDAP)]].
|-
| '''Google SSO''' || OAuth authentication with Google accounts. || See [[Google_Sign_in_usage|Google Sign-In]].
|-
| '''Microsoft SSO''' || OAuth authentication with Microsoft Entra ID (Azure AD). ''Currently in development.'' || See [[Microsoft_Sign_in_usage|Microsoft Sign-In]].
|}


=== External Authentication (LDAP/Custom Login) ===
{{Note|1=For external authentication, the <code>custom_login</code> function '''must''' return a unique numeric <code>id</code> for each user. Shared IDs cause users to share settings.}}
*  Integrate with LDAP/Active Directory using the custom login script.
*  See [[WEB_API#Custom_Login|Custom Login (LDAP)]] for configuration details.
*  '''Important:''' The <code>custom_login</code> function must return a unique numeric <code>id</code> for each user.


== Creating a New User ==
== Creating a New User ==
Line 35: Line 51:
# Click '''Save'''.
# Click '''Save'''.


== User Permissions ==
== Permissions ==


Permissions control what users can access and modify. Set permissions via:
Permissions control what users can access and modify. Set via:
*  '''User-level:''' Direct assignment on individual user.
*  '''User-level:''' Direct assignment on individual user.
*  '''Group-level:''' Inherited from assigned group (recommended for easier management).
*  '''Group-level:''' Inherited from assigned group (recommended for easier management).
Line 47: Line 63:
! Permission !! Description
! Permission !! Description
|-
|-
| <code>is_admin</code> || Full administrative access
| <code>is_admin</code> || Full administrative access (includes upgrade permissions)
|-
|-
| <code>can_cdr</code> || View CDR records
| <code>can_cdr</code> || View CDR records and filter form (required for Call-ID search)
|-
|-
| <code>can_play_audio</code> || Play call recordings in GUI
| <code>can_play_audio</code> || Play call recordings in GUI
Line 78: Line 94:
|-
|-
| <code>can_sensors_operations</code> || Sensor management
| <code>can_sensors_operations</code> || Sensor management
|-
| <code>can_transcribe</code> || Use on-demand transcription (Whisper) on call recordings
|}
|}


{{Tip|Set <code>is_admin</code> to <code>false</code> and use group permissions for granular access control.}}
{{Tip|1=Set <code>is_admin</code> to <code>false</code> and use group permissions for granular access control.}}
 
=== Upgrade Permissions ===
 
Only users with <code>is_admin</code> role can perform:
*  '''GUI upgrades''' via Settings > System > Upgrade
*  '''Sensor upgrades''' via Settings > Sensors
*  '''Auto-upgrade controls'''
 
{{Warning|There is no option to hide the upgrade menu for admin users. To restrict upgrades, control access to admin accounts or use CLI: <code>php php/run.php upgrade -f</code>.}}


== Sensor Access Restrictions ==
== Access Restrictions ==
 
=== Sensor Restrictions ===


Restrict users to specific sensors:
Restrict users to specific sensors:
Line 89: Line 118:
# Users will only see CDR from permitted sensors.
# Users will only see CDR from permitted sensors.


== IP-Based Access Control ==
=== IP-Based Login Restrictions ===


Restrict login to specific IP addresses:
Restrict login to specific IP addresses:
Line 98: Line 127:
{{Warning|If you lock yourself out, you must access the database directly to remove IP restrictions.}}
{{Warning|If you lock yourself out, you must access the database directly to remove IP restrictions.}}


== Microsoft Sign-In Integration ==
=== CDR Data Restrictions ===


{{Note|This feature is currently in development and not available in stable releases.}}
Restrict which CDR data users can view based on phone numbers, IP addresses, or domains:


For SSO with Microsoft Entra ID (Azure AD):
# Edit user or group > '''restrictions''' tab.
# Edit user > '''Secure users''' tab.
# Add filter criteria.
# Enter '''Microsoft Sign In emails''' to map the user.
# Configure boolean logic (see below).
# See [[Microsoft_Sign_in_usage]] for full setup instructions.
 
{{Note|The '''restrictions''' tab filters CDR query results. The '''Secure users''' tab controls login IP addresses. These are different functions.}}


== Audit Logging ==
==== AND vs OR Logic ====


Track user actions for compliance (GDPR, HIPAA):
By default, '''AND logic''' is used: CDR must match ALL conditions.
*  '''GUI Audit:''' Enabled by default in '''Users & Audit > Audit'''.
*  '''File-based Audit:''' Configure <code>AUDIT_LOG_FILE</code> in <code>configuration.php</code>.
*  '''Per-user Audit Mode:''' Set '''Enable audit''' to ''auto'' or ''yes'' on individual users.


See [[GUI_Configuration_PHP#Audit_Log_Settings|Audit Log Configuration]] for details.
To enable '''OR logic''' (match ANY condition):
# In the '''restrictions''' tab, scroll to bottom.
# Check '''OR condition''' checkbox.
# Save changes.


== User Groups ==
== User Groups ==
Line 122: Line 152:
*  Assign users to groups for consistent access control.
*  Assign users to groups for consistent access control.
*  Changes to group permissions apply to all members.
*  Changes to group permissions apply to all members.
== Audit Logging ==
Track user actions for compliance (GDPR, HIPAA). All sensitive GUI actions are logged, including on-demand transcription requests.
{| class="wikitable"
|-
! Method !! Configuration
|-
| '''GUI Audit''' || Enabled by default. View logs in '''Users & Audit > Audit'''. Configure per-user settings in '''Users & Audit > Users/Groups'''.
|-
| '''File-based Audit''' || Set <code>AUDIT_LOG_FILE</code> in <code>configuration.php</code>.
|-
| '''Per-user Audit''' || Set '''Enable audit''' to ''auto'' or ''yes'' on individual users.
|}


== Troubleshooting ==
== Troubleshooting ==


=== User Cannot Log In ===
=== User Cannot Log In ===
*  Check IP restrictions in '''Secure users''' tab.
*  Check IP restrictions in '''Secure users''' tab.
*  Verify username/password (case-sensitive).
*  Verify username/password (case-sensitive).
*  Check if account is disabled.
*  Check if account is disabled.
*  For LDAP: Test connection with <code>php scripts/custom_login.php</code>.
*  For LDAP: Test with <code>php scripts/custom_login.php</code>.


=== Permission Changes Not Taking Effect ===
=== Permission Changes Not Taking Effect ===
*  User must log out and log back in.
*  User must log out and log back in.
*  Clear browser cache if issues persist.
*  Clear browser cache if issues persist.
*  Verify group membership if using group permissions.
*  Verify group membership if using group permissions.


=== Dashboard Graphs Empty for Restricted Group Users ===
=== Empty Dashboard Graphs for Restricted Users ===


'''Symptom:''' A user assigned to a restricted group can access the VoIPmonitor GUI and load the Dashboard, but the graphs appear empty (no data points), whereas an unrestricted admin sees data correctly.
'''Symptom:''' User sees empty graphs while admin sees data correctly.


'''Root Cause:''' The user's group has IP address restrictions configured that prevent access to the required data sources. When a group is restricted to specific IP addresses, only CDR data matching those IPs are displayed in graphs and dashboards.
'''Cause:''' Group IP restrictions filter out required data sources.


'''Solution:'''
'''Solution:'''
# Navigate to '''Users & Audit > Groups'''.
# Edit the affected group > '''restrictions''' tab.
# Adjust or remove IP restrictions.
# User must refresh browser.


# Navigate to '''Users & Audit > Groups'''.
{{Tip|To verify: temporarily clear all group restrictions. If graphs appear, restrictions were blocking data.}}
# Edit the affected user group.
 
# Click the '''restrictions''' tab.
=== Cannot Search by Call ID ===
# Remove or adjust the IP address restrictions to allow access to the required data sources.
# Save the changes.
# Have the affected user refresh their browser to see updated data.


{{Tip|To verify if restrictions are causing the issue, temporarily clear all restrictions in the group and check if graphs appear. If graphs show data after clearing restrictions, the IP restrictions were blocking access.}}
'''Cause:''' Missing <code>can_cdr</code> permission.


{{Note|Group-level IP restrictions are different from user-level IP restrictions. Group restrictions filter which CDR data the user can view, while user-level restrictions (in the Secure users tab) control which IP addresses can log in.}}
'''Solution:''' Enable '''Allow to view CDR''' checkbox on user profile, then have user re-login.


=== Forgot Admin Password ===
=== Forgot Admin Password ===
Reset password via database:
 
Reset via database:
 
<syntaxhighlight lang="sql">
<syntaxhighlight lang="sql">
UPDATE users SET password = MD5('newpassword') WHERE username = 'admin';
UPDATE users SET password = MD5('newpassword') WHERE username = 'admin';
</syntaxhighlight>
</syntaxhighlight>


{{Warning|This sets an MD5 hash. For better security, log in immediately and change the password through the GUI.}}
{{Warning|Log in immediately and change password through GUI for better security.}}


=== Different Search Results Between Users With Identical Permissions ===
=== Different Search Results Between Users ===


'''Symptom:''' Two users with the same GUI permissions see different results when searching for calls in the CDR view. One user can find calls with a specific filter, while the other cannot.
Even with identical permissions, users may see different results due to:


'''Root Cause:''' Multiple factors can cause this behavior, even when users have identical permission flags.
# '''Timezone setting:''' Compare timezone selector (top right of CDR view) between users.
# '''User restrictions:''' Check '''restrictions''' tab for IP/number filters.
# '''Sensor restrictions:''' Check '''Basic data''' > '''Enable sensors'''.
# '''Group restrictions:''' Verify group settings in '''Users & Audit > Groups'''.


'''Troubleshooting Steps:'''
== Advanced: Database-Level Operations ==


'''1. Check Per-User Timezone Setting:'''
User restriction filters are stored in the <code>users</code> table, <code>number</code> column.
The timezone selector in the CDR view is user-specific and affects how date-based filters (e.g., "Today", "Last 7 Days") are translated into database queries.
* Navigate to the CDR List view.
* Compare the timezone setting in the top right corner for both users (see [[Call_Detail_Record_-_CDR#Timezone_Display_Setting|CDR Timezone Display Setting]]).
* If timezones differ, both users may be querying different time ranges despite using the same filter criteria.
 
'''2. Review User Restrictions:'''
Check for per-user restrictions that filter which CDR data is visible.
# Navigate to '''Users & Audit > Users'''.
# Click '''edit user''' for the affected user.
# Check the following tabs for restrictions:
#* '''Basic data tab''' - Review "Enable sensors" setting. Users with different sensor access will see different CDR data.
#* '''restrictions tab''' - Check if the user has IP address or other restrictions configured that filter CDR results.
 
'''3. Check Group Restrictions:'''
If users are members of the same group, verify that both users are getting the expected restrictions.
# Navigate to '''Users & Audit > Groups'''.
# Edit the group and check the '''restrictions''' tab.
# Ensure the group restrictions are appropriate for all users comparing results.
 
{{Tip|The restrictions tab on users and groups controls which CDR data is filtered in queries. This is different from the Secure users tab, which only controls which IP addresses are allowed to log in.}}
 
== User Restrictions in Database ==
 
User restriction filters (configured in the GUI) are stored in the <code>users</code> table in the database. These filters control which CDR data users can view based on phone numbers, IP addresses, and other criteria.
 
=== Viewing User Restrictions ===
 
To view all user restriction filters configured in the system:


<syntaxhighlight lang="sql">
<syntaxhighlight lang="sql">
-- View all user restrictions
SELECT username, number FROM users;
SELECT username, number FROM users;
</syntaxhighlight>


The <code>number</code> column contains the user restriction filters as configured in the GUI.
-- Find restrictions with specific pattern (escape backslashes)
 
SELECT username, number FROM users WHERE number LIKE '%\\\\*%';
=== Finding Specific Patterns in User Restrictions ===
 
To find user restrictions matching a specific pattern, use SQL <code>LIKE</code> queries:


<syntaxhighlight lang="sql">
-- Update restrictions
-- Example: Find restrictions containing an asterisk character
UPDATE users SET number = '<filter>' WHERE username = 'username';
SELECT username, number FROM users WHERE number LIKE '%\\\\*%';
</syntaxhighlight>
</syntaxhighlight>


{{Note|1=<strong>SQL Escaping Note:</strong> When searching for special characters in the <code>number</code> column, backslashes must be properly escaped. In the example above, <code>\\\\</code> represents a single literal backslash in the LIKE clause pattern. This is required because the backslash needs to be escaped for both the SQL string literal and the LIKE pattern.}}
{{Warning|Direct database changes bypass GUI validation. Test in non-production first. Users must re-login after changes.}}
 
=== Updating User Restrictions ===
 
You can update user restrictions directly via SQL:


<syntaxhighlight lang="sql">
== See Also ==
UPDATE users SET number = '<your_filter_here>' WHERE username = 'username';
</syntaxhighlight>


{{Warning|Direct database changes bypass GUI validation. Always test in a non-production environment first.}}
* [[WEB_API#Custom_Login|Custom Login (LDAP)]]
* [[Google_Sign_in_usage|Google Sign-In Integration]]
* [[Microsoft_Sign_in_usage|Microsoft Sign-In Integration]]
* [[Call_Detail_Record_-_CDR|CDR View Documentation]]


{{Tip|After modifying user restrictions via SQL, users must log out and log back in for changes to take effect.}}


== AI Summary for RAG ==
== AI Summary for RAG ==


'''Summary:''' Guide to VoIPmonitor user management. Covers creating local users, LDAP/custom authentication integration (requires unique numeric ID per user), permission flags (can_cdr, can_play_audio, can_download_audio, can_pcap, can_reports_edit, can_alerts_edit, is_admin, etc.), sensor access restrictions (limit users to specific sensor IDs), IP-based access control (Secure users tab), Microsoft Sign-In SSO integration (development feature), audit logging configuration, and user groups for permission templates. Troubleshooting includes IP restrictions, LDAP testing, groups restrictions tab for empty dashboard graphs, and admin password reset via database.
'''Summary:''' Guide to VoIPmonitor user management covering local users and LDAP/custom authentication (requires unique numeric ID per user), permission flags (can_cdr, can_play_audio, can_pcap, is_admin, etc.), upgrade permissions (only is_admin role users can perform GUI/sensor upgrades via web interface, no option to hide upgrade menu for admin users), sensor access restrictions (Basic data tab), IP-based login control (Secure users tab), CDR data restrictions (restrictions tab with AND/OR logic), Google and Microsoft SSO integration, audit logging, and user groups. Troubleshooting covers login issues, empty dashboard graphs for restricted groups, can_cdr permission for Call ID search, different search results between users (timezone, restrictions), and admin password reset via database.


'''Keywords:''' user management, users, permissions, access control, LDAP, custom login, authentication, sensor restrictions, IP restrictions, audit log, user groups, password reset, Microsoft Sign-In, SSO, can_cdr, can_pcap, is_admin, groups restrictions tab, restricted group, empty dashboard graphs, dashboard empty, graphs not showing, group IP restrictions, users table, user restrictions, number column, user restriction filters, database user management
'''Keywords:''' user management, permissions, access control, LDAP, custom login, sensor restrictions, IP restrictions, CDR restrictions, restrictions tab, OR condition, AND logic, audit log, user groups, password reset, Google Sign-In, Microsoft Sign-In, SSO, can_cdr, is_admin, empty dashboard graphs, group restrictions, users table, Call ID search, upgrade permissions, admin upgrade, GUI upgrade, sensor upgrade, timezone


'''Key Questions:'''
'''Key Questions:'''
Line 243: Line 260:
* How do I reset the admin password in VoIPmonitor?
* How do I reset the admin password in VoIPmonitor?
* How do I restrict user login by IP address?
* How do I restrict user login by IP address?
* How do I enable audit logging for user actions?
* How do I set up user groups with shared permissions?
* How do I set up user groups with shared permissions?
* Why can't a user log in to VoIPmonitor?
* How do I configure Microsoft Sign-In for VoIPmonitor users?
* Why are dashboard graphs empty for a restricted group user?
* Why are dashboard graphs empty for a restricted group user?
* How do I fix empty graphs for users in a restricted group?
* How do I configure OR logic between user restrictions?
* Where is the restrictions tab for user groups?
* Why can't a user search by Call ID in the CDR view?
* How do I view user restriction filters in the database?
* What permission is required for CDR view access?
* Which table stores user restriction filters in VoIPmonitor?
* Who can perform upgrades in the VoIPmonitor GUI?
* How do I find user restrictions containing specific patterns?
* Why do two users with same permissions see different search results?
* How do I query the users table in VoIPmonitor database?
* How do I update user restrictions via SQL?
* What columns are in the users table for VoIPmonitor?

Latest revision as of 16:35, 13 January 2026


User Management

This page covers user account administration in VoIPmonitor GUI, including creating users, assigning permissions, and configuring access controls.

Navigate to: Users & Audit > Users to manage user accounts.

User Authentication Types

Type Description Configuration
Local Default authentication using VoIPmonitor's internal database. Passwords stored as hashes. Manage directly in GUI.
External (LDAP/Custom) Integrate with LDAP/Active Directory via custom login script. See Custom Login (LDAP).
Google SSO OAuth authentication with Google accounts. See Google Sign-In.
Microsoft SSO OAuth authentication with Microsoft Entra ID (Azure AD). Currently in development. See Microsoft Sign-In.

ℹ️ Note: For external authentication, the custom_login function must return a unique numeric id for each user. Shared IDs cause users to share settings.

Creating a New User

  1. Go to Users & Audit > Users.
  2. Click Add user.
  3. Fill in required fields:
    • Username - Login name (must be unique).
    • Password - Strong password recommended.
    • Email - For alerts and password recovery.
    • Group - Assign to a permission group.
  4. Configure permissions (see below).
  5. Click Save.

Permissions

Permissions control what users can access and modify. Set via:

  • User-level: Direct assignment on individual user.
  • Group-level: Inherited from assigned group (recommended for easier management).

Permission Flags

Permission Description
is_admin Full administrative access (includes upgrade permissions)
can_cdr View CDR records and filter form (required for Call-ID search)
can_play_audio Play call recordings in GUI
can_download_audio Download audio files
can_listen_active_call Live call monitoring (ChunkPlayer)
can_pcap Download PCAP files
can_messages View SIP messages
can_graphs Access graphs and charts
can_livesniffer Live sniffer functionality
can_capture_rules Manage capture rules
can_reports_edit Create/edit reports
can_alerts_edit Create/edit alerts
can_dashboard View dashboards
can_ipacc IP accounting features
can_audit View audit logs
can_sensors_operations Sensor management
can_transcribe Use on-demand transcription (Whisper) on call recordings

💡 Tip: Set is_admin to false and use group permissions for granular access control.

Upgrade Permissions

Only users with is_admin role can perform:

  • GUI upgrades via Settings > System > Upgrade
  • Sensor upgrades via Settings > Sensors
  • Auto-upgrade controls

⚠️ Warning: There is no option to hide the upgrade menu for admin users. To restrict upgrades, control access to admin accounts or use CLI: php php/run.php upgrade -f.

Access Restrictions

Sensor Restrictions

Restrict users to specific sensors:

  1. Edit user > Basic data tab.
  2. In Enable sensors, select allowed sensor IDs.
  3. Users will only see CDR from permitted sensors.

IP-Based Login Restrictions

Restrict login to specific IP addresses:

  1. Edit user > Secure users tab.
  2. Enable Enable remote addresses.
  3. Add allowed IP addresses/ranges.

⚠️ Warning: If you lock yourself out, you must access the database directly to remove IP restrictions.

CDR Data Restrictions

Restrict which CDR data users can view based on phone numbers, IP addresses, or domains:

  1. Edit user or group > restrictions tab.
  2. Add filter criteria.
  3. Configure boolean logic (see below).

ℹ️ Note: The restrictions tab filters CDR query results. The Secure users tab controls login IP addresses. These are different functions.

AND vs OR Logic

By default, AND logic is used: CDR must match ALL conditions.

To enable OR logic (match ANY condition):

  1. In the restrictions tab, scroll to bottom.
  2. Check OR condition checkbox.
  3. Save changes.

User Groups

Manage groups in Users & Audit > Groups:

  • Define permission templates for multiple users.
  • Assign users to groups for consistent access control.
  • Changes to group permissions apply to all members.

Audit Logging

Track user actions for compliance (GDPR, HIPAA). All sensitive GUI actions are logged, including on-demand transcription requests.

Method Configuration
GUI Audit Enabled by default. View logs in Users & Audit > Audit. Configure per-user settings in Users & Audit > Users/Groups.
File-based Audit Set AUDIT_LOG_FILE in configuration.php.
Per-user Audit Set Enable audit to auto or yes on individual users.

Troubleshooting

User Cannot Log In

  • Check IP restrictions in Secure users tab.
  • Verify username/password (case-sensitive).
  • Check if account is disabled.
  • For LDAP: Test with php scripts/custom_login.php.

Permission Changes Not Taking Effect

  • User must log out and log back in.
  • Clear browser cache if issues persist.
  • Verify group membership if using group permissions.

Empty Dashboard Graphs for Restricted Users

Symptom: User sees empty graphs while admin sees data correctly.

Cause: Group IP restrictions filter out required data sources.

Solution:

  1. Navigate to Users & Audit > Groups.
  2. Edit the affected group > restrictions tab.
  3. Adjust or remove IP restrictions.
  4. User must refresh browser.

💡 Tip: To verify: temporarily clear all group restrictions. If graphs appear, restrictions were blocking data.

Cannot Search by Call ID

Cause: Missing can_cdr permission.

Solution: Enable Allow to view CDR checkbox on user profile, then have user re-login.

Forgot Admin Password

Reset via database: 

UPDATE users SET password = MD5('newpassword') WHERE username = 'admin';

⚠️ Warning: Log in immediately and change password through GUI for better security.

Different Search Results Between Users

Even with identical permissions, users may see different results due to:

  1. Timezone setting: Compare timezone selector (top right of CDR view) between users.
  2. User restrictions: Check restrictions tab for IP/number filters.
  3. Sensor restrictions: Check Basic data > Enable sensors.
  4. Group restrictions: Verify group settings in Users & Audit > Groups.

Advanced: Database-Level Operations

User restriction filters are stored in the users table, number column. 

-- View all user restrictions
SELECT username, number FROM users;

-- Find restrictions with specific pattern (escape backslashes)
SELECT username, number FROM users WHERE number LIKE '%\\\\*%';

-- Update restrictions
UPDATE users SET number = '<filter>' WHERE username = 'username';

⚠️ Warning: Direct database changes bypass GUI validation. Test in non-production first. Users must re-login after changes.

See Also


AI Summary for RAG

Summary: Guide to VoIPmonitor user management covering local users and LDAP/custom authentication (requires unique numeric ID per user), permission flags (can_cdr, can_play_audio, can_pcap, is_admin, etc.), upgrade permissions (only is_admin role users can perform GUI/sensor upgrades via web interface, no option to hide upgrade menu for admin users), sensor access restrictions (Basic data tab), IP-based login control (Secure users tab), CDR data restrictions (restrictions tab with AND/OR logic), Google and Microsoft SSO integration, audit logging, and user groups. Troubleshooting covers login issues, empty dashboard graphs for restricted groups, can_cdr permission for Call ID search, different search results between users (timezone, restrictions), and admin password reset via database.

Keywords: user management, permissions, access control, LDAP, custom login, sensor restrictions, IP restrictions, CDR restrictions, restrictions tab, OR condition, AND logic, audit log, user groups, password reset, Google Sign-In, Microsoft Sign-In, SSO, can_cdr, is_admin, empty dashboard graphs, group restrictions, users table, Call ID search, upgrade permissions, admin upgrade, GUI upgrade, sensor upgrade, timezone

Key Questions:

  • How do I create a new user in VoIPmonitor?
  • How do I restrict a user to specific sensors?
  • How do I configure LDAP authentication for VoIPmonitor?
  • What permissions are available for VoIPmonitor users?
  • How do I reset the admin password in VoIPmonitor?
  • How do I restrict user login by IP address?
  • How do I set up user groups with shared permissions?
  • Why are dashboard graphs empty for a restricted group user?
  • How do I configure OR logic between user restrictions?
  • Why can't a user search by Call ID in the CDR view?
  • What permission is required for CDR view access?
  • Who can perform upgrades in the VoIPmonitor GUI?
  • Why do two users with same permissions see different search results?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=User_Management&oldid=10687"