Zum Inhalt springen
DeutschlandGPT
Organization

Notifications

Choose who receives your organization's notification emails and set their subject lines

Some events send an email to your organization's administrators. Under Organization settings → General → Notifications you decide which of these emails go out, who receives them and which subject they carry. You need the permission Manage organization settings.

License request notification with switch, recipients and subject

E-mail policy

Under E-mail policy you choose which e-mails with your organization's content may leave DeutschlandGPT. It covers:

  • results of scheduled tasks and the notices about failed runs,
  • e-mails about workflows, such as a failed run,
  • e-mails that workflows or the chat send through a connected service: a mail through Gmail or Outlook, and an action that makes the service e-mail people, such as a calendar event with attendees, a public Zendesk reply or a Stripe invoice e-mailed to the customer. Whether such an action sends an e-mail is decided from its inputs when it runs: an event without attendees, an internal Zendesk note or a Stripe invoice charged automatically does not count as an e-mail.
LevelWhat is allowed
No e-mailNone of these e-mails. Integrations that can send e-mail are blocked completely (see below).
Encrypted onlyOnly e-mails that can be encrypted with S/MIME for every recipient. Actions whose e-mail the provider writes itself (e.g. calendar invitations) and e-mails to recipients without a certificate are blocked.
UnrestrictedAll e-mails, encrypted when every recipient has a certificate.

Under No e-mail, every integration that can send e-mail is blocked completely, such as Gmail, Outlook, Google Calendar, Outlook Calendar, Zendesk or Stripe. It cannot be connected, and an existing connection cannot be used, not even for reading, searching or drafts: not in the chat, not in workflows and not in scheduled tasks. In your integrations it is marked “Blocked: e-mail sending is off” with the reason. Existing connections are not deleted and work again as soon as an admin chooses another level. Under the other levels the integration stays usable; only the actions the level does not allow are blocked.

Below the selection you see which integrations and actions the chosen level blocks. Sign-in, password and invitation e-mails are always sent – encrypted when a certificate is on file. The e-mails further down this page (licence and budget requests, news about new models) and invoices also go out under every level.

Before a stricter level is saved, DeutschlandGPT lists the workflows and scheduled tasks that can no longer run as before, with their owners. When a run is blocked, its history says: "Diese Aktion wurde von einem Admin Ihrer Organisation gesperrt. Bitte wenden Sie sich an Ihren Admin." A workflow step the level would block already says so in the workflow editor. When a workflow run is blocked this way, its owner also always gets an e-mail with that sentence and a link to the workflow, without its name or any content, even under “No e-mail” and even when the workflow sends no failure e-mails. Like every e-mail of a workflow, it counts towards the workflow's daily notification limit.

Whose organisation's settings apply to a workflow: for an integration action, such as sending an e-mail or creating a calendar event, and for an own server, the settings of the organisation of the person whose connection the step uses. For HTTP requests, authenticated requests and code, the settings of the workflow owner's organisation, also when a colleague starts the run.

A workflow run, a chat answer and a scheduled task read these settings once, when they start, and keep them until they end. A change takes effect from the next run.

Every change is recorded in the audit log with its old and new value and who made it.

Custom integrations & code

Three switches decide whether functions may be used where DeutschlandGPT cannot determine whether and where they send information:

  • Custom servers: your own MCP servers and WebDAV servers, in workflows and in the chat,
  • Code execution: code written by the AI, i.e. the code node in workflows, code mode and the sandbox in the chat,
  • HTTP requests: requests to freely chosen addresses, i.e. the HTTP Request node, authenticated requests and the AI fetching web pages or loading an image from a web address to edit it. Switched off, the AI can no longer fetch web pages or such images, not even as part of web search, because it could pass information on through an address it fetches; the search itself stays available. The AI's direct calls to a connected integration's own API also stay blocked then, so it cannot get around the integration's actions.

Switching one on shows a notice you confirm: We cannot secure these functions: we cannot determine whether and where they send information, or whether a contract covers it. Use them only if the AI's output is reviewed – for containing no confidential information, or for confidential information being protected sufficiently under § 203 StGB and the rules of your profession. Every change is recorded in the audit log.

As long as the e-mail policy is not “Unrestricted”, DeutschlandGPT blocks requests with credentials to the send endpoints of known mail services (such as Gmail, Microsoft Graph, SendGrid, Mailgun, Postmark, Amazon SES), including through HTTP Request nodes, authenticated requests and code mode. The policy still only fully applies with HTTP requests and Custom servers switched off: through a custom server or another service, a mail can get around it.

S/MIME certificates

On this page admins store the certificates your organization's e-mails are encrypted with:

  • The organization's gateway: if your organization runs an encryption gateway, store its certificate. Members without a certificate of their own then receive e-mails encrypted to the gateway.
  • Certificates for outside addresses: for an address outside your organization, such as a client's, store its certificate once. Every e-mail and every Gmail or Outlook send to that address is encrypted with it. The certificate must name the address. Members can also submit a certificate for an outside address under Account settings → Security. It is used only once an admin confirms it here: it is listed as Pending at the top and taken over with Confirm. Admins get an e-mail about it that names neither the address nor the member. Click the entry to see its fingerprint and check it with the recipient before you confirm. Only admins replace and remove certificates.

Once a recipient has a certificate, this applies in every organization: an e-mail through Gmail or Outlook to several recipients where only some have a certificate is not sent. Send it separately to the recipients with and without a certificate. The page points this out when a certificate is uploaded.

Members upload their own certificate under Account settings → Security. A certificate that expires within 30 days is marked; its owner gets an e-mail 30 and 7 days before it expires. An expired certificate is no longer used. Uploading and removing are recorded in the audit log.

The three notification emails

EmailSwitchWhen it is sent
License requestLicense requestsA member without a license asks for one via "Request license"
Budget requestBudget requestsA member has reached their monthly AI budget and asks for more
New AI modelsNew model announcementsA new AI model becomes available, so you can enable it for your members on purpose

Switching off License requests or Budget requests also means members can no longer send that request by email.

Choose recipients

Without any entries, all administrators of your organization receive the email (All administrators (default)). To send it to specific people instead, search for members under Recipients and add them.

You can also pick a group. Every member of that group receives the email, including people who join the group later, because membership is checked anew on each send.

Set the subject

Enter your own text under Subject, for example to make the emails easier to filter. Leave the field empty to use the default subject. Click Save when you are done.

Was this page helpful?