Technical handover / System map · LeadLift Marketing

The Editing Pipeline 1 walkthrough · code + make

This system takes a client's raw footage to a live ad. One card on one board carries each batch of ads from the first file to the launch. Fidel Guajardo owns it at LeadLift.

People Access, sharing and permissions For AI Point Claude here
System
Editing Pipeline
Pieces
1 walkthrough
Platforms
Code · Make · Drive
Built by
Icarus Growth

How the whole thing fits together

A client puts new videos or images in their Raw Footage folder in Google Drive. A scan finds the new files, and the server makes a card on the Editing Pipeline board. Paulo edits the ads into one folder. Fidel reviews them. The client sees them only when their review switch is on. At the end, Fidel uploads the ads to Ads Manager.

The scan runs every 12 hours, at 6am and 6pm Central. A person can also press Scan for new footage on the board. Each step posts in its own Slack channel. Four Make automations do the Google Drive work for the server.

Before · OnboardingOnboardingMakes the folders and the channel Before · AppScripts boardAn approved script waits
upload
Step 1 · Server + MakeFootage scan6am, 6pm or the button
card
Step 2 · AppFootage ReceivedOne card per upload
brief
Step 3 · AppTo EditPaulo gets the Edited folder
hand in
Step 4 · AppInternal ReviewFidel watches each ad
decides
Step 5 · SlackClient ReviewOnly when the switch is on Step 5 · AppRedo or changesBack to the editor
approved
Step 6 · AppReady To LaunchPosts the folder
by hand
Step 7 · FidelLive In Ad ManagerAds uploaded by hand
reads all
PendingBoard digestPosts to #creative-management
How to read this map: each solid box opens a page. Steps 1 to 7 share one walkthrough, so they all open the same page. The two boxes on the left belong to the other handover sites. Step 5 has two paths: the client sees the ads, or the ads go back to the editor. The dashed box runs today, but it has no walkthrough yet.
Not proven yet (as of 12 Oct)
• No real client has a Raw Footage folder linked yet. So the scan reads test clients only.
• Linking a real client's folder now makes cards from up to 14 days of old files. Wait for the small code change first.
• Make's plan has 10,000 operations a month. Each scan uses about 5, plus 1 for each folder. Many folders, twice a day, use up the plan fast.
• If you hire an editor, new cards still go to Paulo. That stays true until Claude changes the default.
• A server job that stops at its own time limit tells nobody.

The walkthrough

Start here. The page has the video, a short summary, every step, the Slack channels, and a table of what you can change safely.

Unit 01 · Code + Make
Editing pipeline: footage to live ad
From new files in Drive to a live ad, on one card.

Access, sharing and permissions

This section tells you who can open each part of the editing line. It also tells you how to add a person and how to remove a person. Keep this page up to date when your team changes.

Who can get in today

WhoWhat they can openHow they get in
Fidel Guajardo, FounderThe app and every board. Slack, as the workspace admin. Make and Google Drive, as the owner. The server's Modal workspace, as the owner.An emailed code for the app. His own logins for the other tools.
Paulo, CSMThe app, Slack, and the client folders in Google Drive (edit). Paulo is the default editor on new cards.An emailed code for the app.
Sterlin Phillips, Head of Media BuyingThe app, Slack, and the client folders in Google Drive (edit). His Slack id is not on the Team page yet, so the system cannot tag him.An emailed code for the app.
Chris Brown, Media BuyerThe app, Slack, and the client folders in Google Drive (edit).An emailed code for the app.
João Marcos Cascione, Media BuyerThe app, Slack, and the client folders in Google Drive (edit).An emailed code for the app.
Icarus Growth (Sheni Salami)The app, the code on GitHub, Make (an admin seat), the server releases, and every client folder in Google Drive (edit).2 addresses on the app's sign-in list. We remove our access when you tell us.

The app sends a 6-digit code by email. It has no passwords. An Active person on the Team page with an email can sign in. Today 5 people are Active. As of 11 Oct, no LeadLift person has signed in yet, so each person signs in once to prove it works.

Add a new team member

  1. On the Team page, add the person: name, email, job title, Slack id, client limit and status Active.
  2. Tell the person to open the app, type that email and enter the emailed code.
  3. Invite the person to LeadLift's Slack workspace.
  4. Add the person to the editing channels they need: #new-creative, #editor-updates, #creative-review, #amendments, #approved-creative, #pipeline-errors, #creative-management.
  5. Ask Fidel to share the Clients folder in Google Drive with edit rights.
  6. Put the person's Slack id on the Team page. Each new client channel then adds them by itself.
  7. Add the person to older client channels by hand.
  8. If the person is the new editor, ask Claude to change the default editor. Until then, new cards go to Paulo.
  9. If the person needs the Claude connector, ask an admin for a personal link.

