Noema Teams

You create a workspace and get a company code. Employees open Noema, go to Settings → Enterprise, enter the code and their work email, and verify with a one-time code. Their device registers and fetches a policy snapshot — which datasets, tools, model formats, specific models, and remote backends their roles allow. The app caches that policy and enforces it locally, even offline.

Upload handbooks, research, contracts, or course material to your workspace and assign them to roles. Permitted employees see them appear in Noema as company datasets — indexed and searched entirely on device through the same Retrieval-Augmented Generation pipeline Noema users already know. Files are hash-verified on download, stored in app-private storage, and removed when access is revoked.

Default roles — Owner, Admin, Member, Research, Engineering, Finance, Legal, Teacher, Student, Volunteer — are ready out of the box and fully customizable. Per role you decide: which datasets are visible, which tools run (web retrieval, Python, memory, calculators), which model formats and specific models can load, which remote backends and endpoint types are reachable, whether remote inference is allowed at all, and whether the device must operate off-grid.

Policy checks sit inside Noema's execution paths. A disallowed tool doesn't run. A disallowed model doesn't load. A disallowed backend can't be called. If a role requires off-grid operation, the app's network kill switch engages — the same one consumer Noema uses — allowing only policy sync with your workspace. Expired policies degrade safely: cached restrictions stay in force and company datasets go dark until the device syncs again.

Membership is tied to verified work email. Invite employees directly, restrict joining to your email domain, or require admin approval for every request. Each device is individually registered and individually revocable from the console. Single sign-on via OIDC is on the roadmap; v1 keeps identity simple and auditable.

Everything is managed from this site — no spreadsheets, no config files. Overview, Employees, Roles, Datasets, Models & Tools, Invites & Access, Devices, Settings, and an activity stream of administrative events. Telemetry stops there: Noema never sees your documents, prompts, or answers.

Companies with internal knowledge that can't leave the building. Schools giving students a safe, governed assistant. Research groups working with embargoed data. Clinics, law practices, campaigns, nonprofits — teams that need private AI without losing control of internal knowledge or paying per token.