Shuntline›Solutions›Hub›Documentation

Shuntline Hub · documentation

Install, connect, review

For Snowflake administrators, solution teams and security reviewers: how to install Shuntline Hub, how solutions ask it who can do what, and how it is built and secured.

← Shuntline Hub: what it does and why

Installation

The Hub is a free Snowflake Native App, available on the Snowflake Marketplace. A Snowflake administrator installs it from the listing and sets it up once.

  1. 01 · INSTALL

    Install and approve

    Install the app from its Snowflake Marketplace listing into your account and approve its two privileges, each explained at install.

  2. 02 · MAP ROLES

    Grant the Hub's roles

    Grant the Hub's application roles to your own roles: administrators, auditors, users, and the role each solution runs as.

  3. 03 · START

    First administrator

    Become the first Hub administrator: one SQL command.

  4. 04 · ORGANISE

    Teams and access

    Open the console from Snowsight, add your solutions or load the sample data, create teams, give access.

Architecture

For your Snowflake administrators and security team. Everything runs in your account, inside Snowflake: no container, no Shuntline-hosted service, no outbound connection.

Shuntline Hub architecture Inside the customer's Snowflake account, the user opens the Hub console from Snowsight after signing in to Snowflake. The console is a Streamlit app inside the Native App; it runs SQL on the app warehouse, which executes the Hub's procedures and functions over its data, and reads the account's users while it is in use. Shuntline solutions call API.AUTHORIZE and API.LOG_EVENT with the solution_runtime application role. There is no container and no outbound connection. Customer Snowflake account UserSnowsight, afterSnowflake sign-in Native App SHUNTLINE_HUB ConsoleStreamlit, inside Snowsightrole hub_user No containerno endpointno outbound connection SQL App warehouseruns the console's queries Logic & contractprocedures, secure functions Schema core teams · grants · audit reads users while in use Snowflake users ACCOUNT_USAGE.USERS Shuntline solutionsother apps, same account API.AUTHORIZE · API.LOG_EVENT application role solution_runtime

The contract for solutions

ObjectPurpose
API.AUTHORIZE(solution_id, user_name)Roles, scopes and teams of one person in one solution.
API.POLICY_VERSION()Increases with every change; lets a solution drop its cache early.
API.EFFECTIVE_ACCESSEveryone's access, for batch use.
API.TEAM_MEMBERS(team_id)Members of a team and its sub-teams.
API.LOG_EVENT(solution_id, user_name, action, detail)Add a sensitive action to the Hub's audit log.

Application roles: HUB_ADMIN, HUB_USER, HUB_AUDITOR, and SOLUTION_RUNTIME for solution services, never for people.

Security

Snowflake authenticates every user, the Hub checks every role, and every write is validated and audited in the same transaction. No secrets to hand over, nothing stored in plain text.

Authentication

Snowflake first

The console opens inside Snowsight, so every user has signed in to Snowflake. It takes the user's identity from the Snowflake session, never from anything the browser sends.

Authorization

Checked on each action

Only roles holding hub_user open the console. Administration pages need the Hub's admin or auditor role, every change the admin role.

Solutions

A narrow contract

Solutions call the Hub with the application role solution_runtime, which can only read answers and write audit events.

Writes

Validated and audited

Every change goes through a validated procedure, written with its audit event in one transaction. The last Hub administrator cannot be revoked.

Agents

The caller's rights

Agents run with the caller's rights: Snowflake's role grants, row access policies and masking apply as for the person.

Served by Snowflake

Nothing external

The console runs under Snowflake's own content security policy: no external script, style sheet or font, no outbound call, no secret to manage.

Your data

DataSourceWhy
User name, display name, email, user type, disabled flagSNOWFLAKE.ACCOUNT_USAGE.USERSFind people to give access to; mark disabled the people disabled in Snowflake.
Current user nameThe Snowflake session the console runs inIdentify the console user.
Teams, memberships, grants, solution description files, audit eventsEntered by your administrators, or by solutions through API.LOG_EVENTThe Hub's purpose.

The Hub keeps no copy of the account's users: a person is recorded only when given access or added to a team. All of it stays in your account. Nothing is sent to us or anywhere else. No AI model is used or trained by the Hub.

Two privileges, both explained at install

PrivilegeWhy
CREATE WAREHOUSEA small warehouse for the console's queries.
IMPORTED PRIVILEGES ON SNOWFLAKE DBRead the account's user list while the console is in use: find people to give access to, keep known people up to date.
Shuntline Hub

The landing zone, and one set of access rules

What the Hub does for business users, administrators and AI agents, and how it fits the reverse-CRM experience.

Back to the Hub overview →vision · capabilities · AI agents · FAQ

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
Book a demo Write to us with your company, your Snowflake region and the solutions you run.