Security at iEmad

Security is built into the shared platform every module runs on. The controls below describe capabilities the platform is designed for — not legal or certification claims.

Tenant isolation

Designed so each customer's data is scoped to its organization across the database, cache, queues, vectors, storage, and search.

Role-based access

Provides controls for least-privilege roles, with platform administration separated from tenant administration.

Module entitlements

Module access is enforced server-side — not just hidden in navigation.

Audit trails

Sensitive actions are recorded to a tenant-scoped audit log; no product route edits or deletes audit rows.

Secure connector handling

Connector credentials are organization-scoped and access is governed by entitlements and permissions.

AI governance

Provides controls for AI policy, security scanning of inputs, and data-boundary handling.

Data-boundary controls

Designed to keep tenant data within its boundary. Plans carry a retention target; automatic deletion on that schedule is not yet enforced.

Enterprise identity

Single sign-on with Microsoft Entra ID over OpenID Connect. SCIM 2.0 provisioning is in beta. SAML sign-in is planned and not yet available.

For governance and compliance details, see the Trust page.