Group-based access
Users belong to groups. Groups have access to specific connections, schedules, and triggers. A salesperson and a finance lead can both ask questions, but each can access only the data their group has been granted.
Governance
Know who's asking what. Control who sees the answers.
Inquerio AI is one installation, many teams. Each team sees what they should see, and nothing else. Every question is on the record.
Roles and groups
Different teams, different views, one platform.
Sales sees sales. Finance sees finance. The same Inquerio AI handles both, with row-level isolation between them. No 'admin can see everything' shortcuts.
Row-level isolation between tenants
When more than one business unit, subsidiary, or customer shares an Inquerio AI installation, the boundary is enforced at every read. One tenant cannot see another's data, and the system prevents accidental cross-contamination.
Full activity log
Every question is on the record.
Every question, every answer, every export, every scheduled delivery, every trigger fire. Attributed to the user. Time-stamped. Searchable.
When compliance asks "who saw this customer's data, and when?", you have the answer in seconds, not in a week-long forensic exercise. For organizations operating under GDPR, the audit log is the evidence trail that demonstrates exactly who accessed personal data, when, and through which system — without any additional tooling.
The same audit applies to API access. A scoped key fires a question? Logged. With which payload, against which integration, with which response? Replayable.
app.inquerio.ai
app.inquerio.ai
Sign in your way
The way your team actually logs in already.
Username and password + two-factor authentication
Standard credential login with required 2FA. The fallback every user understands.
Passkeys
Modern, phishing-resistant sign-in with platform passkeys. No password to forget, no code to mistype.
API keys with group scope
Programmatic access through scoped API keys. Each key belongs to a group, sees only what the group sees, and can be rotated or revoked at any time.
Built for shared installations
Multi-tenant from day one.
Multi-tenancy isn't an upgrade or an enterprise add-on. It is the default architecture. Whether you have one team or ten business units sharing one Inquerio AI, the same isolation rules apply on every read.
That makes it safe to start with a pilot in one team and grow it across the company without re-architecting later. The boundary you set on day one is the boundary on day three hundred.
Open access for the right people. Closed for everyone else.
Bring your access model. We'll show you Inquerio AI enforcing it on every question, every export, every trigger.