Account setup
HAQQ is one account across several surfaces. Practice management, the AI Twin and the administrative controls behind both are different interfaces onto the same workspace, and a change made in one shows up immediately in the others.
One account, connected interfaces
You sign in once. What you get afterwards depends on where you go, not on which account you used:
| Interface | Where it lives | What you do there |
|---|---|---|
| eFirm | efirm.haqq.ai | The practice-management platform: matters, contacts, hearings, tasks, documents, billing, and the firm settings and roles behind them. This is where daily work happens. |
| Justinian, the Legal AI Twin | chat.haqq.ai | The AI assistant: research, document review, drafting, the prompt library, and the AI settings that govern them. |
| Account administration | Inside the main app | Subscriptions, workspace creation, seats and team management, and account settings including the danger zone. |
Changes propagate. Add a seat on the subscription and the workspace can invite another member; invite a member in eFirm and they sign in with the same account they would use for the AI. There is no second directory to keep in step.
Which interface owns which setting
The most common source of confusion is not how to change something but where. Roughly:
- What the firm has bought — plan, seats, billing cycle, renewal — is account administration. See Manage subscription.
- How the firm works — practice areas, matter types, form templates, currency, tax rate, timezone, sidebar layout — is eFirm. See Settings and Customizations.
- Who can reach what — roles, per-module permissions, record scope, hidden fields — is eFirm. See Setup Roles & Permissions.
- How the AI behaves — models, sources, firm preferences — is Justinian. See AI Settings.
One consequence catches new administrators out: team membership is managed in two places. eFirm holds roles, permissions and day-to-day management; AI seat allocation is set on the Justinian side. Adding somebody to the firm and giving them the AI are two acts, not one. Invite users covers the invitation itself.
Setting up a new firm, in order
A 15-person firm — three partners, seven associates, two paralegals, two administrators and a finance manager — gets from nothing to working in about an hour by going in this order:
- Create the workspace.
- Configure Global Configurations — practice areas, courts, task types — because everything downstream draws its dropdowns from them.
- Set up the roles the firm actually has: Partner, Associate, Paralegal, Admin, Finance.
- Invite all fifteen members, each against the right role.
- Configure financial settings — base currency and tax rate, for instance AED and 5% VAT.
- Connect Microsoft 365.
Everyone then signs in with a one-time code, sees only the modules their role allows, and starts working. The order matters more than it looks. Global Configurations are the foundation the form templates draw from and are referenced across the whole product, so they come first; members invited before their role exists have to be edited afterwards. The same sequence, in more detail and with the later steps included, is in Settings and Customizations.
The workspace is the boundary
Everything above happens inside one workspace, and a workspace is where a firm's data stops. A single HAQQ account can belong to several — separate offices, separate legal entities, or a demo environment kept apart from the real one — and switching between them changes the whole dataset. Which model a multi-office firm should use is a genuine choice with two supported answers; Multi-entity sets out the criterion, and Data Architecture explains what isolation does and does not mean.