2.1 Overview

This chapter explains how users create an AIUNIFY Assistant account, sign in with an email and password, use Google authentication, maintain a secure browser session, log out, and respond to account-access problems.

The authentication system supports:

The application uses separate public pages for Signup, Login, the Google authentication callback, and deactivated accounts. Operational pages remain protected until the browser contains a valid authenticated session.

Understanding Account Access

2.2 Public Pages

The following pages can be opened without an authenticated session:

Pages such as Dashboard, Leads, AI Agents, Campaigns, Call Logs, Appointments, and Settings require an authenticated account.

When a user attempts to open a protected page without a saved authentication session, AIUNIFY Assistant redirects the browser to Login.

2.3 Standard Account Versus Google Account

AIUNIFY Assistant supports two methods of creating and accessing an account.

Standard account

Uses:

Google account

Uses the user’s approved Google profile and email address.

Both methods create the same type of AIUNIFY Assistant user record. The difference is how the person proves their identity when signing in.

2.4 Account Email

The email address is the account’s primary login identifier.

The system stores account emails in lowercase form and removes unnecessary leading or trailing spaces.

For example:

Use an email address that:

1. Is actively monitored
2. Belongs to the intended account holder
3. Can be recovered securely
4. Will remain available to the business
5. Is not a temporary inbox

2.5 User Role

An account can have one of these general roles:

A separate Super Administrator designation also exists.

The role is assigned by the system or an authorized administrator. The public Signup form does not allow the registrant to choose an administrative role.

The first account created in a completely new installation receives the initial administrative designation. Accounts created after the application has been initialized are assigned the normal user role unless an administrator later changes their access.

2.6 Account Status

The User record contains an activation control:

Active

The user can authenticate and access permitted areas.

Deactivated

The user is blocked from protected pages and directed to the Deactivated Account page.

Account activation is separate from the subscription or plan status.

2.7 Plan Status

An account can also have a plan status such as:

A user may be able to authenticate successfully while a particular operation remains unavailable because an active plan is required.

Examples of messages include:

or a trial-related usage limitation.

Account login status and feature availability should therefore be reviewed separately.

Creating a Standard Account

2.8 Opening Signup

To open the registration form:

1. Visit assistant.poweredbyaiunify.com.
2. Select Signup, Sign Up, or Create Account.
3. Wait for the registration page to load.
4. Confirm that the page displays AIUNIFY Assistant branding.
5. Review the form before entering information.

The page heading is:

The form instructs the user to enter the required details to create the account.

2.9 Registration Fields

The standard Signup form contains:

There is no separate Confirm Password field in the inspected Signup form.

Review the Password carefully before submitting because the form does not ask the user to enter it twice.

2.10 Name

The Name field is required.

The backend accepts a Name between:

Enter the account holder’s recognizable professional name.

Examples:

A personal name is generally recommended when the account belongs to one person.

Use an organization or team name only when the account is intentionally managed as a shared operational identity.

2.11 Email

The Email field is required and must contain a valid email format.

Correct:

Incorrect:

Each email can be associated with only one account.

When the email already exists, the system responds:

Do not create duplicate accounts merely because the original password is unavailable.

2.12 Password

A new standard-account Password must contain at least:

The Signup page displays:

The browser checks the length before sending the registration request, and the backend validates the same minimum.

2.13 Creating a Strong Password

Use a unique password that is not used for another system.

A stronger password combines:

Avoid:

The system’s required minimum is eight characters, but a longer unique password is recommended.

2.14 Submitting Registration

After completing the fields:

1. Review the Name.
2. Review the Email.
3. Confirm that the Password is at least eight characters.
4. Select Sign up once.
5. Wait while the button displays Creating account...
6. Do not refresh during processing.
7. Review any success or error message.

A successful standard registration displays:

The browser saves the new authentication session and directs the user to the Dashboard.

2.15 What Happens After Registration

After successful registration, the system:

1. Confirms that the email is not already registered.
2. Encrypts the Password before storing it.
3. Creates the User record.
4. Assigns the appropriate role.
5. Creates default Settings for the new account.
6. Generates an authentication token.
7. Returns the account information.
8. Saves the session in the browser.
9. Opens the Dashboard.

The plain-text Password is not returned in the account response.

