Enterprise access boundary
Client Access Overview
Client access is not activated from the public website. Raven starts with a controlled briefing, a scoped pilot path and a human approval gate before any tenant, account, connector or customer data workflow is opened.
Audience procurement / IT owner
Mode controlled access
Activation human approval only
What Happens First
BriefingRaven confirms environment, role, operational problem and whether the request belongs in research, review, pilot or production discussion.
ScopeThe client and Raven define what is being evaluated, which data class is allowed and who owns the decision boundary.
ChecklistData requirements, transfer channel, retention, deletion, support access and review owner are agreed before operational data is requested.
Pilot gateA read-only, historical, synthetic or anonymized pilot can be prepared only after the scope and boundary are approved.
What Is Not Opened Publicly
No tenant creationThe public page does not create a customer tenant, production account, API token or live collector.
No live writeRaven does not execute customer actions from the public site and does not bypass customer change control.
No payment activationInterest, a form submission or a payment event is never sufficient to activate production access.
No data upload requestOperational data is not requested here. The transfer path must be separately approved.
Account Activation Gate
IdentityCustomer access requires identity verification, MFA and an approved identity provider path before activation readiness.
TenantTenant boundary and RBAC role must be verified before a customer user, support account or API service account can be considered.
Legal and securityDPA, terms, security review, support owner, audit reference and owner approval must be attached before activation review.
Support and APISupport access must be time-bounded. API service accounts require sensitive credentials management and rotation policy before use.
Customer activation release gateAccount readiness does not create access. Customer activation requires accepted account gates, approved customer-activation review, owner or admin release, audit reference, rollback reference and support scope.
No account creationThe public site does not create an account, create a session, open tenant runtime, write a database, call a provider or send activation notification.
API envelopeFuture API access requires endpoint contract, auth, tenant, RBAC, audit, idempotency, rate-limit and provider-signature gates before use.
API guard stackFuture API access also requires endpoint release approval, closed runtime blockers and safe error mapping before any listener can be considered.
Portal sessionCustomer portal session readiness requires account activation reference, auth context reference, owner approval, audit reference, CSRF reference, bounded TTL, identity verification, MFA verification, tenant scope verification, RBAC verification, terms acceptance and DPA readiness.
No session runtimeThe public site does not create a portal session, set a cookie, call external auth, open tenant runtime or write a database.
Portal modulesPortal modules are entitlement previews: Live Briefing, Incidents, Decision Packets, Reports And Dossiers, Evidence Vault, Simulations, Technician Dispatch, Billing And Credits, Audit Export, Users And Security, Settings and Collectors require package depth, RBAC permission, portal-session-ready reference, audit reference and owner approval before release.
No module runtimeNo module is loaded, no tenant data is read, no write action is performed, no tenant runtime is opened and no external export is created from the public page.
Workspace read modelWorkspace read model is prepared only from approved module snapshots and approved data modes: synthetic, historical approved, anonymized approved or read-only approved. It requires portal-session-ready reference, data snapshot reference, module entitlement references, audit reference and owner approval.
No workspace data fetchThe public page does not render a customer workspace, read a database, start live queries, open tenant runtime or load customer data.
Workspace export gateWorkspace, report, dossier, audit, CSV, XLSX, JSON or PDF export requires approved scope, approved format, held delivery mode, audit reference, owner approval, export authority, retention policy for non-synthetic data and DPA/redaction gates when personal data is present.
No export runtimeThe public page does not write files, create external exports, enable downloads, send notifications, read a database, load customer data or start delivery.