EntariBusiness

Employees do not need to know the whole workspace. They sign in, open Actions in the navigation, and only see what their role can access, grouped under headings such as Personnel, Finance, and IT. Files live in hubs; work they must do starts here.

One action at a time. They expand Personnel, for example, and choose «Hire employee»: role, start date, and IT/equipment needs. The candidate gets a secure link and fills CPR, address, and bank themselves, so managers do not type that in. The case lands in the HR register, and an employee folder can be created under HR when the person becomes active.

Or an expense. «New expense»: amount, purpose, and a photo or PDF of the receipt. Amounts can be suggested when the attachment can be read. Save writes to Finance; if approval is on, the approver gets a case under Actions. A bubble shows when something needs you (needs you / waiting / completed).

Or a hindrance at work. «Raise objection» reports a blockage so it lands structured in the legal/objection list, not in a random email thread. «Manage access» is the matching path for IT: pick an employee, add or remove system access, save.

On the phone. Field view is built for one-handed use: hubs, actions, and the camera for receipts and equipment. You do not hunt for the right SharePoint folder in the field, you pick the action and take the photo there.

What happens in the background. The form saves to the right register and hub. The bell at the top can show notifications you turned on under Settings (for example expenses or objections), but work that needs you still lives under Actions. The first time, the intro guide (question mark) can walk through hubs, files, actions, and search. After that it is usually: find the action, fill what is needed, close.

You are the controller of content you put in Entari. Entari ApS is the processor under GDPR Article 28 when we process that content on your behalf. This is set out in our data processing agreement (DPA), which comes with EntariBusiness.

Cloud and Connect. Entari Cloud is hosted on Microsoft Azure in the EU. There we store workspace content, registers and files as processor. With Entari Connect, business data remains primarily in your own Microsoft 365 tenant (SharePoint, lists, files), where Microsoft is your processor. Entari then processes only the limited metadata needed for licence, support and integration.

Access. Sign-in uses Microsoft Entra ID. Workspace access follows roles and security groups (for example leader, employee, read-only). With Connect, permissions sync to SharePoint folders so files and rights stay aligned while you work.

EntariPass (shared passwords). EntariPass uses zero-knowledge client-side encryption: secrets are encrypted in the browser with AES-GCM (256-bit) before storage. The key is derived locally from the PIN or master password with PBKDF2 (310,000 iterations). The PIN and key are never sent to Entari, and we cannot read plaintext in normal operation. If you lose both the PIN and the recovery key, the content cannot be recovered. About EntariPass.

Operational security. We implement appropriate technical and organisational measures, including access control, encryption in transit (TLS), environment separation, logging of administrative actions and confidentiality for staff with access. OCR via Azure AI Document Intelligence runs only when you use that feature.

Where the precise terms live. Roles, subprocessors, export on termination and the rest of our duties are in the data processing agreement (DPA) and the privacy notice, in the product and on our legal pages. We are in soft launch and do not yet have an independent security audit; that is stated plainly in those documents.

Entari Connect means business data lives in your Microsoft 365, not in a parallel database with us. You work in Entari; files, folders and registers land in SharePoint and Microsoft Lists in your tenant. Sign-in is Entra ID (SSO/MFA). You can continue in File Explorer or OneDrive shortcuts when that fits.

Consent first. A Global Admin approves Entari once («Approve» / Admin Consent). That grants the app Microsoft Graph rights to read your users and org structure, create security groups, read/write SharePoint in the areas you later choose to deploy, create Teams, and send service messages when the platform needs to notify people. Consent itself does not change your existing SharePoint or Teams structure, concrete hubs are chosen and previewed in deployment.

What is created per hub. When you deploy a department, provisioning runs in order: Entra security groups → Team and SharePoint site → permissions → folders in the document library → Microsoft Lists for registers. Each department typically gets three groups: leader, employees, and read-only. Access, publication and external sharing mirror to SharePoint permissions when writes are enabled.

New department. If you create a new hub (custom department), the same pattern applies: the name becomes the Team name, the three security groups are created automatically, you choose the folder structure (often numbered 01_, 02_, …), and on deploy the site, folders and lists land in the tenant. Your existing tenant root and Teams are not rewritten.

Forms and lists. Actions in Entari are forms. When you save, the record writes to the right register. Under Connect the register is a Microsoft List: form fields mirror to list columns, so what you see in Entari is the same content you can open in SharePoint. Custom processes and Form Builder can sync fields and choice options to the list.

What Connect does not do. Encrypted EntariPass passwords are not rewritten into Microsoft. Deleted Entari lists and folders are not rebuilt automatically. Notifications/approvals to Teams are optional under Settings. Live file writes follow your Connect configuration, you own the tenant, licences and data classification.