VeritomeHelp Centre
/
Browse documentation
Using Veritome

Organisation: profile, members, billing, security and data

The Configure screen for everything set once: the organisation profile that feeds your documents, members and roles, your own AI literacy standing, billing, SSO, security, data residency, API keys, integrations and notifications.

Updated Veritome documentation

Organisation (under Configure) holds everything that is configured once for the workspace. Which tabs a person sees depends on their role — an Org admin sees them all; a member sees their own.

Organisation

  • Organisation profile — legal name, country, address, contact email, organisation type, legal form, registration number, website and size band. These values pre-fill the provider identity block on the EU declaration of conformity and the Annex VIII registration sheet, so fill them in early. The contact email and country are what mark the profile complete on the first-run checklist.
  • Members & roles — invite people, set their role, reset a password, remove a member; and the roles themselves — the built-in set, custom roles, per-permission editing. See Invite your team and assign owners.
  • AI literacy — your own Art. 4 standing: the answers you gave, the programmes assigned, and when your record lapses. The team view lives on the Academy.
  • Billing & plan — the plan, its caps, and the usage meter. While billing is off it reads Free public release; see Plans, billing and upgrades.

Security & access

  • SSO & SCIM — enterprise OIDC single sign-on and directory provisioning. See Set up SSO and SCIM provisioning.
  • Security — require two-factor authentication for every member, the password policy, and session controls. Two-factor is opt-in per account from the first-run checklist and enforced on every login once enrolled.

Data & platform

  • Data, privacy & residency — where your data is held (application and database on Hetzner in Nuremberg; Aria on Mistral in Paris under a commercial agreement with no training on your data), a residency statement you can show your team and put in your DPA, a data export, and workspace deletion.
  • API keys & webhooks — scoped ak_ keys for the machine API and the MCP server, and outbound webhook endpoints. See Machine API and the MCP server.
  • Integrations — the planned directory, identity and task integrations. The four live read-only OAuth evidence connectors (Drive, SharePoint, GitHub, Jira) are connected from Evidence → Connectors, not here.
  • Notifications — which channels and which events notify you.

Compliance and account

  • My acknowledgements — the disclaimers and declarations you have accepted (the working-draft acknowledgement on first export, Aria's disclaimer), with dates.
  • Referrals — invite peers to Veritome.

Where the audit log went

The audit trail was a Settings tab; it is now a screen of its own under Prove it — Audit trail — with the integrity banner and the CSV export on it.