Skip to main content

Enterprise Onboarding Guide

A step-by-step guide for IT administrators setting up Nquiry for their organization.

Choose Your Deployment Path​

Nquiry is delivered through two channels. Pick the one that fits your data-sovereignty and procurement constraints, then follow the matching path.

Path A — Direct SaaS (app.nquiry.ai)​

JE Vectors operates the entire stack in our AWS account. You sign up, invite users, and start working — no infrastructure to provision and nothing to install.

Best for: Organizations comfortable with multi-tenant cloud, teams that want to be productive on day one, anyone evaluating Nquiry before a larger commitment.

Prerequisites:

  • A modern web browser (Chrome, Firefox, Safari, Edge)
  • An email address for the organization owner account
  • A decision on your billing plan (Trial is free for 14 days)

Skip to Step 1 — Create Your Organization below.

Path B — Licensed (Single-Tenant) Deployment​

Nquiry is deployed as a complete, isolated stack in your own AWS account via AWS Marketplace. Your investigation data never leaves your AWS boundary; you control encryption keys, backups, and the upgrade cadence.

Best for: Federal agencies, healthcare systems, and other organizations that require data sovereignty (FedRAMP, IL-4, agency-specific data residency rules) or that already operate inside an authorized AWS boundary.

Prerequisites are an AWS environment, not a browser. See Customer Environment Requirements for the full prerequisite list (AWS account type, Bedrock model access, sizing guide, deployment process). Once your environment is provisioned and Nquiry is deployed, the rest of this guide — organization setup, user invitations, workflow — applies to your deployment exactly as it does to SaaS. Pick up at Step 2 — Configure Your Organization.

Step 1: Create Your Organization​

SaaS path only — licensed deployments handle account provisioning during the deployment process described in Customer Environment Requirements.

  1. Navigate to app.nquiry.ai and sign up with your email address.
  2. Complete email verification.
  3. Set up multi-factor authentication (recommended for all admin accounts):
    • WebAuthn (passkey/biometric) — most secure, recommended
    • TOTP (authenticator app) — works with Google Authenticator, Authy, etc.
  4. A personal organization is automatically created for your account.
  5. To create a team organization: go to Settings → Organizations → Create Organization.

Step 2: Configure Your Organization​

From the Admin Dashboard (available to Owners):

Organization settings:

  • Set organization name and slug
  • SaaS: Choose your billing plan (Trial → Core → Pro → Enterprise)
  • Licensed: Plan selection is not applicable — your license entitles you to full functionality with unlimited users

User management:

  • Invite team members by email (Settings → Members → Invite)
  • Assign roles based on responsibilities:
    • Owner — Full access including billing and member management. Assign to IT administrators or team leads.
    • Admin — Can manage members and access all investigations. Assign to supervisors or team leads.
    • Member — Can create and manage their own investigations. Assign to investigators, auditors, analysts.
    • Viewer — Read-only access. Assign to reviewers, stakeholders, oversight personnel.
  • Members receive an email invitation and create their own accounts with MFA.

Step 3: Understand the Data Model​

Each organization contains investigations (also called projects). Each investigation follows a four-phase workflow:

  1. Planning — Define topics and investigative questions
  2. Collection — Upload and organize evidence (documents, interviews, observations, datasets, notes, standards)
  3. Analysis — Generate AI-assisted analysis per question, topic, or overall summary
  4. Reporting — Generate structured reports with evidence citations

Evidence types supported: PDF, Word (.docx), Excel (.xlsx/.xls/.csv), images (JPEG, PNG, GIF, WebP), Markdown, and text files. Full file-type list in product-facts.md §7.

Storage limits (SaaS): 2 GB on Trial, 25 GB on Core, 100 GB on Pro, unlimited on Enterprise. Storage (Licensed): Determined by your RDS and S3 sizing — see the Customer Environment Requirements sizing guide.

