Frequently asked questions

Yes. A signed-in user can build a portfolio containing a professional profile, skills, experience, projects, education, certifications, and custom sections. New portfolios are private until you explicitly publish them.

Yes. You can create a portfolio from one of your own resumes or import a resume into an existing portfolio. The import copies supported fields once; future portfolio and resume edits remain independent.

No. Public visibility and search indexing are separate controls. You can publish a link-only portfolio while keeping indexing disabled, or explicitly allow indexing when you want broader discoverability.

Yes. The current release includes Emerald, Minimal, and Midnight presentation themes without changing your stored portfolio content.

Use Template Finder when you are unsure. It considers application type, industry, career level, ATS strength, company fit, and visual preference. For heavily automated hiring portals, simpler ATS-focused layouts are generally the safest starting point.

Yes. Resume content is stored separately from the visual template, so you can change designs without re-entering your information.

Yes. Open the PDF / Print view and use your browser’s print dialog to save the resume as a PDF.

No. ATS-oriented layouts are designed for readability and conventional parsing, but employers use different systems and hiring criteria. Always review the actual job requirements and the exported document.

Yes. Signed-in users can create private work letters including resignation notices, leave requests, job application and cover letters, offer responses, promotion or compensation requests, transfer requests, employment verification requests, recommendation requests, workplace explanations, grievances, apologies, and custom professional letters. Every generated draft remains editable before printing or sending.

No. Work letters are private account documents and do not receive public share links. You choose when to preview, print, save as PDF, or send the final letter.

No. Generated drafts are starting points. Verify names, dates, company policy, contractual obligations, notice periods, and any legal or HR requirements that apply to your situation before sending.

No. New resumes are private by default. A public resume becomes available only when you explicitly enable its share link.

Review phone numbers, personal email addresses, home or precise locations, references, private project links, and any information you would not want redistributed. Anyone with a public link may be able to copy or capture the page.

The current implementation can record the resume viewed, view time, a privacy-preserving visitor hash, and referring site origin. It intentionally does not retain the visitor User-Agent in public-resume analytics.

Yes, when those providers are configured by the deployment operator. New social sign-up can also be disabled independently by an administrator.

The application uses provider tokens during the authentication exchange but does not persist them in its account database.

Yes. TOTP authenticator apps and one-time recovery codes are supported. Production deployments can require 2FA for platform administrators.

Sensitive account operations can require a fresh authentication session. This reduces the risk of a stale browser session changing security credentials.

When enabled by the operator, Workfolio sends a single-use verification link to the account email. Opening the link does not immediately consume it; you confirm verification on the Workfolio page so automated email scanners do not use the token for you.

When password recovery is enabled, use Forgot password on the sign-in page. Workfolio returns the same message whether an account exists or not, and reset links are single-use and time-limited. A successful reset signs out existing sessions.

Yes. Account settings lists registered browser sessions using coarse device labels. You can revoke one active session or sign out all devices. Network addresses are stored only as privacy-preserving hashes for these session records.

Account settings provides a portable JSON export that excludes passwords, 2FA secrets, tokens, and session identifiers. Eligible users can also permanently delete their account; enterprise owners and platform administrators must first resolve ownership or role requirements.

Yes. Organization workspaces support role-based access. Permissions determine who can view, edit, manage, or administer shared workspace resources.

The resume-access path is designed so platform roles do not automatically grant silent access to private resume content. Access still follows ownership or explicit organization-workspace permissions.