Learn the product the same way you will operate it.

New users should begin at the Encompax account layer so profile identity, legal acknowledgements, support routing, module approvals, and future upgrade posture all live in one place.

• Choose Google, Microsoft, or email sign-in.
• Complete the profile basics for operator and organization identity.
• Accept terms and privacy before workspace access begins.
• Land in the workspace shell before module launch begins.

Returning operators should move through the workspace shell, where Encompax restores module cards, package posture, support routes, and rollout guidance from the same account profile layer.

CSV and spreadsheet imports are good for first-run rollout because they make the data shape visible early. If a customer already owns a database or API system of record, Encompax should preserve that truth instead of forcing the workflow back into spreadsheet-only onboarding.

• Use CSV or Excel for first-run visibility.
• Use Google Sheets export when the team already operates in Workspace.
• Use database or API connections when the customer has an active system of record.
• Save source posture so upgrades do not restart onboarding.

Encompax uses org-aware source mapping so a customer can begin with one module, then reuse that same connectivity posture when a second module is added later.

Early rollout accounts should stay grounded in starter language until the workspace proves that module usage, data connectivity, and operator support posture are real. Once evidence strengthens, package messaging can move from starter rollout into cross-module readiness and governed expansion.

SIL is the current live rollout path. Future access to Marengo, agents, and additional module families should appear as controlled upgrades inside the same signed-in Encompax workspace.

The public site introduces the product, but the real purpose of the account and workspace layer is to keep approvals, support accountability, legal acknowledgement, data posture, and module expansion in one stable control surface before any operator enters module-specific workflows.

A shared workspace means operators can keep the same sign-in pattern, support language, rollout desk, business contacts, and upgrade model as Encompax grows across SIL, Marengo, and future agentic workflow surfaces.

We are checking the current support, billing, security, and rollout desk paths from the published support object.

The help center, FAQ, terms, and privacy pages remain the short-form references, while this resource library becomes the deeper operating manual for how Encompax account access and module rollout actually work.