Q: How do I create a Jurixa organization?
A: Use Create organization to set up the owner account, then choose whether the organization operates as an agent or mediator, or as a provider, so Jurixa creates the correct profile.
Create organizationHelp center
Firm-focused answers for workspace setup, automations, inbox routing, billing, and security controls.
A: Use Create organization to set up the owner account, then choose whether the organization operates as an agent or mediator, or as a provider, so Jurixa creates the correct profile.
Create organizationA: They can enter through the same sign-up. During onboarding, they choose the organization's Jurixa role: an agency gets an agent or mediator profile, and a provider gets a provider profile.
Create organizationA: Choose Agent or Mediator if your organization represents or coordinates clients. Choose Provider if your organization performs legal or procedural work.
Choose Jurixa roleA: No. If you have an external agent, the agent can create your client profile. If a provider introduces you, or if you sign up directly, JURIXA Agent mediates the Procedure and keeps communication routed through the agent by default.
Start with JURIXA AgentA: Yes. Solo practices and large firms use the same provider architecture. The difference is plan, seat count, team permissions, Procedure volume, reporting depth, and whether the firm also acts as a mediator for its own clients.
Create organizationA: Add allowed email domains in settings, then teammates can join using approved domain emails or invitations.
Open domain settingsA: Owner and Admin can manage settings and billing. Staff can run operations modules, and Viewer is read-focused for reporting visibility.
See role guideA: Open Settings in the demo workspace to view demo role accounts (Owner/Admin/Staff/Viewer) and sign in with each account to verify access differences.
Open demo role checkA: 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 underlying client, the authorized agent or mediator, the provider doing the work, communication rules, billing policy, status, and audit trail in one place.
See Procedure modelA: The client is the person or business receiving the service. The agent or mediator manages the relationship, intake, routing, or representation under consent. The provider is the firm, solo lawyer, or service unit responsible for the legal or procedural work.
See role modelA: An agent or mediator can be an external agency, consultant, accountant, business representative, family office, firm team, Jurixa coordinator, the client acting for themselves, or a future AI/human support model. The important rule is that the Procedure must record scope, authority, and consent.
See agentsA: Yes. An agency or mediator can manage a portfolio of represented clients, as long as each client relationship has the right consent and scope. Billing can then be based on represented clients, active Procedures, seats, a subscription tier, or a negotiated policy.
Create agent organizationA: A provider is the organization or professional unit performing the legal or procedural work. Clients do not choose providers from a public directory; external agents or JURIXA Agent route the Procedure to the provider.
See role modelA: No. The provider performs the legal or procedural work. When a provider introduces a client, JURIXA Agent is the mediator for that Procedure unless an external agent relationship is recorded separately.
Create provider organizationA: For direct-client requests, Jurixa can coordinate intake, document readiness, provider routing, status follow-up, and paid support options. The provider still performs the legal or procedural work, while Jurixa coordination keeps the Procedure organized.
See Jurixa coordinationA: By default, Procedure communication follows client to agent to provider. In an external-agent flow, the client communicates with that agent. In provider-introduced and direct-client flows, JURIXA Agent mediates. Direct client-provider contact appears only when the agent approves it for that Procedure.
See communication modelA: Consent and scope prevent someone from acting for a client without clear authority. They define what the agent can see or do, such as preparing information, uploading documents, communicating with the provider, handling billing, or approving procedural steps.
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: 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: Open Settings and use End-to-end Intake Encryption. The built-in generator creates a key pair in your browser, inserts the public key for save/rotation, and lets you copy or download the private key for offline custody. JURIXA does not re-display the stored public key; only status/fingerprint metadata is shown.
Open key generatorA: Billing should follow the role and source of the Procedure. Clients may pay for Jurixa-guided support or provider services, agents may be billed per represented client or active Procedure, and providers may pay subscription, seat, usage, or mediated-client access fees.
Review billing modelA: Yes. Clients use their invited JURIXA portal at no charge. Providers use the Provider Workspace plan, selected and managed from Billing inside the provider profile.
Create organizationA: Client portal access is free for invited clients. Providers choose Provider Workspace from Billing, complete Stripe Checkout, then Owners manage payment details from Settings through Stripe Customer Portal.
Open billingA: Provider Workspace is the standard provider plan. It covers provider-side procedure intake, mediated communication, document work, scheduling, billing, and reporting without separate add-on module activation.
Compare plansA: Provider Workspace supports email and SMS delivery for standard provider operations. Organization-level channel toggles still control whether an available channel is used.
View plan channelsA: Billing shows the Provider Workspace base plan price and the effective monthly total for the organization. Standard provider workspaces do not activate separate add-on module charges.
Review pricing detailsA: Yes. Owners can open Stripe Customer Portal from Settings to change plans, update payment details, or cancel at period end.
Open customer portalA: Stripe sends payment-failure events and JURIXA syncs status. You should update payment method in Customer Portal to restore active subscription access.
Open billing managementA: JURIXA is not accounting, trust-accounting, or tax software. It supports procedure operations and shows operational revenue-impact estimates for planning.
Set finance profileA: Yes. Set working days and office hours in Settings. Manual consultation creation and CSV/API intake outside that schedule are automatically rejected.
Configure working scheduleA: Yes. In Settings you can enable overlapping consultations and define default concurrent capacity per 30-minute slot. Scheduling and imports enforce this automatically.
Set overlap policyA: Yes. In Calendar, Owner/Admin can choose a location and slot start time (30-minute boundary) and set capacity for that exact slot.
Open calendar capacityA: Go to Settings and update WA/SMS Delivery Settings. You can enable/disable channels, set sender labels, and set office sender numbers used for actual SMS/WhatsApp delivery.
Open WA/SMS settingsA: Workspaces can run in simulation mode during rollout. For production delivery, your platform admin connects an approved messaging provider and your team sets sender numbers in Settings.
See provider modeA: Yes. Set your office sender numbers in Settings. If Twilio is configured, JURIXA uses those numbers for reminder sends; otherwise it stays in mock mode.
Configure office sender numbersA: Every consultation message can include expiring one-time tokens so contacts can confirm, cancel, or request reschedule safely.
Open automationsA: Use the dashboard and reporting pages for missed-consult rate, cancellations, recovered slots, reminders sent, and backlog trends.
Open reportingA: Add-on modules are deactivated in standard provider workspaces. If a provider needs custom operational work beyond Provider Workspace, submit a Support Desk request so JURIXA can scope it separately.
View enabled modulesA: Standard add-on module activation is not available from the provider sidebar. Use Support Desk for custom operational requests that need JURIXA review.
Open Support DeskA: Standard provider workspaces do not expose add-on module activation. JURIXA reviews custom operational requests through Support Desk when a provider needs scoped work outside the core plan.
Open settingsA: Enabled add-on runtime controls are not part of the standard provider workspace. Provider operations should be managed from the profile front page, procedure workspace, settings, billing, support, and calendar.
Open profile front pageA: Add-on module badges are hidden in standard provider workspaces because add-ons are deactivated. Use Billing for the Provider Workspace subscription and Support Desk for custom requests.
Open settingsA: The standard monthly total is the Provider Workspace base plan. Add-on module charges are not active in standard provider workspaces.
Review billing impactA: There is no standard add-on rollout order while add-on modules are deactivated. Start with Provider Workspace, then use Support Desk for any custom operational scope.
Open Support Desk