01
Microsoft Entra sign-in
Folentra supports Microsoft Entra work-account sign-in when a deployment is configured with the required identity and API settings.
Security
Client-level access. Recorded changes. Clear AI boundaries.
Folentra separates implemented workspace controls from deployment-specific assurances. Hosting, retention and provider details should be confirmed in an approved security review for the service you use.
02
Client-scoped roles
Protected client endpoints apply minimum Viewer, Editor or Owner requirements, with separate administrator permissions.
03
Change history
Supported create, update and delete activity is recorded with the actor and timestamp. Supported updates also include field-level before-and-after context.
04
User-triggered AI
AI assistance starts with a user action. Generated text and structured suggestions are working material that requires professional validation before use.
Operational transparency
Deployment details should be confirmed in an approved security review.
Hosting, encryption, retention, recovery, AI-provider handling and subprocessors depend on the approved production configuration. Folentra does not publish certification badges or infrastructure claims until that information has been verified for release.
Deployment-specific scope
Hosting region · Encryption arrangements · Retention and deletion · Backups and recovery · AI provider handling · Subprocessors
These details should be supplied through the approved security schedule and privacy notice for the relevant deployment.
A closer look at Folentra
Discuss Folentra’s access model and deployment context.
Book a focused walkthrough using illustrative client data, from transaction mapping to editable Word output.