Remove a person

  1. On the Team page, set the person to Inactive. They cannot sign in, and their connector link stops within 60 seconds.
  2. Remove the person from LeadLift's Slack workspace.
  3. In Google Drive, remove the person from the Clients folder.
  4. Also remove the person from each client folder that has a direct share. Drive does not do this by itself.
  5. If the person was the default editor or reviewer, ask Claude to change the default.
  6. If the person had GitHub access to the code, remove it.

Shared links and portals

Shared itemWho gets itHow to stop it
The client's Raw Footage folderAnyone with the link can add files. This lets a client upload with no Google account (Sheni's choice, 11 Oct). The link is a bookmark in the client's Slack channel.Fidel changes the folder's sharing in Google Drive. Tell Icarus Growth first: after the change, the client cannot upload.
The client's folder and its Edited folderThe client's email can view the client folder, so the client can watch each batch in the Edited folder. The client can also add files to Raw Footage and Lead Sheet.Fidel removes the client's email from the folder in Google Drive.
The ad review linkIt goes to the client's Slack channel at Client Review. It opens one batch of ads. Anyone with the link can approve the batch or send notes. It needs no sign-in.The link acts only while that card waits at Client Review. After the client answers, it changes nothing.
The client's private Slack channelThe client, through a Slack Connect invite. Client review posts go there.Remove the client from the channel in Slack. Do not archive or delete the channel, and keep the bot in it. If you do, client review posts stop and #sentry reports it. You can rename the channel safely. The system finds the channel by its id, not its name.
Icarus Growth's share on client foldersEach address in the Icarus Growth domain can edit every client folder.Ask Icarus Growth to remove this share from each client folder at the end of the handover.
This documentation siteAnyone with the address can read it. It holds no key, password or connector link.Ask Icarus Growth to take it down.

Claude connector

The connector lets Claude read the boards, clients, team and calls. On this board, it can also log, find, change and move cards for an admin. As of 11 Oct, nobody has used it on real work. Only Fidel has a link today.

RoleWhat it can do
AdminReads everything the app shows. Makes a change only after the person approves it. The log records each change under that person.
MemberReads only.

Today Icarus Growth makes each link and gives it to one person. After the handover, the named owner does this. The link shows one time only. To add it in Claude:

  1. Open Claude, then go to Settings, then Connectors.
  2. Choose Add custom connector.
  3. Name it LeadLift OS.
  4. Paste your personal link and save.
The link is personal, like a password. Anyone who has it acts as you. Never post it in a channel, a document or a screenshot. To turn a link off, set the person to Inactive on the Team page. It stops within 60 seconds. You can also ask a developer to replace the link.

The code

The code is in a private GitHub repository that Icarus Growth owns today. Sheni Salami is its admin, and 3 Icarus Growth developers can read it. Nobody at LeadLift has access yet.

The change guide does not name an owner at LeadLift yet. We write that name in before the move. The server already runs in Fidel's own Modal workspace, but Icarus Growth runs the releases today. A copy of each of the 4 Make automations is in the code folder.

  1. LeadLift makes or chooses a GitHub account or organisation.
  2. Icarus Growth transfers the repository to it. Its history stays.
  3. Give the named owner a release login for Fidel's Modal workspace.
  4. Do not move or rename the server. Three database rules call its address, and the board posts stop with no error.
  5. Check that the checks (lint and tests) run with no secrets.
  6. Write the owner's name and email in the change guide.
  7. Anyone who installed the Claude Code plugin adds it again from the new address.

Accounts and who owns each login

ToolWhat it does hereWho owns the login
ModalRuns the server, the scan schedule, the board digest and every web address.Fidel's workspace. Icarus Growth runs the releases today.
MakeRuns the 4 footage automations: list the files, move them, merge two cards, make the Edited folder.Fidel's account, on the Core plan (10,000 operations a month). Icarus Growth edits through a key. Sheni has an admin seat.
Google DriveHolds every client folder and all the footage.Fidel's Google account. Make's Drive connection needs a new sign-in before 11 Apr 2027.
SlackCarries every editing post and the client review link.Fidel is the workspace admin. Icarus Growth set up LeadLift's Slack app.
SupabaseKeeps the board, the cards and the sign-in.Not confirmed yet. Icarus Growth confirms this before the handover.
CloudflareHosts the app.Not confirmed yet. Icarus Growth holds a release key.
ResendSends the sign-in codes.Not confirmed yet.
GitHubHolds the code.Icarus Growth today. It moves to LeadLift at the handover.

The server keeps its settings and keys in Modal's secret store. This page names no value. The For AI file lists the setting names.

Sheni Salami
icarusgrowth.com