Security for your IT team
Glow Up redesigns a copy of your Qlik Cloud app in your own tenant and checks that every chart still gives the same numbers. It never writes to your original app.
In short
- Where it runs. Your organisation has its own runner, on Fly.io in London, shared with no other client. The runner has no public address. Only the connector reaches it, over a private network.
- How it reaches Qlik. Through one OAuth machine-to-machine client that your Tenant Admin creates, tied to one named Glow Up user and the spaces you choose. Deleting that OAuth client switches everything off at once.
- What leaves your tenant. App structure (sheet and chart titles, measure and dimension definitions, field names), the figures charts display, and pictures of the redesigned sheets. Row-level data, data files, data connections and source-system credentials do not leave.
- AI. The design steps use Anthropic's Claude API. Sheet pictures and app metadata go to it, and row-level data does not. The security pack sets out what is sent.
- People. Your users sign in with Microsoft or Google. Glow Up holds no Qlik passwords or user tokens.
What the runner can and cannot touch
It can
- Sign in as the one Glow Up user, with a Professional entitlement.
- Make, edit and tidy copies in your Glow Build space, where that user is Can manage.
- Read the source spaces you choose, where that user is Can view.
- Work on only the apps on the list you approved at install, and refuse any other.
- For a restyle only, upload a theme through a second OAuth client.
It cannot
- Write to your original app.
- Act as a Tenant Admin, or change data connections, reloads, load scripts, users or API keys.
- Read anything in a space the Glow Up user has no role on, including other people's personal spaces.
- Reach row-level data, QVDs, data files or section access rules.
- Keep a change that fails the values check, because it is rolled back.
How the install works
Nothing is installed in your network. Your Qlik admin does the work in your own Qlik Cloud tenant, in this order.
- Qlik, about 15 minutes. Add a user such as glowup@yourcompany with a Professional entitlement. Create a shared space called Glow Build and make that user Can manage. Give the user Can view on each shared space whose apps may be glowed up. Check the Reporting service is on, because sheet pictures need it. Create a machine-to-machine OAuth client with scope
user_defaultand user impersonation allowed. - The AI model, about a minute. Use your own Anthropic key, which keeps the model data under your own agreement and billing. Or BB Data Services supplies one, from a workspace used for your organisation alone.
- People, about two minutes. Name your approvers (one or two) and the people who can ask.
- Go live. The licence is set up from values that have just been checked, BB Data Services runs the health check, and your users add the connector.
Your Qlik secret and AI key are checked and then held only as encrypted Fly.io secrets for your runner. They never appear in email, chat, documents or source control. A BB Data Services operator could read them on the machine, and the security pack says so.
Sign-in, approvals and report links
- Sign-in is OAuth with Microsoft or Google. The connector checks each token's signature, expiry, issuer and audience, and refuses an email that is not on your organisation's list.
- A run is visible only to the person who started it.
- Anything that starts a run or spends money needs a confirm step, and a new app also needs an approver's yes by email. Approvers are named at onboarding.
- Every action goes into a hash-chained audit log, so a later edit to a row is detectable.
- The connector limits each person to 60 tool calls a minute and ten starts an hour.
- A report link carries one opaque token that shows no email and binds the run, its owner and an expiry. A link given in chat works for 24 hours, and the link in the ready email for 7 days. The report page loads nothing from anywhere else.
Retention and leaving
Run records, working files, sheet pictures and reports stay on your runner. The glowed-up copies sit in your own Glow Build space, so you keep or delete them as you like.
At the end of the contract BB Data Services revokes the licence and every user, destroys your runner and its disk, and deletes your sign-in records. You then get a signed offboarding receipt. If you ever suspect a problem, delete the Glow Up OAuth client in your Qlik Management Console, and Glow Up stops reaching your tenant at once.
Incidents: glowup@bbdataservices.com, or Brian Booden at brian@bbdataservices.com.
The full pack
This page summarises our security pack for client IT teams. The full pack lists every kind of data and where it goes, the subprocessors, the access model, isolation, retention and deletion, and how incidents are handled. The pack and the install runbook are shared on request.