Shuntline Hub · the landing zone on your Snowflake
Start from the data, act from there
hub /hʌb/ · noun The place where business users land on their CRM referentials and data in Snowflake, and the one set of rules that decides who can do what, in every solution and for every AI agent.
The data warehouse used to be the end of the cycle: operations ran in the CRM, data was copied out, analytics came after the fact. Shuntline turns it around. CRM referentials and data land in Snowflake first; business users start there, focused on their own data; operations are triggered from there, in specialized solutions on Snowflake or in the tools outside, like a CDP or the CRM.
The warehouse is the beginning
Not the end of the cycle to feed analytics, but the place where focused business data is grasped and operations are triggered.
Yesterday · the warehouse ends the cycle
With Shuntline · the warehouse starts it
How it fits
People sign in to Snowflake and land in one place. From there they work their data, ask an assistant, and go down to the solution that does the job. Every way in follows the same rules, decided in the Hub and enforced by Snowflake.
Shuntline Hub
Who can do what across your solutions: teams, roles, data scopes, reviews and audit. A free Snowflake Native App, available on the Snowflake Marketplace.
The Hub →AI agents
Snowflake CoWork, Cortex Agents and MCP clients work on the solutions' data within each person's access. Set up when a solution is installed.
AI agents →Landing zone
A front door for business users: CoWork artifacts and dashboards across solutions, an assistant, and links down to every solution, on Snowflake or outside.
Landing zone →Who can do what, decided once
A Snowflake Native App, installed in your own Snowflake account. Snowflake authenticates people; the Hub authorizes them. Solutions store no users and no permissions of their own: they ask the Hub “what can this person do here?” and apply the answer. The Hub is free and optional: you can keep your own MDM or access referential, or rely on Snowflake's native roles when the use case needs nothing more. The Hub is free and optional: you can keep your own MDM or access referential, or rely on Snowflake's native roles when the use case needs nothing more. The Hub is free and optional: you can keep your own MDM or access referential, or rely on Snowflake's native roles when the use case needs nothing more.
Solutions and my access
Each person sees the solutions they can open, with their role in each and a link to open them, and a “My access” page with their roles, data scopes and teams.
One console
Teams, people, roles and scopes per solution, the solutions catalogue, access reviews and the audit log, in one place, opened from Snowsight.
One question to ask
A new solution, standard or custom, is added from its description file, with no change to the Hub. Client libraries for Python and TypeScript, with caching built in.
Key capabilities
| Teams | Teams and sub-teams that mirror the organisation (Marketing › France, Sales › Spain). Access given to a team reaches its members and every team below it. |
|---|---|
| People and leavers | Follows your Snowflake account: someone disabled in Snowflake, or in the identity provider behind it, loses access to every solution at once. |
| Roles and data scopes | Each solution declares its roles (administrator, router, viewer…) and its scopes (country, brand, channel…). Access is a role, optionally limited to some scope values. |
| Dated access | Holiday cover that ends by itself, an agency whose access starts on its contract date. |
| Any solution instance | Add a solution from its description file, preview what an update changes, disable and re-enable it. Roles still held by people are never silently deleted. |
| Access review | Who has which access, through which team, exportable for periodic reviews. |
| Audit log | Every change, with who made it, when, and the before and after. Solutions add their own sensitive actions to the same log. |
| Sample data | One click loads a fictional company, with four solutions, twelve teams and twenty-four people, to see every screen at work before going live. |
How access adds up
One authorization layer that even your AI agents obey
Snowflake CoWork, Cortex Agents and MCP clients now work directly on company data. Each is a new way in. The Hub makes sure they follow the same rules as everyone else, with nothing to develop per agent or per solution.
Snowflake signs people in
Through your identity provider. Agents act as the person using them, never as a shared account.
The Hub decides
Teams, roles and data scopes, managed once, for every solution and every agent.
Snowflake enforces
On the solutions' data, every query, from a dashboard, SQL, an app or an AI agent, returns only what the person may see.
Ask across solutions
In Snowflake CoWork, a business user asks about leads, consents or campaigns and gets answers within their own scope. A sales manager for France sees French leads, nothing else.
Act through the solutions
Agents change data only through the solutions' own actions, exposed as tools through Snowflake's managed MCP server. Each action checks the Hub first and is recorded in the audit log.
Included, same rules
Solutions keep their operational records in hybrid tables, in Snowflake itself, so analysis and AI read them in place, under the same rules.
A landing zone for business users
Snowflake is built for data teams. Shuntline brings business users onto it, with an experience made for their daily work rather than for data engineering, built with each customer.
One place to land
The Hub knows which solutions each person can use and where they live, and links down to every one of them.
CoWork artifacts, made for your teams
Entry views built as Snowflake CoWork artifacts and dashboards across solutions: today's leads, consents to handle, campaigns live in each market. Shared with a team, on live data, each showing a person only their scope.
Snowflake CoWork
Questions, summaries, “what needs my attention today?”, and actions through the solutions, all within the person's access.
Specialized solutions
Shuntline solutions keep their own screens for operational tasks on Snowflake; tools outside, such as a CDP or the CRM, receive what they need to act.
Screens for the daily work, an assistant for everything else, one set of rules for both.
Why it matters
For the people who answer to auditors, and for the people who want AI on their data without new risk.
One answer to “who can see what?”
Including what AI agents could reach.
AI adoption without new risk
Turning on an agent doesn't widen anyone's access.
Less to maintain
One place to grant, review and revoke, for every solution and every agent.
Everything stays in Snowflake
No copy of users or data elsewhere, one platform to secure.
Business users at home
A landing zone and an assistant, instead of a data engineering tool.
Free, and light to run
The Hub is free; it uses a small warehouse on your account, and nothing runs on a schedule.
Questions about the Hub
Short answers to what CRM owners, Snowflake administrators and security teams ask first.
What is a reverse-CRM experience?
It moves users and records upstream. People start from their enterprise data in Snowflake, land in one governed space, Shuntline Hub, where they view, analyze or ask Snowflake CoWork, then go down to the solution that does the job: a Shuntline solution on Snowflake, or a specialized app such as Salesforce or a CDP, which receives only what it needs to engage. Reverse ETL already made the warehouse the starting point for marketing, building audiences there and activating them in ad, email and CDP tools; a reverse CRM applies the same logic to the CRM's users and records. Shuntline Hub → · Read the essay: The Reverse CRM →
Does any of our data leave our Snowflake account?
No. The Hub runs inside your account, with no container and no outbound connection. We have no access to your data.
Do we manage another set of passwords?
No. People sign in to Snowflake, usually with your company's identity provider. The Hub never sees a password.
What happens when someone leaves?
Disabling them in Snowflake, or in the identity provider behind it, blocks their sign-in at once, so they lose access to every solution. The Hub then marks them disabled in its records, reviews and exports, with no manual step.
Can an AI agent see more than the person using it?
No. Agents act as the person using them, Snowflake applies the Hub's decisions on every query, and agents change data only through the solutions' own actions, which check the Hub first and are recorded in the audit log.
Can we give access for a limited time?
Yes. Each grant can have a start date, an end date, or both.
Can we limit someone to some countries or brands?
Yes, if the solution declares that scope. Scopes from several grants add up.
Can we audit who changed what?
Yes. Every change is recorded with its author, time, and before and after values, in your account.
Does it work with custom solutions?
Yes. Any solution that ships a description file and asks the Hub through its contract is added with no change to the Hub.
What about tools outside Snowflake, like a CDP or the CRM?
The landing zone links down to them, and solutions send them what they need to act, such as an audience or a converted opportunity. Access inside those tools stays governed by the tools themselves.
What does it cost?
The Hub is free. Like any Native App it runs on your Snowflake resources: a small warehouse billed by Snowflake, used only while the console is in use. Nothing runs on a schedule.
Do we have to use the Hub?
No. The Hub is a free, optional accelerator, delivered as a Snowflake Native App. Solutions also work with your own MDM or access referential, or simply with Snowflake's native roles when the use case doesn't call for teams and data scopes.
Add any solution instance
The Hub has no fixed list of solutions. An administrator adds each solution instance running in your account, whatever it is: Lead management, Opt-in, Campaigns & UTM, a second Lead management for another region, a custom solution. Its description file says which roles and scopes it understands; from then on, access to it is decided in the Hub.
Every lead onto the right track
One intake for every sender, filed by rules, routed to whoever works it.
Lead management → Opt-inIt records, you decide
A consent register and a privacy centre per person.
Opt-in → Campaign referential & UTMOne catalogue across every business unit
Campaigns, codes and UTM links, defined once.
Campaigns & UTM →See your organisation in the Hub
Bring the teams and roles you manage today across your solutions. We set them up in the Hub live, in a Snowflake account, and walk your administrators and security team through the architecture.
- A working session with the team that builds it
- Your teams, roles and scopes, set up on the spot
- Security review material on request