TalentAssure
Sign in Candidate register
Knowledge base

FAQ for deployment, admins, recruiters, candidates, and integrations.

Use this page as the operating handbook for the current production rollout. It covers setup, GoDaddy deployment, candidate workflows, approvals, integrations, and common failure points.

Admins

Setup and users

First admin, roles, permissions, and post-deploy checks.

Candidates

Portal journey

Registration, application, documents, expectations, offers, and onboarding.

Operations

Hiring workflow

Requisitions, approvals, screening, interviews, assessments, and offers.

IT

Integrations

SMTP, SMS, WhatsApp, calendar, AI, BGV, storage, webhooks, API, and SSO.

Getting started

How do I log in as an admin?

Open /login and use the admin account created during first-time setup. After login, confirm you can access Dashboard, Jobs, Candidates, Reports, Settings, Users, and Integrations.

How do I create the first real administrator?

Temporarily enable FIRST_RUN_SETUP_ENABLED=true, set a strong FIRST_RUN_SETUP_TOKEN, open /setup/admin?token=YOUR_TOKEN, create the admin, then set FIRST_RUN_SETUP_ENABLED=false.

Should demo data be used in production?

No. Demo data is only for local testing. A fresh production database should start with the production schema, real admins, real approval users, and real requisitions.

Recruitment workflow

Are job codes and candidate codes auto-generated?

Yes. Codes should be generated by the application so users do not manually maintain unique references. If code generation fails, use the production error reference ID to inspect storage/logs/laravel.log.

Can standard approvals work without AI workflows?

Yes. Department or hiring manager approval, talent acquisition approval, and finance approval must work independently. AI workflow mapping is optional and should never block normal requisition approval.

Who needs user accounts for approvals?

Anyone expected to approve inside TalentAssure needs a user account. Typical setup: hiring manager, talent acquisition approver, finance approver, recruitment admin, and backup admin.

Candidate portal

How does a candidate register?

Candidates use /candidate/register. After login they should see candidate-focused pages only: application, expectation alignment, documents, messages, offer review, and onboarding steps assigned to them.

What should the application form support?

The candidate form should support India phone wording, India citizen work authorization, date picker or clear date format, source and notice period “Other” options, dropdowns for country/state/city, save draft, and save-and-continue without 500 errors.

Can candidates delete uploaded files?

They should be able to remove or replace files before a document is locked by verification, approval, offer, or onboarding status. After a status change, deletion should be controlled by admin permissions.

Integrations

When is an integration enabled?

An integration is enabled only when its required environment values are present and the matching feature flag is true. Otherwise it remains configured-but-disabled, needs setup, or manual mode.

How should Brevo SMTP be rolled out?

Configure MAIL_HOST, MAIL_PORT, MAIL_USERNAME, MAIL_PASSWORD, MAIL_ENCRYPTION, MAIL_FROM_ADDRESS, and MAIL_FROM_NAME. Test forgot password first. Then set COMMUNICATION_EMAIL_ENABLED=true only after candidate email templates and consent copy are approved.

Can SMS, WhatsApp, calendar, AI, BGV, API, and SSO be added later?

Yes. Configure one provider at a time in .env, verify Settings > Integrations, test the workflow, and only then expose the automated action to users.

GoDaddy deployment

Which files should I preserve before a fresh upload?

Keep a copy of /public_html/alcodex.in/index.php, /public_html/alcodex.in/.htaccess, the live /home/.../talentassure_app/env file, and anything under private storage that contains candidate uploads.

Why is the storage folder important?

Laravel uses storage for logs, sessions, cached views, private uploads, and generated files. Deleting it can remove uploaded candidate documents and make troubleshooting impossible.

What should I test after deployment?

Open /health, then test public pages, login, forgot password, admin dashboard, job creation, candidate registration, candidate application save, document upload, assessment save, offer builder, and logout.