AI generation quotas (SaaS): 15 total on Trial (does not reset), 25/month on Core, 50/month on Pro, unlimited on Enterprise. Generations include: analysis generation, analysis regeneration, and report sections. AI Guide chat messages are free (Haiku 4.5, 200/day soft cap per user). AI generations (Licensed): No vendor-imposed quota. Bedrock costs flow directly through your AWS bill — see ADR §2 and the sizing guide for typical token usage.

Step 4: Set Up Your First Investigation​

We recommend the organization owner or an admin creates a test investigation to verify the workflow:

  1. Create a new investigation — Choose a work type (e.g., Review, Audit, Investigation).
  2. Add a topic and 2-3 questions — These structure what you're investigating.
  3. Upload 3-5 evidence items — Use the bulk upload feature (up to 20 items at a time).
  4. Link evidence to questions — This tells the AI which evidence is relevant to which questions.
  5. Generate analysis — Run a question analysis to see the full AI output with quality metrics.
  6. Review the results — Check faithfulness scores, coverage, confidence levels, and cited evidence.

This end-to-end test confirms that evidence processing, AI analysis, and quality metrics are all working for your organization. For licensed deployments, this is also where you verify that Bedrock model access and quotas are correctly configured before rolling out to your team.

Demo scenario available: The "Disappearance of Mr. Davenheim" guided demo (available in the template library) provides a complete investigation scenario with 30 evidence items, pre-defined questions, and expected outcomes. It's useful for training new users.

Step 5: Establish Organization Practices​

Before rolling out to your team, consider:

Evidence management:

  • Establish naming conventions for evidence items
  • Decide on evidence type categorization standards
  • Set expectations for linking evidence to questions (more links = better AI analysis)

Quality standards:

  • Define minimum faithfulness and coverage thresholds for your organization (e.g., 85%+)
  • Establish a review workflow: who reviews AI analysis before findings are finalized?
  • Document when to regenerate analysis vs. when to add more evidence

Access control:

  • Assign roles based on the principle of least privilege
  • Owners should set up MFA for their accounts immediately
  • Review member access periodically (the Admin Dashboard shows active users)

Audit trail:

  • All actions are logged automatically (uploads, analysis generation, report exports, team changes)
  • Audit logs are accessible from the Admin Dashboard
  • Logs include: user, organization, timestamp, action type, IP address, success/failure

Ongoing Administration​

Regular tasks:

  • Review and manage team members as staff join or leave
  • Monitor storage and AI generation usage from the Admin Dashboard
  • Review audit logs for any unusual activity
  • Ensure all team members maintain active MFA

Billing management (SaaS):

  • Billing is managed through the Settings page (Owner access required)
  • Plans can be upgraded at any time; downgrades take effect at the next billing cycle
  • Enterprise customers: contact your account representative for billing changes

Updates and maintenance (Licensed):

  • Updates are customer-initiated. New container image versions are published to AWS Marketplace; your operations team chooses when to apply them — see Customer Environment Requirements §9 for the release model and zero-downtime update path.
  • Bedrock costs and AWS infrastructure costs appear on your AWS bill; review the sizing guide if usage outgrows your initial deployment size.

Support:

  • In-app AI Guide provides contextual help and methodology guidance
  • Email support: support@nquiry.ai
  • Enterprise customers: dedicated support channel as defined in your service agreement
  • Licensed customers: annual maintenance and support is included with the license — contact JE Vectors for incident response, version upgrades, and architecture consultation

Security Recommendations​

For organizations handling sensitive data:

  1. Require MFA for all users — Especially WebAuthn for admin/owner accounts
  2. Use the Viewer role for stakeholders who need read-only access
  3. Review audit logs monthly for unexpected access patterns
  4. Brief your team on evidence handling procedures before starting investigations
  5. Establish data classification — Nquiry is designed for sensitive but unclassified information by default; licensed deployments can be configured for IL-4 (DOD CUI) — see the single-tenant architecture ADR §5

Next Steps​