Skip to content

Integrations & Delivery Settings

What this screen is for

Integrations & Delivery is one of the eight purpose groups of Platform Settings, and it answers what your installation reaches outside itself: outbound mail, the licence store and the routing usage travels on, IP geolocation enrichment of sign-in records, and the marketplace gateway. Opening the group card lists four subgroups as cards — Email & Notifications, Licensing, Geolocation and RapidAPI Gateway, in that order. None of the four administers records of its own, so none has a screen of its own and all four are covered here.

Four values in this group can be written from this screen, and two of those four are secrets, so the editable, non-secret surface of the whole group is two values — both of them in Email & Notifications. Of the rest, some are owned by the deployment, some are read-only observations, and two are secrets somebody else manages.

What this group mostly holds is credential custody and connection facts, not tuning. The platform brings its own defaults and no customer credentials, so every connector here is inert until a deployment supplies one.

What must exist first

Platform Settings is a platform screen, reached in the platform context and served only to the platform tenant. Before you work here:

  • The permission to read platform configuration. It is what shows the Platform Settings sidebar entry at all and what loads the catalogue these cards count.
  • The permission to write platform configuration, for any change to a value. No value here is classified dangerous, so the third, dangerous permission is never asked for on any of these four screens.
  • A separate permission to read the delivery chain, for the Delivery tab of Email & Notifications. Holding platform configuration read does not carry it.
  • Separate permissions again to change the delivery chain, which the platform-configuration write does not carry and does not replace: on Delivery, the permission to write notification providers for saving and the permission to test them for a test send; on Per tenant, the tenant-provider write and test permissions. Write and test are independent, so you may hold one without the other. Only the platform super administrator holds them.
  • A platform audit-read permission for the Activity tab. Without it, Licensing, Geolocation and RapidAPI Gateway show no tab bar at all, because Configuration is then their only view.
  • A SaaS-hosted deployment for RapidAPI Gateway, which is withheld everywhere else.

Decisions you make here

Every card in this group carries a status chip rather than a row count, because all four are connectors. Three of them — Licensing, Geolocation and RapidAPI Gateway — derive that chip from the catalogue itself: the subgroup reads Active when at least one of its values carries a non-empty effective value that differs from its default, and Not configured otherwise, with a stored secret counting as set. Email & Notifications is the exception: it asks the platform for a delivery verdict, because it is the one subgroup here with a real delivery chain the platform can report on.

Email & Notifications

Two values, and the only tabbed leaf in this group. The outer bar offers Configuration, Per tenant and Activity; inside Configuration there are General and Delivery.

General holds both catalogue values: the display name shown beside the sender address, and the subject line applied to a notification that supplies none. Each applies to the next message sent, with no restart. Each refuses a line break, and that refusal is the point — a line break here would let extra mail headers be injected into every outbound message.

Delivery is not a settings table and carries no count. A mail, SMS or WhatsApp provider is a record with a lifecycle rather than a value, so its host, its port, its sender address and the primary-and-failover choice are all properties of that record. Its credential is sealed per provider and is not a catalogue entry, so nothing on this screen names it.

Per tenant provisions one tenant's own delivery chain from the platform side. The tenant is chosen from an explicit selector, so it stays blind provisioning rather than acting as that tenant. Its save and test controls follow the tenant-provider permissions above, each on its own.

Licensing

Values in three sections: where the licence store is, how usage is routed to it, and its secrets. Every one of them is read-only. There is no editable licensing value left in the catalogue, and a write against any of them is refused as a method that is not allowed.

The two topic entries deserve a second look, because they name the same event topic from two sides: one is the topic usage is published to, the other the topic the licence service consumes from. They agree by default and nothing keeps them in step, so a deployment that changes one and not the other stops usage reaching the licence service with nothing turning red. Read them together, and change them together in the environment.

The two secrets are operator-managed: the password of the licence database role, and the key that signs trial-licence usage records for tamper detection. Neither value is ever shown. What the entry tells you is whether one is stored.

Geolocation

Values in three sections: the master switch and asynchronous lookup, the provider API, and its resilience. Exactly one of them is writable here: the provider API token, a masked secret. Typing a new one replaces what is stored outright, applies without a restart, and is never echoed back to you.

The others split in two. Most are owned by the deployment — the master switch, the async completion timeout, the provider request timeout and the circuit-breaker values — and each of those entries names the deployment setting that sets it, which is where you change it. The provider base URL is a read-only observation.

A wrong or expired token is not detected when you save it. Every lookup then fails upstream, which both drops the location from the sign-in record and drives the provider circuit breaker open, so confirm one enriched sign-in after rotating. Rotate only while geolocation is enabled: with the feature on, a blank token stops the service from starting at all.

RapidAPI Gateway

One value: the shared secret the marketplace gateway presents on every proxied request. It is masked, and you can replace it here.

The subgroup is not offered on a customer-operated install. Its card, its sidebar node, its address and its command-palette entry are withheld together, and a deep link to it lands you back on this group's landing rather than on a hidden screen. It is also the one key in the whole catalogue the platform refuses by deployment type: on a customer-operated install a write is refused as not applicable, before any other gate is reached.

How it relates to other screens

The root of this surface explains what every screen below it shares: the posture filter, the search palette, how secrets behave, and when a saved value takes effect. Two other screens answer questions this group raises but does not decide — what your installation is connected to, and what the licence itself grants.

Where to read more