2.16 Default Settings

AIUNIFY Assistant creates a default Settings record for each newly registered account.

The user can later configure:

Creating an account does not automatically complete those operational settings.

2.17 Signup Is Processing

While the registration request is being submitted:

1. The form controls are disabled.
2. The button displays a loading indicator.
3. The button text changes to Creating account...
4. The Google Signup option is temporarily disabled.

Wait for the request to finish before trying again.

2.18 Signup Failed

A general registration failure can display:

The form can also show the more specific backend message.

Before resubmitting:

1. Confirm the internet connection.
2. Confirm the email format.
3. Confirm the Password length.
4. Check whether the email is already registered.
5. Wait for the first request to finish.
6. Avoid repeatedly selecting Sign up.

Registering with Google

2.19 Sign Up with Google

The Signup page contains:

This uses Google authentication rather than creating a separate AIUNIFY Password.

To register:

1. Open Signup.
2. Select Sign up with Google.
3. Wait for Google’s authentication page.
4. Choose the intended Google account.
5. Review the account information being shared.
6. Continue.
7. Wait for AIUNIFY Assistant to complete authentication.
8. Confirm that the correct account opens.

AIUNIFY Assistant requests access to the Google profile and email identity needed for authentication.

2.20 Information Received from Google

The Google authentication process can provide:

AIUNIFY Assistant uses this information to find, link, or create the corresponding account.

The Google password is not provided to AIUNIFY Assistant.

2.21 Existing Google-Linked Account

When the Google profile identifier is already connected to an account, AIUNIFY Assistant signs in to that account.

The system does not create another user record.

2.22 Existing Account with the Same Email

When the Google identifier has not previously been stored, the system checks whether an AIUNIFY Assistant account already uses the same email address.

When the email matches, the system links the Google identity to that existing account.

The user can then access the same account through Google authentication.

This prevents a standard account and Google account with the same email from becoming two separate workspaces.

2.23 New Google Account

When no matching Google identifier or email exists, AIUNIFY Assistant:

1. Creates a new User record.
2. Uses the Google display name.
3. Uses the Google email.
4. Stores the Google identifier.
5. Assigns the appropriate user role.
6. Creates default Settings.
7. Completes authentication.

2.24 Google Authentication Callback

After Google approves the authentication request, the backend returns the user to the AIUNIFY Assistant callback page.

The callback page:

While this is occurring, the page displays:

If the callback information is missing or invalid, the browser returns to Login.

2.25 Google Signup and Google Login Use the Same Process

The Sign up with Google and Log in with Google buttons open the same Google authentication endpoint.

The system decides whether to:

1. Sign in to an existing Google-linked account
2. Link Google to an account with the same email
3. Create a new account

The user does not need to know in advance which operation will occur.

2.26 Choosing the Correct Google Account

When more than one Google account is active in the browser:

1. Review the account chooser carefully.
2. Select the business-approved account.
3. Confirm its email.
4. Do not choose a personal account unintentionally.
5. Verify the AIUNIFY Assistant account email after login.

Using the wrong Google email can create a separate AIUNIFY Assistant account.

2.27 Removing Google Access

Disconnecting AIUNIFY Assistant through Google’s account-security settings may prevent future Google login.

It does not necessarily delete the AIUNIFY Assistant account or its data.

Before removing access:

1. Confirm another approved login method exists.
2. Confirm the account has a usable standard Password where applicable.
3. Contact Support when account recovery is uncertain.

Logging In with Email and Password

2.28 Opening Login

To open the Login page:

1. Visit assistant.poweredbyaiunify.com.
2. Select Login.
3. Confirm the heading Welcome back.
4. Enter the account Email.
5. Enter the Password.
6. Choose the Remember Me setting where appropriate.
7. Select Log in.

The page identifies the workspace as the location for managing campaigns, conversations, and calling operations.

2.29 Email Address

Enter the email associated with the account.

The system validates the email format before processing the login.

Email matching is effectively case-insensitive because account emails are stored in lowercase.

2.30 Password

Enter the exact Password.

Passwords are case-sensitive.

Check:

Do not paste a Password from an untrusted clipboard manager or message.

2.31 Showing or Hiding the Password

The Login page contains an eye control beside the Password field.

