'%20d='M136%20392%20V208%20H152%20V232%20H164%20V208%20H180%20V232%20H192%20V208%20H208%20V392%20Z'/%3e%3cpath%20fill='url(%23ft-side)'%20d='M304%20392%20V208%20H320%20V232%20H332%20V208%20H348%20V232%20H360%20V208%20H376%20V392%20Z'/%3e%3cline%20x1='256'%20y1='128'%20x2='256'%20y2='88'%20stroke='%230E3B26'%20stroke-width='6'%20stroke-linecap='round'/%3e%3cpath%20fill='%23BA0D61'%20d='M256%2086%20L292%2097%20L256%20108%20Z'/%3e%3cpath%20fill='url(%23ft-center)'%20d='M216%20392%20V128%20H234%20V152%20H247%20V128%20H265%20V152%20H278%20V128%20H296%20V392%20Z'/%3e%3crect%20x='250'%20y='200'%20width='12'%20height='30'%20rx='6'%20fill='%23FDFDFD'/%3e%3crect%20x='166'%20y='262'%20width='11'%20height='26'%20rx='5.5'%20fill='%23FDFDFD'/%3e%3crect%20x='335'%20y='262'%20width='11'%20height='26'%20rx='5.5'%20fill='%23FDFDFD'/%3e%3cpath%20fill='%230E3B26'%20d='M238%20392%20V354%20A18%2018%200%200%201%20274%20354%20V392%20Z'/%3e%3crect%20x='112'%20y='392'%20width='288'%20height='26'%20rx='9'%20fill='url(%23ft-base)'/%3e%3c/svg%3e)
Fortress · Identity and access Multi-tenant by design.
Enforced on each record.
Fortress is the identity and access plane under every Appriana product. Isolation, identity, and access are first-class parts of the offering. This page says how.
Isolation lives at query time. Settled before a row is read.
Bound at the query
Every read passes through a tenant-aware query layer with a resolved tenant context attached. The scope of the result is fixed before the database runs the statement.
Scoped by path
Tenancy is carried on every record. Resources live on paths such as /orgs/acme, and reads stay inside the caller's path.
Systems held to the same rule
Internal services and scheduled jobs run inside a tenant context of their own. Cross-tenant elevation exists only where it is needed, and it runs through controlled paths.
One identity. Many ways to reach it.
Multiple identifiers
A work email, a personal email, a legacy username, a phone number. Identifiers can be added, verified, and retired while the identity holds steady.
Multiple credentials
A password, a SAML assertion, an OAuth grant, an API key. Each credential attaches to the same principal, and each one is revocable on its own.
Humans and services
Service accounts are first-class principals, distinct from human users, with rotating keys and scopes of their own.
Realms
A Realm is the boundary an identity belongs to. Internal staff, customer users, and contractor populations each get their own, with policy to match.
| Policy | Internal staff | Customer users |
|---|---|---|
| Self-registration | Disabled | Invite-only, or open |
| Email verification | Required | Required |
| MFA | Enforced | Enforced, or optional |
| SSO | SAML or OIDC, required | SAML, OIDC, or password |
Permissions on a path. Scoped to the resource.
/orgs/acme/ns/production/bloom/reports/Q1one report/orgs/acme/ns/production/bloom/**a product, inside one namespace/orgs/acme/**the whole organizationPermissions, roles, groups
Permissions are atomic: read, write, delete, execute, admin. Roles bundle permissions. Groups collect principals. Grants bind groups to roles on a path.
DENY beats ALLOW
Where grants overlap, an explicit DENY wins. Exceptions have to be stated, and stated exceptions are easy to audit.
Sessions
Administrators see every active session with its IP, device fingerprint, and start time. Sessions are revocable one at a time, or all at once.
What this looks like from your seat.
SSO with your IdP
SAML or OIDC. Your team signs in the way it already does.
MFA at the Realm level
MFA is set on the population, so it covers everyone it should.
Granular access for your teams
Read-only executives, admin operators, and contractors scoped to exactly what they need.
Sessions your admins revoke
Your team revokes sessions directly, without a support ticket.
Tenancy held at query time
Your data and another customer's data stay out of each other's reach.
Appriana staff in a separate Realm
Any required access runs through Fortress itself, in a realm of its own.
Vetting Appriana for enterprise rollout?
Bring your security team.
A 30 minute briefing covers tenancy, access controls, and security posture, in direct conversation with the people who build and operate the platform.