Skip to content

Security in context.

Security requirements belong in the deployment conversation from the start. Here is how NexINT approaches access and workspace boundaries.

Updated 17 November 2026

Controlled access

Application access requires an authorized account. The sign-in flow supports server-managed sessions, administrator-provisioned accounts, password changes, and multi-factor challenges when required by the account configuration.

Workspace boundaries

Work is organized by organization and case. Permissions and data access depend on the authenticated user and the deployed configuration. Discuss the roles and separation your team requires during scoping.

Deployment requirements

Hosting location, network controls, retention, backups, encryption requirements, and incident processes should be agreed for your deployment. Specific production security settings should be confirmed during the deployment review.

Source credentials

Some providers require credentials or separate licenses. Include those requirements in your scoping conversation. Never send passwords, API keys, or sensitive case material through the public quote form.

Security questions

For a deployment security review or to report a suspected issue, contact contact@nexint.app. Describe the affected component and the issue without including credentials or sensitive evidence.

Contact the team ↗