Use it to:

1. Temporarily display the entered Password
2. Check for a typing error
3. Hide the Password again before submitting

Do not reveal the Password when another person can view the screen.

2.32 Remember Me

The Login page contains a Remember me checkbox.

The checkbox value is included in the login request. However, the inspected password-login route does not apply a separate token-expiration period based on that checkbox.

Therefore, users should not rely on Remember Me as the only control for session security.

Always log out on:

2.33 Submitting Login

After entering the credentials:

1. Select Log in once.
2. Wait while the button displays Logging in...
3. Do not refresh.
4. Wait for the success message.
5. Confirm the Dashboard opens.

A successful login displays:

2.34 Invalid Email or Password

When either credential is incorrect, the system responds:

For security, the message does not identify whether the email or Password was wrong.

Check both fields before trying again.

2.35 Stale Browser Session Protection

When the Login page opens, the application removes any older locally stored token and user record.

It also removes the earlier session before submitting a new login request.

This prevents an unsuccessful login attempt from reusing a previous person’s saved session.

After a failed login, the current browser should remain unauthenticated rather than reopening an old Dashboard session.

2.36 Browser Session Storage

After successful authentication, the browser stores:

This information allows protected pages to recognize the signed-in account.

Removing browser site data may sign the user out.

Using a different browser or device requires a separate login.

2.37 Password Login Session

The inspected standard password-login route generates an authentication token without a separate user-facing expiration control.

The session can stop working when:

1. The user logs out.
2. Browser storage is cleared.
3. The account is deactivated.
4. The account is deleted.
5. The authentication token becomes invalid.
6. Server security credentials are rotated.
7. The application rejects the token.

Do not assume that closing the browser always ends the session.

Logging In with Google

2.38 Log in with Google

The Login form includes:

To use it:

1. Open Login.
2. Select Log in with Google.
3. Choose the correct Google account.
4. Complete Google authentication.
5. Wait for Completing login...
6. Confirm that the expected AIUNIFY account opens.

2.39 Google Login Duration

The Google authentication route creates a token configured for approximately:

A user may be required to authenticate again after the token expires or becomes invalid.

This does not prevent the user from logging out earlier.

2.40 Google Authentication Failed

When Google authentication fails, AIUNIFY Assistant returns to Login.

The callback can display:

or:

Try:

1. Confirming the correct Google account.
2. Allowing required cookies and redirects.
3. Opening a private browser window.
4. Disabling an interfering privacy extension.
5. Confirming the browser permits Google authentication.
6. Trying again after the first attempt has fully ended.

2.41 Google Returns to the Wrong Domain

A configuration problem may exist when Google authentication returns to:

Record:

1. The address displayed
2. The time
3. The Google account email
4. The page message
5. The browser used

Send the information to Support. Do not publish callback URLs containing authentication information.

Authentication and Protected Pages

2.42 Opening a Protected Page

For each protected page, AIUNIFY Assistant checks whether a token is present in browser storage.

When no token is available, the browser is sent to:

2.43 Current-User Verification

Protected backend requests verify the token and then confirm that the corresponding User record still exists.

When the User no longer exists, the backend responds:

A token by itself is not enough when its related account has been removed.

2.44 Invalid Token

When the token cannot be verified, the system can respond:

Sign out or clear the old browser session, then log in again.

2.45 Expired Token

When an expiring token reaches its end, the system can respond:

Return to Login and authenticate again.

2.46 Authentication Required

When no valid token is supplied to a protected operation, the backend responds:

This can occur when:

1. The user is signed out.
2. Browser storage was cleared.
3. A request was opened from an old tab.
4. A copied API or file link was opened without a session.
5. A browser extension blocked the authentication header.

2.47 Unauthorized Administrative Page

Administrative routes are protected separately.

When the signed-in account is not an Administrator or Super Administrator, the user is redirected to the Dashboard or receives:

Do not attempt to bypass the restriction with a copied administrative URL.

Account Deactivation

2.48 What Deactivation Means

An administrator can set an account to inactive.

When:

the user can no longer access protected AIUNIFY Assistant functions.

The backend responds:

The frontend detects that response and redirects to the Deactivated Account page.

2.49 Deactivated Account Page

The page displays:

