Connector and export rules
Business Summary: Connector and export rules ensure action connector writes and sensitive data extracts require the right approvals — so external systems and bulk exports stay under governance, not silent automation.
Connectors link Nimbus to CRMs, ERPs, warehouses, and document systems. Intelligence connectors read data; action connectors write or execute changes. Governance focuses on writes and exports that carry compliance risk.
Note: Org-wide connector rule editor on Governance is planned. Today, Critical HITL on workstreams and Confirm & run write toggles enforce most write gates.
How this fits in Nimbus
Connector rules sit in the governance stack alongside HITL presets. Any proposed write passes through Confirm & run opt-in, Critical sign-off, and (when policy requires) dual approval before execution.
flowchart LR
Plan[Plan run] --> CR[Confirm and run write toggles]
CR --> Run[Agent executes]
Run --> Crit{Critical HITL?}
Crit -->|Yes| SO[Sign-off]
SO --> Write[Action connector write]
Export[Bulk export] --> Pol[Export policy]
Pol --> SO
Action connector writes
Any proposed downstream write in Plan mode — update CRM, post to Slack, push to ERP — should pass through Confirm & run (you opt in to specific write actions via checkboxes), Critical HITL (sign-off before execution), and Strict dual approval when policy requires two approvers.
Writes never fire silently when governance is enabled.
Action-write gate checklist
| Gate | Where it appears | What it blocks |
|---|---|---|
| Confirm & run write toggles | Plan mode before execution | Unchecked actions never run |
| Critical HITL | Collaboration rail HITL review | External write until approver signs off |
| Strict dual approval | Second approver on Critical | High-risk ERP or CRM updates |
| Org export policy (partial UI) | Governance → export rules (planned) | Bulk customer or financial extracts |
Cross-reference approvals in Audit and History — committed writes should appear as decision events with approver identity.
See Intelligence vs Action connectors.
Export rules
Export rules govern bulk extraction of data from Nimbus or connected systems — for example, downloading customer lists, financial extracts, or wiki vault exports.
Policies may require admin approval before large exports, logging to Audit & History (when wired), and blocking exports for guest tier users.
Org export policy UI is partial; treat sensitive exports as Critical operations until rules are explicit.
Linking rules to governance teams
Governance empty state tip: "Link governance rules to connector and export actions."
| Team | Example rule |
|---|---|
| Brand & Legal | All public messaging connector writes need Legal approver |
| FP&A Office | ERP journal writes dual approval |
| Operations | Warehouse export over 1000 rows needs admin |
Attach rules to governance teams when org UI is available.
Connector credentials vs policy
Binding a connector to a workstream does not grant every teammate credentials. Auth flows and org tier still apply. Policy controls whether an approved run may write, not who set up OAuth.
See Managing connections.
Example scenario
A RevOps workstream binds Salesforce as an action connector. At Confirm & run, the owner checks only the pipeline stage update action — not bulk export. Mid-run, Critical HITL opens; two approvers sign off. Activity shows Committed to Salesforce. A separate analyst requests a large CRM extract; export policy (when live) would require admin sign-off — today, treat it as Critical and coordinate manually.
What you'll see
What you'll see: Confirm & run Downstream write actions checkboxes; Critical checkpoint naming target system; Governance tips mentioning connector linkage.
FAQs {#faqs}
Q: Are intelligence reads gated the same as writes? A: Reads use connector permissions and org tier. Critical HITL targets writes and high-risk exports, not routine analysis reads.
Q: Can I disable all action connectors org-wide? A: Admins can avoid binding action connectors and leave write checkboxes unchecked. Formal org deny-list is planned.
Q: Do wiki syncs count as exports? A: Wiki sync from connectors is ingestion into Company Wiki — different from exporting Nimbus data outward. Both may need policy in regulated industries.
Q: What happens if I reject a write checkpoint? A: The write does not execute; agent may revise plan or stop. Activity logs rejection.
Q: Where are connector export rules documented for my organization? A: Your Nimbus administrator configures org-wide connector and export rules. See Human-in-the-loop for how approvals apply to writes.
Q: Can I approve writes without binding the connector first? A: No. Action connectors must be bound to the workstream and authorized before write actions appear at Confirm & run.