Start typing to search...
No results for ""
The General Settings panel allows administrators to configure global system behavior, user registration rules, authentication flow, and common application preferences.
These settings control the visibility of utility and help-related links in the admin interface.
When enabled, the following links will be hidden from the interface:
Use case:
Enable this option to keep the interface clean or to prevent users from accessing external help and documentation links.
Currency settings define how monetary values are displayed across the system.
$, ₹, €USD, INRExample Display:
$100This setting allows you to select a default country code.
Use case:
Useful for setting a default dialing code based on your region or target audience.
These settings apply to the [kivicareRegisterLogin] shortcode and control user registration behavior.
Enable registration for the following roles:
Only enabled roles will be able to register using the registration form.
For each enabled role, you can define the default account status after registration:
Use case:
Ideal for scenarios where certain roles (such as Doctors or Receptionists) require verification before gaining access.
This setting enables Google reCAPTCHA protection on the login and registration page generated by the[kivicareRegisterLogin] shortcode.
You can generate these keys from:
👉 https://www.google.com/recaptcha/admin/
Purpose:
Protects the login and registration forms from spam, bots, and automated attacks.
When enabled:
Use case:
Provides a more inclusive gender selection option for users.
These settings control where users are redirected after a successful login, based on their role.
You can define a custom redirect path for:
Example:
/doctor-dashboard
If left empty, the system will use the default redirect behavior.
These settings control where users are redirected after logging out, based on their role.
Available fields:
Use case:
Useful if you want users to land on a specific page such as a login screen, home page, or custom landing page after logout.
When enabled, authorized users can make limited changes even after an encounter has been closed.
Editable fields after encounter closure:
Applicable roles:
When disabled:
Use case:
Enable this option if authorized medical staff need the flexibility to correct or update basic encounter details after the encounter has already been closed.

Start typing to search...
No results for ""