Connectors & data governance: shared data, on your terms

Some things belong in one place, not copied into every app: your customer list, your product catalogue, a payment or CRM account. On Croft, a connector lets your apps share a data source or reach an outside tool — Stripe, HubSpot, your own API — without the keys ever living in an app’s code. You add each tool’s key to Croft once; it’s kept locked away, and your apps use the connection through a gate that adds the key only on the way out. A leaky app can’t spill a key it never had.

For teams, the important word is allow. Not every data source should be open to everyone. Mark a sensitive connector — payroll, your customer database — as needing approval, and anyone can build an app that asks to use it, but it stays switched off until an admin says yes. You can approve a connector for a specific app or a specific person, not the whole company, so new starters and one-off tools don’t get the keys to everything by default.

And it’s all on the record. Every connector, approval, and use is logged, so if someone asks “who can reach our billing data?” the answer is a page, not a guess.

That’s the quiet difference between a toy and a tool a business can rely on: shared data where it helps the work, a guardrail where it protects the business. It’s the same least-privilege principle that runs through the rest of Croft — everything starts locked, and you open exactly what you mean to.

Your assistant sets connectors up for you; you just say “connect our Stripe account.”

See connectors → · Read the docs →

More from the blog