Q: Who is the founder of JURIXA?
A: JURIXA is founded by Behnam Dehghani, an AI developer, TimeAware AI researcher, and senior web developer.
About usHelp center
Client-focused answers for portal access, document uploads, communication, support tickets, AI guidance, and signatures.
A: JURIXA is founded by Behnam Dehghani, an AI developer, TimeAware AI researcher, and senior web developer.
About usA: Use Create organization to set up the owner account for a provider workspace. Clients use the separate client portal path for procedure access.
Create organizationA: Providers use organization sign-up. During onboarding, JURIXA creates the provider profile and workspace settings for that organization.
Create organizationA: Choose Provider if your organization performs legal or procedural work. Clients should use the client portal path instead of creating an organization.
Choose Jurixa roleA: No. Clients can sign up publicly, complete their legal profile, open a procedure request, request quotes, select a provider, and then communicate with that selected provider. Provider invitations still work, but each invitation is tied to one unique procedure.
Start a JURIXA procedureA: JURIXA Education Desk is the client path for education-service seekers, especially international students applying for higher education, scholarships, qualification recognition, enrollment documents, or student visa and residence coordination. It starts with the Education category, a focused service dropdown, and an editable prefilled summary before JURIXA reviews the route.
Start JURIXA Education DeskA: Yes. Solo practices and large firms use the same provider architecture. The difference is plan, seat count, team permissions, Procedure volume, reporting depth, and how the provider manages its client procedures.
Create organizationA: Public client signup asks for the legal name as shown on the passport, NIF or TIN, legal document address, contact details, and notification consent. These details help providers prepare procedure documents with fewer corrections.
Create client profileA: Provider organizations can include certified lawyers or law firms, certified accountants, and service providers for allowed clerical, logistical, or administrative tasks. Available desks depend on the provider profile type, credential scope, and platform review.
Create organizationA: The public JURIXA pages and portal entry points support English, Portuguese, Spanish, Italian, and French through the language picker.
Open full FAQA: The installable app opens the portal sign-in and sign-up experience and skips the public landing page so clients and providers can go straight to the workspace entry point.
Open portal appA: Yes. A guided demo workspace can be enabled by your platform admin so teams can review workflows with preloaded sample data before going live.
Open demo loginA: A Procedure is the governed record for a legal or administrative workflow. It connects the client, the provider doing the work, communication rules, billing policy, status, and audit trail in one place.
See role pathsA: In JURIXA, the client is the person or business receiving the service and using the client portal. The provider is the firm, lawyer, or professional unit that performs the legal or procedural work. A Procedure keeps these responsibilities connected without mixing them.
See role pathsA: Yes. An accountant or another regulated professional can be a provider when they hold a verified professional credential for the scoped work. A certified accountant can handle accounting and tax work, while lawyers and solicitors remain required for reserved legal acts. Clients still do not pick providers from a public directory; JURIXA routes the work to the right verified provider.
Provider guideA: A provider is the organization or professional unit performing the legal, tax, accounting, audit, or procedural work. New routed work requires a verified credential with the right scope for the Procedure. Clients do not choose providers from a public directory; JURIXA routes the Procedure to the provider.
Provider guideA: Provider invitations are tied to one unique procedure. When the invited client accepts, JURIXA confirms legal identity and procedure details for that invited procedure before communication continues.
Create provider organizationA: JURIXA structures the request, category questions, quote routing, selected quote reference, and procedure record. JURIXA does not provide the professional service directly; the selected provider performs the scoped work.
Client guideA: Procedure communication keeps client messages, provider updates, document requests, support tickets, and status changes attached to the Procedure record. Direct client-provider contact appears according to the Procedure's configured communication rules.
See role pathsA: A client first opens a procedure request. JURIXA asks category-specific questions, can help polish the written summary, and uses that request to support quote routing and provider selection.
Client guideA: The selected quote number is attached to the financial agreement. JURIXA creates a system-owned financial-agreement pre-step before provider-defined procedure steps, so the agreement reference stays locked and visible.
Client guideA: Yes, when that provider supports the new category. You can request a quote from your current provider first, and if the amount or scope is not acceptable, you can request quotes from other matching providers.
Client guideA: Do not select the quote if the amount, scope, timing, or provider fit is not acceptable. Where available, you can request other quotes. Paid provider work should start only after the accepted quote and financial agreement path are complete.
Client guideA: JURIXA uses clear procedure references such as CAT-TIN-SEQUENCE, where CAT is a short category code, TIN is the taxpayer number supplied in the intake profile, and SEQUENCE keeps repeated procedures distinct.
Client guideA: A service provider may support clerical, logistical, and administrative tasks where permitted, such as booking appointments, filling standard forms, submitting paperwork with authorization, or tracking status. Reserved legal, tax, accounting, or representation acts must stay with the qualified professional required for that work.
Provider guideA: Desks are the provider's active practice areas for quote routing. The provider chooses desks during organization setup according to profile type and credential scope, and clients request quotes from providers whose desks match the category.
Provider guideA: Yes. Providers can build reusable category workflows, then each accepted procedure receives its own step snapshot after the financial-agreement pre-step. Providers can add or remove provider-owned steps without an extra internal approval layer.
Provider guideA: A provider should keep its professional profile, accepted work areas, team access, and credential context aligned with the Procedures it accepts. Work outside scope should be declined or clarified before delivery begins.
Provider playbookA: Providers review the routed source, client summary, category, requested outcome, and instructions before quoting or accepting. Quote responses and acceptance decisions should stay attached to the Procedure.
Provider playbookA: The provider uses Procedure steps for intake, document preparation, review, filing or delivery, client-safe summaries, and completion records. Internal notes stay separate from what the client should see.
Provider playbookA: Create or finish your client profile, open a procedure request, answer the category questions, and request quotes from matching providers. After you select a quote, communication continues with the selected provider inside the procedure.
Client guideA: Create or sign in to a provider organization, keep your active desks and credential scope aligned, and receive procedure-specific quote requests, documents, and client context through the provider workspace.
Provider guideA: Ask JURIXA is designed as a guided product assistant. It can explain which portal or guide to open, what a Procedure status means operationally, how client and provider roles fit together, where to upload documents, how onboarding works, and what safe next step to take inside JURIXA. It should not decide legal strategy, calculate legal deadlines, or replace the responsible provider.
Open full FAQA: Ask JURIXA uses curated JURIXA guidance, page-aware navigation context, and a retrieval layer first. When the configured LLM service is reachable, it can turn that context into a more natural answer; when it is not reachable, it falls back to the curated retriever answer. In both modes, it is bounded to product guidance and safe operational next steps, not legal advice.
Open full FAQA: Contact JURIXA support for account access, portal issues, billing administration, upload problems, or platform questions. Contact the selected provider for professional scope, documents, procedure strategy, filings, and case-specific decisions.
Open full FAQA: Growth and Pro AI features use server-side legal-data API access when configured. The full Portuguese legal corpus is not shipped to the web app; if the legal-data service is unavailable, JURIXA should show a graceful unavailable state.
Provider guideA: Document generation is a standalone workspace view in the sidebar. It is no longer buried inside a single procedure, although generated documents can still be connected to the relevant work.
Provider guideA: Start by deciding whether you already have portal access. If you do, open the client portal and continue inside your Procedure. If you are joining directly, start a JURIXA procedure so it can be organized and routed safely. Once inside, keep documents, signatures, support requests, and status questions tied to the portal.
Client guideA: Providers create a provider organization, keep professional scope and team access aligned, and work from Procedure records that show source, client context, status, documents, next action, and billing context. The goal is to turn routed demand into organized delivery without losing governance.
Provider guideA: Start with the client guide and compare the active practice areas by the situation, document, authority, deadline, or life event you need to handle. If two routes seem close, choose the main outcome you need first; JURIXA can help organize the Procedure before provider routing.
Client guideA: Consent and scope keep provider work tied to clear client authority. They define what information can be used, what documents are needed, how communication works, and what billing or procedural steps are approved.
Read scope policyA: No. Ask JURIXA explains product navigation, operational workflow, Procedure status concepts, onboarding, billing, and safe next steps. Legal strategy, rights analysis, deadlines, and case-specific advice should be handled by the responsible provider or qualified professional.
Read safety boundaryA: Access is role-scoped. Your details are used for your profile, procedure requests, quote routing, the selected provider relationship, support where needed, and platform administration under the privacy policy. They are not a public provider directory profile.
Read privacy policyA: Important events use email and, where configured and consented, SMS or WhatsApp. Provider-branded messages should use the JURIXA-ProviderName format so clients recognize the source.
Read privacy policyA: Ordinary procedure communications are retained as part of the procedure record. This keeps the communication history complete for status, evidence, support, and handover context.
Read privacy policyA: No. JURIXA is operations-only and stores minimal metadata. For intake safety, organizations can enable end-to-end public-key encryption so CSV/API contact payloads are persisted only as ciphertext envelopes, while organization key material is wrapped at rest and never re-displayed in settings/admin pages.
Read scope policyA: Open the Privacy Policy page to review scope, data-handling roles, provider usage, security boundaries, and contact-data responsibilities. If you want the section about what JURIXA stores versus what your firm remains responsible for, start with Scope and roles.
Read privacy policyA: Open the Terms and Conditions page to review service use rules, billing and cancellation commitments, provider dependencies, suspension or termination conditions, and legal notices. For privacy-specific details, open the Privacy Policy alongside it.
Read terms and conditionsA: For now, JURIXA billing is provider subscription only. Clients may accept provider quotes, but JURIXA does not add its own surcharge to those quote amounts; quote amounts remain agreement records between the client and selected provider.
Review billing modelA: Provider organizations manage subscription plan, payment proof, and approved add-ons from Billing. Bank transfer and MB Way are supported offline payment paths where available, with platform admin approval before access changes continue.
Provider guideA: Clients can complete legal identity details, prepare intake, answer procedure questions, upload documents, request quotes, select a provider, and keep communication organized. The provider quote and agreement govern paid professional work.
Client guideA: The provider organization pays JURIXA through its subscription plan. Client-provider procedure prices are handled through the accepted quote or financial agreement with the selected provider.
Client guideA: Clients use the secure portal login and enter their access code from the firm. After login, they see status, required documents, communication updates, support tickets, and signature requests in one place.
Open client portalA: In the client dashboard, open Documents and submit each requested document requirement. Upload status is reflected back to the assigned team dashboard.
Open documentsA: Use the Communication tab in the client dashboard. Messages are linked to the procedure and routed according to the procedure's communication settings.
Open communication panelA: Clients can submit and track Jurixa technical support tickets directly from the Support tickets tab in the portal. Provider teams can follow up from their workspace when a ticket is tied to a procedure.
Open support ticketsA: Open the Digital signatures tab to review pending requests and complete each signing action. Firms can track pending and completed signature steps from the client matter workflow.
Open digital signatures