Set up Claude in about 5 minutes, understand how our files are organised, and get the keys to your clients. Do this one first.
Read this first · plain English · no tech knowledge needed
What is all this? The whole thing explained simply
You do not need to understand code, "tech", or how any of this is built to do brilliant work here. But it helps to know roughly what's happening behind the scenes, so none of the words look scary. If you've never heard of GitHub or "commit" or "deploy" — perfect, this is written for exactly you.
🗄️
Start with one idea: GitHub is a shared filing cabinet in the cloud. All our client work lives inside it — online, not on your computer. Everyone on the team opens the same cabinet, so you always have the latest version of everything. That cabinet is called GitHub. Our cabinet is the Team Vault. That's it — that's the big scary word handled.
The magic bit — you can never lose or break anything
You know how Google Docs keeps a history, so you can scroll back to how a document looked last Tuesday? GitHub does that for everything — every file, forever. Every time work is saved, it quietly keeps a dated snapshot with the name of who did it. That's called version control. It's the reason you can experiment freely: any mistake — wrong edit, deleted the wrong thing — rolls back in seconds. Nothing is ever truly gone.
What happens to one change — start to finish
Say you update a client's landing page. Here's the journey that change goes on behind the scenes. Claude does every single step for you — you just talk in plain English. You only need to recognise the words when they pop up:
✏️
You make a change
You tell Claude what you want in normal English. It edits the actual files for you.
📸
Commit = save a snapshot
Like hitting "save" — but it keeps a dated photo of exactly how things looked at that moment, that you can always come back to.
⬆️
Push = send it up to the cabinet
Uploads your saved work to GitHub so it's safe off your screen and everyone can see it.
🌿
Branch = your own private copy
Your work happens on a private copy, so you're never messing with the real live version while you tinker. Like editing a duplicate of a document before replacing the original.
🔗
Preview = a private test link
A test version of the page that only you and Tom can see — so you can check your change before the public ever does.
🙋
Pull Request = "please check my work"
You raise your hand: "I'm done — here's my copy, please review it." It goes to Tom. (Often shortened to "PR".)
✅
Merge = Tom approves it
Tom checks it and blends your copy into the real version. This is the moment your work becomes official.
🌍
Deploy = it goes live
The website publishes automatically the second Tom approves. Done — the public can now see your change.
💬
You never type any of these words, or any "commands". You just say something like "save this and get me a preview link" — and Claude does the commit, the push, the branch and the pull request for you. This page is only so you know what's going on when you see the words.
The words, in one place
Bookmark this. Whenever a word confuses you, it's here in plain English.
GitHubThe shared filing cabinet in the cloud where all our work lives. Online, always up to date.
Team VaultOur specific cabinet — the folder of all client work you have access to.
RepoShort for "repository" — just a fancy word for one project's folder inside GitHub.
Version controlThe auto-history. Every save is kept forever with your name — so anything can be undone.
CommitSave a snapshot. A dated, labelled save-point you can return to.
PushSend your saved work up to the shared cabinet so it's safe and visible.
BranchYour private working copy, so the live version is never at risk while you work.
Pull Request (PR)"Please check my work." Sends your copy to Tom to review and approve.
MergeTom approves and folds your work into the real version. Now it's official.
DeployPublish to the live website the public sees. Happens automatically when Tom approves.
PreviewA private test version of a page, to check it before it goes public.
Live / ProductionThe real, public version the client and their customers actually see.
What you'll use
Claude Code on the web — in your browser
You work in Claude Code on the web at claude.ai/code. This is Claude running in Anthropic's cloud — connected straight to our shared files on GitHub. You give it instructions in plain English; it builds and edits the real files for you.
🖥️
Nothing runs on your computer. No installs, no terminal, no downloading files. Everything happens in the cloud. Your personal laptop and your personal data stay completely separate from client work — you just open a browser tab and talk to Claude.
One-time setup — about 5 minutes
Tom sends you two invites: one to Claude (your own login/seat) and one to the Team Vault on GitHub (our shared client work).
Make a GitHub account if you don't have one (free, 2 mins), then send Tom your GitHub username so he can add you.
Accept both invites from your email.
Go to claude.ai/code in your browser and sign in.
Connect GitHub when asked. You'll see attain-digital-team-vault appear — that's your workspace. Done.
🔒 claude.ai/code
Your workspace after setup:
Project connected → attain-digital-team-vault
A chat box where you type what you want. That's it. You never leave this page.
⛔
You will never use a "terminal" or install anything. If a guide ever tells you to open a terminal or run a command on your own machine — stop, that's not our setup. Everything you need is inside claude.ai/code.
The mental model · 20 seconds
The Vault is a ring of client boxes
All our client work lives in one place — the Team Vault — split into a folder per client: clients/wiltshire-energy/, clients/eco2u-nw/, and so on. You'll only ever work inside the clients you've been given the key to. Everything about a client — their emails, pages, brand kit, notes — lives in that client's box.
🗂️ One folder per client
Open a client's folder and everything for them is right there. Never mix two clients in one task.
🔑 You see your clients only
Tom grants you keys per client. No key = you can't see that client. Simple and safe.
💾 Nothing gets lost
Every change is saved with your name on it and can be rolled back. Build freely — you can't break anything permanently.
How you get access to a client
You ask → Tom approves → you're in
You can only work on clients Tom has unlocked for you. When you need a new client, or a credential (a login, an account, an API key to a client's tools), you never store or hunt for it yourself — you request it, and Tom ticks the approval.
🙋
1. You requestAsk for the client or credential you need — in the app, or message Tom directly.
→
👑
2. Tom approvesHe ticks your name against that client in the access console.
→
✅
3. You're inThe client's folder and data unlock for you instantly. Untick = access gone.
🔐
Credentials never live on your computer. Client logins, passwords and account keys are never saved to your machine or pasted into notes. If a task needs one, you request access and it's handled centrally — or Tom does that step for you. This protects the client and you.
Two things you might request
Access to a client
"Can I get access to Eco2u? I'm doing their May email." → Tom ticks Eco2u → the folder appears for you.
A credential / account
Need to log into a client's ad account or CRM? Don't ask for the password. Ask Tom to grant the access or do that step — the login stays off your machine.