The Mothership

MUUS·THE MOTHERSHIP

Team workspace

Sign in to continue

MUUS team only — @muusmedia.com email required

m.

[ LOADING ]

m.

[ MOTHERSHIP / 05 ] / PROJECT TRACKER / v.05

CONNECT your TEAM

All projects, brands, and creators sync live across the team. Enter your shared Supabase workspace, or set up a new one in 5 minutes.

CONNECT TO WORKSPACE

WORKSPACE ID

SUPABASE URL

ANON / PUBLIC KEY

FIRST TIME? SET UP A NEW WORKSPACE

5-minute setup:

Go to supabase.com, sign in, create a new project (free tier is fine)
Open SQL Editor → New query → paste the SQL below → Run
Open Project Settings → API → copy "Project URL" and the "anon public" key
Pick any string for workspace ID (e.g. muus-team) and paste everything above
Share workspace ID + URL + anon key with your teammates

create table muus_kv ( workspace_id text not null, key text not null, value text, updated_at timestamptz default now(), primary key (workspace_id, key) ); alter table muus_kv enable row level security; create policy "kv all" on muus_kv for all using (true) with check (true); alter publication supabase_realtime add table muus_kv; -- Storage bucket for asset/file uploads (100 MB per-file cap) insert into storage.buckets (id, name, public, file_size_limit) values ('muus-assets','muus-assets',true,104857600) on conflict (id) do nothing; create policy "assets read" on storage.objects for select to anon using (bucket_id='muus-assets'); create policy "assets write" on storage.objects for insert to anon with check (bucket_id='muus-assets'); create policy "assets delete" on storage.objects for delete to anon using (bucket_id='muus-assets');

EST. 2019 · MUUS MEDIA · BUILT IN-HOUSE

NOTIFICATION CENTER

[ HOME ] Team dashboard. What we're working on this week, what we're shooting for, what just won.

GOOD MORNING

--

Wed May 6 · Week 19

[ 01 ] THIS WEEK

[ 02 ] MEETINGS & INVITES

[ 03 ] UPCOMING DEADLINES

[ 04 ] NOTEPAD PERSONAL

[ 05 ] REMINDERS

$

PRIVATE ledger

[ OWNER ONLY · LOCAL DEVICE ]

Admin (finance + contracts) is shared across all your devices on this workspace, locked behind your password.
Forgot? Reset and clear data.

[ PRIVATE / OWNER / DEVICE ONLY ] · Not synced to team · [ LOCK ]

// STUDIO FILTER

// FINANCE \u{1F512} owner-only

OVERVIEW

PIPELINE

INVOICES

BALANCES

[ BALANCES ] amount paid / amount left per project. Deposits roll up under their parent invoice. · shows invoiced projects only — drafts excluded

// OPERATIONS visible to the whole team

MUUS RATE CARD / SERVICE CATALOG ▸

[ MUUS RATE CARD ] service-level pricing & usage / buyout reference. Snackables pricing lives in the Snackables packages catalog.

OUTREACH SEQUENCES

[ SEQUENCES ] Cold outreach templates shared across the team. Enroll leads from the Leads view; edit templates here.

TEAM

[ TEAM ] Manage who is on the workspace, their roles, and access.

// CLIENTS brand & client registry

CLIENT REGISTRY

[ CLIENTS ] legal entities, registered addresses & authorized signatories. Legal names appear ONLY inside contract & invoice PDFs — never in front-facing views.

One-time setup, ~20 minutes. After this, you and your teammates can connect Google Calendar with one click. Required by Google for any app that touches their APIs.

01

Open Google Cloud Console

Go to console.cloud.google.com. Sign in with your Google account.

02

Create a new project

Top of page, click the project dropdown → NEW PROJECT. Name it "The Mothership" → CREATE. Wait ~10 sec for it to provision, then make sure it's selected in the top dropdown.

03

Enable the Google Calendar API

Open this direct link. Click ENABLE. Wait a few seconds.

04

Configure OAuth consent screen

Open this link. Pick External → CREATE.

Fill in:

App name: The Mothership
User support email: your email
Developer contact email: your email

SAVE AND CONTINUE.

On Scopes page: click ADD OR REMOVE SCOPES, find and check ALL THREE: https://www.googleapis.com/auth/calendar, https://www.googleapis.com/auth/spreadsheets, https://www.googleapis.com/auth/drive.file, hit UPDATE. SAVE AND CONTINUE.

On Test users page: ADD USERS → add your email + every teammate's Google email (Frida, Elijah, etc.). SAVE AND CONTINUE.

05

Create OAuth Client ID

Open this link. Click CREATE CREDENTIALS → OAuth client ID.

Application type: Web application.
Name: The Mothership Web.

Under Authorized JavaScript origins: ADD URI → paste your tracker URL exactly (e.g. https://muusagency.github.io). No trailing slash.

Under Authorized redirect URIs: ADD URI → paste the same URL.

CREATE.

06

Copy the Client ID

A popup shows your Client ID (looks like 1234567890-abc123def.apps.googleusercontent.com). Copy the whole string.

Paste it back in the tracker: Settings → GOOGLE CALENDAR → CLIENT ID field → SAVE.

07

Connect & you're done

Click CONNECT GOOGLE CALENDAR. Google will pop up a sign-in. Pick your account, grant access. The tracker now reads/writes to your real Google Calendar.

Each teammate does step 7 only (you do steps 1-6 once for the whole team). Each teammate connects with their own Google account.

Why all this?

Google requires every app that accesses their APIs to be registered in Cloud Console. There's no way around it. The good news: it's free, takes 20 min, and you only do it once. After that, the tracker becomes a real calendar app.

"Test users" limit

Google limits unverified apps to 100 test users. For a 5-person team, you don't need verification. Just add everyone as test users in step 4. If MUUS grows past 100 people, you'd submit the app for verification (4-6 weeks, requires privacy policy).

ASSIGNEE

DUE

PRIORITY

STUDIO

SUBTASKS

NOTES

COMMENTS

PACKAGES

No packages tracked.

ACTIVITY LOG