and explains that an administrator deactivated the account and platform access is no longer available.

The page contains:

The Support email is retrieved from the application’s public Settings. When that retrieval fails, the interface uses its built-in fallback support address.

2.50 Contacting Support About Deactivation

When the account was unexpectedly deactivated:

1. Select Contact Support.
2. Confirm the recipient email.
3. Provide the account Name.
4. Provide the account Email.
5. Explain when access last worked.
6. Explain whether the account belongs to an organization.
7. Include the exact message.
8. Do not include the Password.
9. Wait for an authorized review.

2.51 Deactivation Versus Plan Restriction

These are different conditions.

Deactivated account

The user cannot access the platform.

Inactive, canceled, or trial plan

The user may be able to log in but certain operations can require an upgrade or active subscription.

Do not report a plan limitation as account deactivation unless the page specifically says Account Deactivated.

2.52 Deactivation Versus Account Deletion

Deactivation does not necessarily delete:

It blocks access while the User record remains present.

2.53 Logging Out from the Deactivated Page

Select Log Out to:

1. Remove the saved token.
2. Remove the saved user record.
3. Return to Login.

This prevents the browser from repeatedly trying to reopen the deactivated session.

Logging Out Normally

2.54 Opening Logout

To log out:

1. Open the account menu in the Header.
2. Confirm the displayed Name and Email.
3. Select Logout.
4. Wait for the success message.
5. Confirm the Login page opens.

2.55 What Logout Removes

The standard Logout action clears:

It then displays:

and sends the browser to Login.

2.56 Logout Does Not Delete Data

Logging out does not delete:

It only ends the saved browser session.

2.57 Closing the Browser Is Not Logout

Because the session is stored in browser storage, closing the tab or browser may not remove the saved authentication information.

Use the visible Logout action on shared or sensitive devices.

2.58 Logging Out of Google

Logging out of AIUNIFY Assistant does not necessarily log the user out of Google.

Likewise, logging out of Google does not automatically guarantee that the AIUNIFY Assistant browser session was removed.

Use both services’ logout controls where appropriate.

Password Recovery and Email Verification

2.59 No Confirmed Self-Service Password Reset

The inspected application source does not contain a customer-facing:

Therefore, a user who cannot remember the Password should contact the authorized platform administrator or Support.

Do not repeatedly create replacement accounts with the same business information.

2.60 Password-Recovery Procedure

When a standard Password is unavailable:

1. Confirm the correct Email.
2. Check whether Google Login is already linked to that email.
3. Try Log in with Google only when the Google account is authorized.
4. Contact Support when access remains unavailable.
5. Provide the account Name and Email.
6. Complete the organization’s identity-verification procedure.
7. Never send an old Password to Support.

2.61 No Confirmed Email-Verification Workflow

The inspected Assistant version does not expose a customer email-verification page or verification-email route.

A successful Signup creates and authenticates the account immediately.

Businesses should still ensure that users register with valid, controlled email addresses. The absence of a verification step means email accuracy must be reviewed carefully.

Troubleshooting Registration

2.62 Name Validation Error

Confirm that the Name:

1. Contains at least two characters
2. Contains no more than 50 characters
3. Is not blank
4. Is not only spaces

2.63 Email Validation Error

Confirm that:

1. The address contains @.
2. The domain is complete.
3. There are no spaces.
4. Only one email is entered.
5. The address has not already been registered.

2.64 Password Too Short

Enter at least eight characters.

The Signup form will not submit a shorter Password.

2.65 User Already Exists

This means the Email is already registered.

Use Login instead.

When appropriate, try Google Login with the same email because the application can link the Google identity to the existing account.

2.66 Signup Returns a Server Error

Try:

1. Waiting before resubmitting.
2. Confirming the API is reachable.
3. Using another browser.
4. Opening a private window.
5. Confirming the Email is not already registered.
6. Contacting Support with the time of the error.

Do not send the Password in the support request.

2.67 Account Was Created but Dashboard Did Not Open

1. Open Login.
2. Enter the newly registered Email and Password.
3. Check for a success message.
4. Try a private window.
5. Confirm the account is not deactivated.
6. Contact Support when the account cannot be found.

Troubleshooting Login

2.68 Login Button Remains on “Logging in...”

