These panels control what a Connect Any API connector may call and which data it may read: the hosts its recipe can reach, the streams discovery finds, and the data access grants that let the recipe read rows from a Lake or Warehouse object. You meet them in the connector wizard and in the recipe editor. For the connector end to end, see Connect any API; for the recipe itself, see The recipe editor.
A recipe can call only the hosts you approve. You approve them under Hosts, on the Connection step of the wizard and on the config node of the recipe editor.
While the list is empty it reads "No hosts yet. The assistant adds the API's host when it writes the recipe; you can pre-approve one here."
A pending host keeps the Connection step open with "Approve the pending hosts below - the recipe can only call approved hosts.", and the recipe cannot move on until every host is approved or revoked. Every change confirms with "Host approved" or "Host revoked", or fails with "Failed to approve host" or "Failed to revoke host".
If the connector already has data access grants, approving a host asks first: Also send granted data to these hosts? The dialog explains "This connector has data access grants. Approving the hosts pins every active or broken grant to them as well." and lists each affected grant, for example "Grant {name}: values of {columns} from {object} will also be sent to {hosts}". A broken grant gets its own line: "Grant {name} (broken): once it is restored, values of {columns} from {object} will also be sent to {hosts}".
Click Approve and send to approve the hosts and pin the grants. Revoked grants are not pinned.
Streams are the data sets the recipe can return. Discovery fills the Streams step of the wizard and the streams node of the recipe editor.
| Column | What it shows |
|---|---|
| Stream | The data set. Type in Filter streams… to narrow the list. |
| Origin | Declared when the recipe names the stream, Discovered when discovery found it. |
| Columns | The number of columns found; they are inferred on save and sync from a sample. |
| Lake | Imported once the stream is a Lake table, or Not imported. |
| Load | Not loaded yet, Loading, Loaded (with the row count and time) or Failed (with the error). |
Before anything is discovered, the panel reads "No streams yet - Save and sync to validate the recipe and discover streams." With no manifest it reads "No streams - the recipe has no manifest yet.", and if discovery finds none while the recipe declares none, it reads "The recipe declares no streams and discovery returned none."
A grant lets the recipe drive its requests from the rows of one Lake or Warehouse object; the recipe reads them as the stream grant_{name}. Only the admin role sees this section; see Who can do what in the Lake. For the grant's lifecycle and limits, see Data access grants.
The Data access section lists every grant with its state, Active, Broken or Revoked, and a summary such as its row count, date column or cap. While it is empty it reads "No data access yet. A grant lets the recipe drive its requests from the rows of one Lake or WH object. PII columns are sent as tokens."
To stop a grant, click Revoke and confirm Revoke data access "{name}"?: "Loads that still reference the stream grant_{name} fail from the next run. The grant stays in the audit log." The button is hidden on an already revoked grant. Actions confirm with "Data access "{name}" granted" or "Data access revoked", or fail with messages such as "Could not grant the data access" or "Could not revoke the data access".
Because the connector has live grants. Approving the hosts pins every active or broken grant to them, so granted columns will also be sent to the new hosts. Review the listed grants and click Approve and send only when that is what you want. See Data access grants.
No. Only Active and Broken grants are listed and pinned; revoked grants are left as they are.
Only users with the admin role see it. Ask your administrator to give you that role; see Who can do what in the Lake.
You must type the object's exact name under Type the object name to confirm first. The box shows the name as its placeholder, and the input resets every time the dialog opens. Grant access becomes available when the typed name matches exactly.
Yes. Type it under Add host and press Enter, with an optional port. The recipe can call only approved hosts, so a host approved now is ready when the recipe needs it. If the connector has grants, approving still asks the pinning question first.
The stream is imported, but its table has never been loaded. Data lands only when the table is loaded, either by hand from the Lake or by a workflow; the badge's tooltip says so. See Run, stop and troubleshoot loads.
After a stream is imported, its columns belong to the Lake table. The Schema button is disabled and says "This stream is imported - edit its columns in the Lake table." Open the table from the Imported link and edit its columns there.
The recipe or its settings changed since the last discovery. Click Refresh streams in the recipe editor, or Save and sync, which saves, validates and rediscovers. The rows update when discovery finishes; nothing is loaded into the Lake by this.
The badge marks each PII column of the object. Grants send PII columns as tokens, never as raw values, so the API never receives the original value.
A column name is blank, or a save is already running. Fill every name, or wait for the current save to finish, and the button becomes available.
The dialog notices. It reads "The approved hosts changed while this dialog was open. Review the new host list below, then confirm again.", re-lists the hosts, and asks you to confirm on the new list.