34.1 Settings Overview

AIUNIFY Leads separates several types of configuration so users can manage their own Profile, organization-level Company information, Email configuration, and AI configuration independently.

These should also be distinguished from Website Settings, which control website-specific and language-specific public information documented earlier in this manual.

34.2 Profile Settings

The authenticated Settings router includes a dedicated Profile area.

The Profile route requires authentication but does not declare the additional Company, Email, Roles, or AI permission used by those other Settings sections.

Use Profile for the signed-in user's personal account settings exposed by that screen.

Distinction: Profile Settings belong to the user account. Website Settings belong to a selected Website and Website Language.

34.3 Company Settings

The Settings router includes a separate Company area.

Access is protected by:

companies_edit

Company settings affect organization/workspace configuration and should be changed only by users responsible for company-level settings.

34.4 Company Settings vs Website Settings

Area Scope
Profile The signed-in user's account.
Company Settings Company/workspace-level configuration.
Website Settings The selected Website and selected Website Language.
AI Settings AI provider/configuration used by supported AI functions.
Email Settings Mail configuration used by supported application email functions.

34.5 Email Settings Access

Email settings are protected by the email_edit permission in the Settings router.

The confirmed Email operations include:

  1. Retrieving current Email Settings.
  2. Updating Email Settings where available for the deployment mode.
  3. Managing Send Mail Settings.
  4. Sending a Test Email.

34.6 Sending a Test Email

The Email settings interface includes a Send Test Mail workflow for supported Mail or SMTP drivers.

The Test Mail form requires a valid Email address.

The test button can remain disabled until the applicable Email configuration has been verified.

34.7 When to Test Email

Send a Test Email after changes to mail configuration and before relying on the system for operational messages.

Testing is particularly useful after changes involving:

  1. Mail driver configuration.
  2. SMTP configuration.
  3. Application mail credentials.
  4. Other supported Email Settings.

34.8 AI Settings Access

AI Settings are protected by:

ai_settings_edit

The confirmed AI Settings operations include:

  1. Retrieving current AI Settings.
  2. Updating AI Settings.
  3. Testing the AI connection.

34.9 Test the AI Connection

After changing AI configuration, use the supported connection test before attempting to use AI Website generation tools.

A successful Settings save by itself does not replace testing whether the configured AI connection can actually be used.

34.10 AI Settings Permission vs AI Feature Permission

Two different permission concepts are involved:

Permission Purpose
ai_settings_edit Allows access to the AI configuration Settings area.
ai_features_access Allows use of supported AI generation features when their other requirements are satisfied.

A Staff Member may therefore be permitted to use configured AI tools without being permitted to change the underlying AI Settings.

34.11 Additional AI Requirements

Individual AI Website tools can also require:

  1. The AI feature to be enabled.
  2. A valid AI configuration.
  3. The required feature-specific permission.
  4. A selected Website.
  5. Website Languages where required.
  6. Website Pages where required by the generation workflow.

34.12 AI Configuration Error

If AI functionality is called without the required configuration, the confirmed message includes:

AI is not configured. Please configure AI settings first.

34.13 Email Templates

The Settings router also contains an Email Templates area under the email_edit permission.

Email templates should be edited only by personnel responsible for application communications.

34.14 Administrative Maintenance Settings

The application source also contains technical maintenance areas such as application updates, modules, storage, database backups, translations, and other system-level configuration.

Those maintenance functions are not part of the normal AIUNIFY Leads end-user operating workflow covered by this manual and should be reserved for appropriately authorized administrators.

34.15 Recommended Settings Procedure

  1. Identify whether the change belongs to Profile, Company, Website, Email, or AI Settings.
  2. Verify the current user has the required permission.
  3. Make only the intended change.
  4. Save the configuration.
  5. Use Send Test Mail after relevant Email changes.
  6. Use Test Connection after relevant AI changes.
  7. Verify the affected operational feature after the test succeeds.
Write Your Comment