Product Guides

How Active Directory changes reach Inaya (through an RMM, Rewst or a connector you run), what is mapped, and what Inaya never does.

Capture bills and receipts from upload, email and WhatsApp, import bank statements, and let the AI categorize, match and reconcile. It recommends; your permissions and approvals decide. Every step is audited and recorded as evidence.

One checked, recorded checkpoint in front of Inaya's text AI assistants: it detects prompt injection and personal data, applies your organization's policy, sends risky actions for human approval, and records every decision in the audit trail and Evidence Graph.

Build, schedule and audit business workflows that combine your Inaya data, an AI Operations Manager, rules and notifications, with human approval for anything that changes a record and evidence for every run.

The organization, department, project, and document layer that every Business Operations module (Tasks, CRM, Procurement, Inventory, Finance, HR) builds on.

Let your customers sign in, raise and follow requests, read help articles, ask an AI assistant that only answers from your published knowledge, and suggest ideas, while your team works tickets with queues, SLAs and a full audit trail.

Turn your Finance, CRM and Procurement records into official, numbered, encrypted, verifiable documents — with approval, secure delivery and a full evidence trail.

How directory groups and attributes become Inaya departments, projects and roles, why privileged access is never granted from an arbitrary group, and how manual overrides are kept.

Let your directory, HR system, PSA or MSP automation drive who has access to Inaya. Joiners, movers and leavers change access automatically, a leaver is cut off at once, and Inaya stays the authority, verifying and recording every change.

How an identity change travels from your directory, HR system or automation to Inaya access, and where each guarantee is enforced.

The webhook contract (signature, timestamp, replay, size, tenant binding), credential lifecycle, privilege rules, and what is tested.

Why an event was refused, ignored or parked, what to check first, and answers to the questions administrators ask most.

What happens to Inaya access when someone joins, changes team or leaves; how immediate revocation works, its states, and the honest limits on tokens and sessions.

A real, provisioned PostgreSQL database, a general document-understanding studio for any document type, and an AI workbench for data cataloguing, quality checks, model registry and a governed sandboxed code runner.

Connect your Entra tenant to Inaya: signed events, optional Microsoft Graph pull with your own app registration, and how this relates to Inaya's existing Microsoft sign-in.

How a managed service provider manages customer organizations through Inaya identity automation without ever crossing tenant boundaries, with delegated technician roles.

Find drift between your directory and Inaya, certify who should have access, expire temporary access, and find work left without an owner. Reports and decisions only; nothing is deleted or reassigned silently.

How a Rewst workflow (or any automation platform) drives Inaya identity actions and receives Inaya events, with reference workflows, and an honest statement of what has and has not been tested.

Generic adapters that normalize RMM, PSA (ITSM) and HR events into Inaya joiner, mover, leaver and status-change events.

Inaya's SCIM 2.0 server: what it supports, how users and groups map to lifecycle events, and what is deliberately not supported.

End-to-end encrypted chat, notes and sharing inside Inaya, with the controls an organization needs to run them safely.

Real network storage (SMB and NFS) for your office, connected to Inaya's encrypted cloud storage, verified backup and recovery, ransomware response, evidence and What-If simulation.

Real-time SQL access to legacy and relational data sources through a live, permission-scoped virtual schema — inspired by Software AG CONNX.

How a physical or virtual Linux host joins your organization's infrastructure cluster, and what happens after it does.

A customer-owned physical compute, network, and block-storage layer underneath Inaya's existing enterprise platform — bare metal you control, not a second cloud.

A decentralized, node-reported threat registry with reputation-weighted confirmation — public, not a single company's private blocklist.

Mount your organization's Inaya storage as a real drive letter on Windows or a real mount point on Linux.

Client-side encryption, binary sharding, and DePIN-backed custody for every file stored on Inaya.

Use Inaya through a real, tested S3-compatible API — verified against the AWS CLI, rclone, Terraform, and the AWS SDK.

An IBM Cloud VPC Storage-inspired control panel for volumes, file shares, snapshots, and automated backup policies — plus a real Terraform provider.