1. Wait for the request to finish.
2. Confirm the internet connection.
3. Avoid selecting the button repeatedly.
4. Refresh after confirming no session was created.
5. Try another browser.
6. Check whether the API is available.

2.69 Login Appears Successful but Returns to Login

Possible causes include:

Try a private browser window and confirm that site storage is permitted.

2.70 Login Opens the Wrong Account

This can occur when:

1. The wrong Google account was selected.
2. A different browser profile was used.
3. Several people share the same browser.
4. A previously linked Google identity was chosen.

Log out, reopen Login, and select the correct account.

2.71 Deactivated Message Appears After Login

The Password or Google authentication may have been valid, but the account has been disabled.

Use Contact Support from the Deactivated Account page.

2.72 “Authentication Required” Appears During Work

The saved session may be missing or invalid.

1. Save any unsaved text externally where possible.
2. Return to Login.
3. Authenticate again.
4. Reopen the page.
5. Confirm that the account is active.

2.73 Old Account Information Appears

1. Log out.
2. Close all AIUNIFY Assistant tabs.
3. Clear site storage when authorized.
4. Reopen Login.
5. Authenticate with the intended account.
6. Confirm the Header Name and Email.

Account Security

2.74 One Account Per Authorized User

Create separate accounts for different staff members rather than sharing one login.

Separate accounts improve:

2.75 Never Share Authentication Tokens

Do not copy or send browser authentication information.

Never place a token in:

An authentication token can provide account access without the Password while it remains valid.

2.76 Protect Google Accounts

A Google-linked AIUNIFY account depends on the security of the Google identity.

Enable:

2.77 Review the Account Header

After each login, review the Name and Email displayed in the Header.

Stop before making changes when the wrong account is open.

2.78 Shared Device Procedure

On a shared device:

1. Avoid Remember Me.
2. Use a private browser window where permitted.
3. Do not save the Password.
4. Log out of AIUNIFY Assistant.
5. Log out of Google where used.
6. Close the browser.
7. Confirm the next user does not see the Dashboard.

2.79 Deactivate Former Users

When an employee or contractor should no longer have access, an authorized administrator should deactivate or remove the account promptly.

Changing only shared-resource assignments may not end the person’s login access.

Registration and Login Checklist

2.80 New Account Checklist

Confirm that:

1. Signup opens correctly.
2. The intended Name is entered.
3. The Email is valid.
4. The Email belongs to the intended user.
5. The Password contains at least eight characters.
6. The Password is stored securely.
7. Sign up is selected once.
8. Account creation succeeds.
9. The Dashboard opens.
10. The Header shows the correct Name and Email.
11. Default Settings are available.

2.81 Google Authentication Checklist

Confirm that:

1. The correct Google account is selected.
2. The Google email matches the intended AIUNIFY account.
3. Google displays the expected authorization request.
4. The callback displays Completing login...
5. The success message appears.
6. The correct workspace opens.
7. A duplicate account was not unintentionally created.

2.82 Login Checklist

Confirm that:

1. The correct Email is entered.
2. The Password capitalization is correct.
3. The eye control is used safely.
4. Remember Me is used only on an approved device.
5. Login is selected once.
6. Login successful! appears.
7. The Dashboard opens.
8. The Header shows the expected account.

2.83 Logout Checklist

Confirm that:

1. Logout is selected from the Header.
2. Logged out successfully appears.
3. Login opens.
4. The Dashboard cannot be reopened without authentication.
5. Google is also logged out where required.
6. Shared-device browser windows are closed.

2.84 Account-Status Checklist

Confirm that:

1. The account is active.
2. The account role is correct.
3. Administrative access appears only where authorized.
4. The plan status is understood.
5. A plan restriction is not mistaken for deactivation.
6. Deactivated users contact Support.
7. Former users are promptly disabled.
8. Account deletion is not assumed merely because access was deactivated.

Chapter Completion

At the end of this chapter, the user should understand how to create a standard AIUNIFY Assistant account, register or log in with Google, use the email-and-password Login form, interpret Remember Me, protect the browser session, respond to invalid or expired authentication, identify account deactivation, contact Support, log out securely, and handle the absence of a self-service Password Reset or email-verification workflow.