SquadSquadOpen Squad

User guide

Everything Squad does

In the order you are likely to need it — getting around, your cohort, your projects, messages, calls and your account. Search it, or read it straight through in about five minutes.

Getting around

The three areas of the screen, and the fastest way to reach anything.

Everything is two clicks away: cohorts and channels on the left, the conversation in the middle.
The layout
The left sidebar lists the main sections — Home, Chats, Channels, Direct Messages, People, Meetings, Calls, Files, Tasks, Projects, Project Lab, Forms and Learning notes (and Admin for Owners and Admins) — with your channels and direct messages under them. The top bar holds search, the + button, notifications, shortcuts to Meetings and Learning notes, this guide (the headset) and your account. The middle is whatever you have open.
Search anything
Press ⌘K (Ctrl+K on Windows and Linux) from anywhere to open search, or click the search box in the top bar. It looks across channels, people and messages.
The + button
The + button in the top bar creates anything: New message, New channel, New workspace, Create task, Schedule meeting or Upload file.
Install Squad on your phone
Squad can live on your home screen like any other app, with no browser bars — which is most of the screen back during a call. On Android and Windows the browser offers to install it. On an iPhone or iPad nothing offers: tap Share, then Add to Home Screen (in Safari the Share button is at the bottom; in Chrome it is beside the address bar). Sign in again inside the installed app the first time — iOS keeps it separate from the browser.
On a phone
A tab bar along the bottom has Home, Chats, Channels, Meetings and Menu; Menu, or the button in the top-left, opens the full sidebar. Everything else works the same, including calls.
Signing up
Create an account with your name, email and password, and choose Which class are you from? — your cohort (and track, or Not sure yet), Short course, or Not in a cohort. An administrator then verifies you; until then you see Account awaiting verification. Once approved you land straight in your class's channels.
If your account is deactivated
An administrator can deactivate an account — for example when fees are overdue or a student defers. You are signed out and see Account deactivated, with their reason if they gave one. Nothing of yours is deleted, and an administrator can reactivate you once it is sorted out.
Approve and manage accounts (admins)
Owners and Admins approve new accounts in Admin → Users; an approved person is placed in the class they chose, as a student, with their track. Sort by Newest first, Oldest first or Recently verified. Deactivate takes a reason the person will see and Reactivate undoes it. Delete removes the account with its messages, files and forms for good, and asks you to type their email to confirm. Only the Owner can delete an administrator.

Cohorts

Your class: its channels, its people, and how to join one.

A card per class: what it teaches, how many people are in it, and whether it is running.
What a cohort is
A cohort is your class — Cohort 9, Cohort 10 — and it owns its own channels: General, Announcements, one per learning track, Projects & Assignments and Support. Only its members can see them.
Join a cohort
If you chose your class when you signed up, you are put in it when your account is approved. Otherwise open Browse cohorts, under the channel list in the sidebar, and press Join cohort. You can be in more than one at a time, which is what happens when you carry on into a new class or help with an old one. A class marked Finished can only be joined by an admin.
  1. Sidebar → Browse cohorts
  2. Press Join cohort on your class
  3. Open the cohort to pick up its other channels
What joining gives you
You are put straight into the cohort's General and Announcements, and nothing else. Its track channels, projects and support are yours to pick from the cohort's own page, so your sidebar stays short.
Leaving, and coming back
Leave from the cohort's page. You lose access to its channels, but everything you wrote stays exactly where it is — and if you rejoin later you find it all again, including the day you first joined.
Find your classmates
The People page filters by cohort, by learning track, by whether somebody is a student, an instructor or support, and by who is online right now. Everyone's badges show every class they are in.

Projects and capstones

How to do your assigned project: your repository, milestone evidence, daily updates, the defense, and how you complete.

Your capstone page: the rules at the top, then your own status, repository and milestones.
Find your projects
Open Capstone Projects in the sidebar (on a phone, in the menu). Your projects — the ones assigned to you — are at the top, with a red number beside Capstone for how many still want today's update; it clears as you post. Under Browse projects is every project shared with the Squad community, from any class: search them, filter by type or class, and open any one to read its brief and milestones. Reading is open to every member, and nobody else's work is ever shown.
Read the Capstone page at a glance
The top of the page counts what matters today: updates due today, your projects, projects you run and projects to explore. Under it, Today's update still to post lists what you owe. Each card's colour says what kind of project it is — amber or green for data engineering capstones, violet for the data science capstone, blue for an ordinary project — and its bar shows how far through you are: Day 3 of 10 · 7 days left, Last day or Ended. The footer says Posted today or Post today's update.
Start a project yourself
Any project you can read, you can take on. You get your own record — milestones, repository, daily updates and defense — exactly as if your instructor had assigned it.
  1. Open the project from Browse projects.
  2. Press Start now, read what it commits you to, and press Start now again.
  3. If the project began before today, you get its full length counted from today; your deadline is shown before you confirm.
  4. It now appears under Your projects, and the daily update and milestones work as for everybody on it.
Read the rules before you start
A capstone is individual work. The top of its page says so: Project Type — Individual Capstone; Submission Requirement — Complete End-to-End Implementation; Collaboration — Individual Work Only; Assessment — Individual Technical Defense Required. Read the Individual Capstone Requirement notice under it. You may use official documentation, your instructors and approved learning resources. Submitting another student's implementation, splitting the project with classmates, or presenting shared code as your own is prohibited. Open Project brief — read the full specification for the full brief, data sources and deliverables.
Set up your GitHub repository
All your work lives in one repository of your own. Instructors review that repository, so make it public or give them access.
  1. Create a new repository on GitHub for this project, with a README.
  2. On the project page, find GitHub repository, paste its https:// address and press Save.
  3. Commit as you go, with clear messages. Your history is part of the evidence that the work is yours.
  4. If you ever change the address, press Change. The new repository has to be reviewed again.
Submit evidence for a milestone
A capstone has eight milestones, listed under Milestones. Each says what to build and what counts as evidence. Every milestone must be approved: completing only some modules is not completing the capstone.
  1. Open the milestone by clicking its name.
  2. In the box, describe what you built, how it works and how you tested it, in your own words.
  3. Add an https:// link to that part of your repository — a folder, a file or a commit.
  4. Press Submit for review. The milestone now shows Awaiting review.
  5. Wait for your instructor. Approved means it counts. Changes requested means read their feedback under Submission history, fix it, and submit again.
How milestone review works
Only an instructor can approve a milestone, after reviewing your own work; there is no way to mark one done yourself, and a classmate's approval never counts for you. If you resubmit while one is still awaiting review, the new one replaces it. Once a milestone is approved it is closed and cannot be resubmitted. Everything you submit, and every review, stays in Submission history. Evidence submitted after your deadline is still accepted, but is marked late.
Post your daily update
Every project asks for one short update a day, on your own — classmates never see yours.
  1. Open the project (on a capstone, scroll to Daily updates).
  2. Under Today, fill in What did you do today? — the only required part.
  3. Add What's next? and Anything blocking you? if you have them, and a link to today's work.
  4. Press Post update. You can press Edit today's update until midnight.
What counts as today
A day is the calendar day in Nairobi, whatever your phone's clock says. You can edit only today's update; earlier ones stay as they were. On a weekdays-only project, Saturday and Sunday are never counted as missed, though you may still post. Instructors reply under your updates, and you see their replies on the same page.
Your deadline
Your status card shows your deadline. It is the class deadline unless your instructor gave you a personal one, in which case it says personal deadline. Daily updates close after it; milestone evidence is still accepted but marked late.
Prepare for your technical defense
At the end you demonstrate your own work to an instructor and answer questions on all of it — not only the part you liked most. The areas you must cover are listed under Individual technical defense on your project; each capstone has its own. A working project you cannot explain is flagged for further review instead of passing.
  1. Open your project and read the list under Individual technical defense — that is what you will be asked about.
  2. Prepare to show the whole thing end to end, starting from a diagram of your architecture or approach.
  3. Run each part live from your own repository: on a data engineering capstone, ingestion, streaming, transformations, the warehouse and orchestration; on data science, your preparation, analysis, model and dashboard.
  4. Be ready to explain your choices and their limits: data quality checks, how a pipeline fails and recovers, or what your model gets wrong.
  5. Rehearse once without notes. If you cannot explain a part, that is the part to revisit before the defense.
How you complete the capstone
Your status card lists everything still missing. You complete the capstone only when all eight milestones are approved, your repository has been reviewed, you have demonstrated your defense, your instructor has recorded a final assessment out of 100, and that score meets the pass mark an administrator set. Until a pass mark is set your status reads Assessed — pass mark not set.
A way to work through it
Draw the architecture and data model before writing code. Build the smallest batch path end to end first, then automate it, then add quality checks and the rest. Submit each milestone as soon as it works rather than all at the end — review takes time, and feedback early saves rework. Write your README and documentation as you go, and post your daily update before you stop each day.

Channels and direct messages

Where conversations live.

Browse channels shows every channel you can join, with what each one is for.
Create a channel
Use + → New channel and give it a name. Make private keeps it to the people you invite. Owners, and a class's instructors while the class is running, can choose Who it belongs to — the whole workspace or a class — and make a class channel Staff only.
Rename a channel
Edit channel in the channel's menu changes its name and description; a line in the channel says who changed it. Admins can edit any channel, a class's instructors its class channels, and whoever made a workspace channel can edit it. #general keeps its name.
Browse and join
Channels in the sidebar shows every channel you can see. Open one to read it and join it.
Channel tabs
Each channel has tabs above the conversation: Messages for the conversation itself, Files for everything shared there, Tasks for work tracked in that channel, Events for its meetings, and Wiki for notes the channel keeps.
Direct messages
Use + → New message, or click anyone's avatar and choose to message them. Direct messages are private to the two of you.

Writing messages

Formatting, mentions and everything the composer can do.

A message with its reactions and a thread. The actions sit at the top right of a message: always there on a phone, and on a laptop when you point at it.
Send and new line
Enter sends. Shift+Enter starts a new line without sending. An unsent draft is kept when you move away and is still there when you come back.
Formatting
Squad understands markdown: **bold**, *italic*, ~~strikethrough~~, `code`, ```fenced code blocks```, > quotes, - bullet lists, 1. numbered lists, - [ ] checklists, # headings, tables and links. The Aa button in the composer opens shortcuts for the common ones.
Mention people
Type @ and start typing a first name, surname or handle — the list finds people either way, accents or not. Use the arrow keys or click to pick; the mention shows as the person's name, and clicking it opens their profile. They get a pop-up if they are in Squad, and an email if they are away (see Email notifications). On a laptop the Mention someone button in the composer opens the same list.
Notify everyone with @all
@all notifies everybody in the conversation, so only the people who run the room can use it: Owners and Admins anywhere, a class's instructors and support in that class's channels, and the host in a meeting chat. It never works in direct messages. If it would reach more than 25 people, Squad asks Notify everyone? first, and it can be used at most 5 times an hour.
Tag a whole class
Instructors and support staff of a class, and Owners and Admins, can type # and pick a class — #cohort-9 — to notify every current member of it. The list says how many people that is. A # word that is not a class, like #general, stays plain text.
Find your mentions
Open Chats and choose Mentions & reactions to see the latest messages that mention you or tag your class.
Emoji
The smiley button opens the emoji picker. You can also react to any message from the buttons at its top right: a quick row of twelve — 👍 👎 ❤️ 😂 🎉 🔥 👏 🙌 😮 🙏 ✅ 👀 — and the full picker for the rest.
Threads
Reply in a thread to keep a side conversation out of the main channel. Open a message's replies to read or add to the thread.

Sharing more than text

Files, clips, code, polls and tasks, all from the composer.

A poll: one vote each, live counts, and it can be closed when the vote is done.
Record a voice or video clip
In the composer, open the ⋯ menu and choose Record audio clip or Record video clip. Squad asks for your microphone (and camera), shows a live preview while you record, and lets you play it back before anything is sent. Press Send to post it, or Record again to start over. Clips can run up to 5 minutes and nothing is uploaded until you send it.
  1. Click ⋯ in the composer.
  2. Choose Record audio clip or Record video clip.
  3. Allow the microphone or camera if your browser asks.
  4. Press Start recording, then Stop when you are done.
  5. Listen back, then press Send — or Record again to retake it.
Share a file
Upload a file with the paperclip, or — on a phone, where the message box keeps only what it needs — from the + button beside it. The file also appears in the channel's Files tab and on the Files page.
Share code
The ⋯ menu has Code snippet, which posts code in a block with its language, easier to read than pasting it inline.
Ask a question with a poll
Choose Create poll from the + menu, write a question and up to ten options. Everyone in the conversation votes with one tap and sees the results update live. Tap your answer again to take your vote back, or another to change it. Whoever posted the poll can close it when the vote is done.
Turn talk into a task
Use + → New task, or the task button in the composer, to track something in the channel's Tasks tab.

Calls

Starting, joining and running a live call.

A call: the room fills the screen, and the controls sit within a thumb of the bottom edge.
Start or join a call
Start a call from a channel or a direct message. Squad asks for a Call name first — Cohort 9 - Power BI Dashboarding — because its recordings are named after it. Anyone in the conversation can join it while it is running. Every call starts with your microphone muted, so nobody hears your room before you choose to speak — press the microphone button when you are ready.
If your connection drops
Squad puts you back in the call by itself — the banner says you don't need to do anything — and keeps trying for 5 minutes. If it cannot, join again from the channel once your connection is back. If the call server itself is down, Squad says so before you join and during the call, and workspace admins see it too.
Keyboard shortcuts in a call
M mutes and unmutes, V turns your camera on and off, H raises or lowers your hand, and C opens the chat. They do nothing while you are typing or a menu is open. Recording and ending the call have no shortcut, on purpose.
Choose your microphone and camera
Press the small arrow beside the microphone or camera button to pick another device — a headset, a USB microphone or an external webcam. The switch happens straight away without leaving the call, and Squad remembers your choice on this device. The microphone menu also has noise cancellation, which filters out fans and typing; turn it off if it cuts your voice out.
Invite people
Copy the call link to invite anyone — people with an account go straight in, and people without one join as guests. You can also ring everyone who has not joined yet.
The waiting room
Guests and people who are not in the room wait until a host lets them in. Hosts see who is waiting and can Admit them one at a time or Admit all.
Raise your hand
Raise your hand to ask to speak without interrupting. Hosts see raised hands in the order they went up. Your hand follows you — it stays up if you reload or join from another tab.
Share your screen
Share your whole screen, a window or a tab. Everyone in the call sees it until you stop sharing.
Chat during a call
The call has its own chat with everybody in it, so links and notes do not interrupt whoever is speaking. The paperclip, Share a file, sends up to 10 files at once: they wait above the box until you press Send, and you can remove any first. The poll button beside the box asks the room a quick question — guests can vote too, and the results are kept with the meeting's record.
Record a call
The host and co-hosts can record; other participants cannot, and are shown a Recording badge whenever it runs. Recording is asked for rather than started silently, because it keeps a copy of everyone in the call. It can be paused and resumed, and any host or co-host can stop it — even one somebody else started. A recording is saved in parts of up to 35 minutes, each posted in the conversation as soon as it is ready. When the recording ends, the parts are joined by themselves into one Full recording, posted in the same place.
Keep a call running
Go back to Squad without leaving the call — it keeps running in a dock so you can read and write while you listen.

Hosting a call

What a host can do that others cannot.

Participants, with the controls a host has over each person.
Manage participants
Hosts can mute someone who has left their microphone open, ask someone to unmute, stop a screen share, and remove someone from the call.
Asking someone to unmute
A host cannot switch your microphone on for you. They can send a request, and you decide.
Admitting people
The waiting strip shows who is waiting, with Admit beside each person and Admit all. Press Let everyone in in the call's top bar to let people in without asking — it also admits everyone already waiting. Link guests still wait to be admitted. Press it again to make people ask.
Rename a call or its recording
The host, co-hosts and workspace admins can rename a meeting: in the call, click its title; on the meeting's page, press Rename. Everyone sees the new title straight away, and the next recording is named after it. Only the host (or an admin) can rename a recording, from the Recordings list on the meeting's page — every part and the messages that posted them are renamed too.

Meetings

Scheduling ahead, and what happens at the time.

Schedule a meeting
Use + → Schedule meeting. Pick the channel, the people, the time and the length. It appears on the Meetings page and in the channel's Events tab.
Join at the time
Open the meeting and join from its page. The meeting has its own chat, which stays with the meeting afterwards, files and all.
Watch a recording afterwards
The meeting's page has a Recordings list: the Full recording first, then each part, with Play and Download. A recording shared in a conversation shows as one card you can play in place, with the meeting it came from underneath.

Files

Finding what has been shared.

Find a file
The Files page lists everything shared with you, and each channel's Files tab lists that channel's. Search by name, filter by type — PDF, Excel, Word, PowerPoint, images, recordings, audio clips, archives — or by who uploaded it, and sort the list.
Preview and download
Click a file to preview it. Recordings and voice clips play in place; other files can be downloaded or their link copied.

Learning notes

Course notes for every subject, tasks your instructors grade, and your learning record.

Find a subject
Open Learning Resources in the sidebar. Each subject — MS Excel, Power BI, SQL, Python, Linux, dbt, Apache Airflow, Apache Kafka and Software Engineering — is a card showing how many of its sessions you have completed. Open one to see its sessions down the side; assignments are highlighted.
Read a session
Each session says how long it takes to read and how many of its tasks you have answered. Click any screenshot to see it full size. When you have read it and done the tasks, press Mark session complete at the bottom — it goes on your learning record. Previous and Next move between sessions.
Answer a task for grading
Task cards marked Your turn are graded by your instructors out of 10.
  1. Press Answer this task.
  2. Write your answer — SQL, results, or a few sentences, whatever the task asks for.
  3. Press Submit for grading. The card shows Submitted · awaiting grade.
  4. When it is graded you see your score out of 10 and your instructor's feedback. Improve and resubmit sends a new answer and clears the current grade.
Practise for interviews
MS Excel, Power BI, Python, Apache Airflow and Apache Kafka each have an Interview Practice session: over 100 questions with model answers, from beginner to advanced, and how to practise them.
Your learning record
My learning record, and the record on your profile, show the sessions you have completed in each subject, how many tasks are graded with your average, and how many await a grade. Only you and your instructors and admins can see it — classmates cannot.
Grading (instructors and admins)
Instructors and admins press Grade tasks on the Learning notes page. To grade lists every answer waiting, filterable by subject: give a score from 0 to 10, add feedback if you like, and press Save grade. If the learner changed their answer while you were grading, Squad asks you to grade the new one. The same people can add and edit notes.

Forms

Make a form, share its link, and collect answers — including workshop registrations with payment and check-in.

Make a form
Any member except guests can make a form: press the + button at the top and choose Forms.
  1. Press New form, and start from a template or build your own.
  2. Give it a title and add questions: short answer, paragraph, multiple choice, checkboxes, phone number, file upload or a section heading.
  3. To show a question only after a certain answer, use Only show this question when ….
  4. Press Create form.
Share it and collect answers
Copy link gives you a link anyone can fill in, with no account. Each person gives their email first, and each email can answer once. The Responses tab lists every answer, and Download CSV exports them. Stop accepting responses closes the form; Accept responses opens it again. Add co-managers in Settings to share the work.
Run a workshop registration
Start from the workshop template, or turn on Event page, Track payment and Track attendance in a form's Settings. People register from the event page and get a registration ID to keep for check-in. On the Registrations tab, managers see the totals, search by name, email, phone, ID or payment code, set each payment to Verify payment, Reject payment or Waive fee, and mark attendance from Registered to Checked In and Attended on the day.

Running a project (instructors and admins)

For a class's instructors and support staff, and for Owners and Admins: assign projects, read updates, review milestones, record defenses and final assessments.

One student's capstone, as staff review it.
Create a project or a capstone
Only a class's instructors and support staff, and Owners and Admins, create projects — and only for their own class.
  1. Open Projects and press New project.
  2. Choose the class. Under Start from, pick A blank project or one of the individual capstone templates; a template fills the title, the brief and the eight milestones.
  3. Set the start and due dates, and whether only weekdays count. Leave Class only off to share the brief with the whole Squad community, or tick it for a confidential project only this class sees.
  4. Under Assign to, choose every student in the class or one track, and press Create and assign. Staff are never assigned. Any member can also join a community project themselves with Start now; they appear in your grid from the day they started.
Assign more people, or take someone off
On the project page, Assign more adds picked students, a track or the whole class; only current students of that class are added. The person icon at the end of a row takes a student off: their work is kept, and assigning them again brings it back.
Read daily updates
The Daily updates grid shows every student by day: a green tick is posted, a red cross missed, a dashed box due today. Tick Hasn't posted today to see who is behind. Click a green tick to read that update and reply; the student sees your reply under it.
Review milestones
Capstone progress lists every student with their eight milestones, repository, defense, final score and status, and how many submissions await review. Click a student's name to open their record.
  1. Open the milestone marked Awaiting review — the latest submission and its link are at the top.
  2. Check the work in their repository yourself.
  3. Approve it, with an optional score out of 10, or write what to fix and press Ask for changes.
Repository and personal deadlines
On a student's record, press Mark repository reviewed once you have reviewed their final repository. Under the status, set a personal deadline for that student only, or press Use class deadline to put them back on the class's.
Record the technical defense
Ask questions across the whole architecture. Under Individual technical defense, tick each area the student demonstrated and could explain. Record as demonstrated is only possible with every area ticked; otherwise write what they could not explain and press Flag for further review.
Final assessment and pass mark
The final assessment, out of 100, opens once every milestone is approved, the repository is reviewed and the defense was demonstrated. The pass mark is set on the project page by an Owner or Admin only; until it is set, nobody is marked as having completed.
Edit, extend or archive
Edit changes the title, brief and dates for everyone. Archive closes a project: nothing new can be posted, everything already posted is kept, and Restore opens it again. Nothing is ever deleted.

Project Lab

Hands-on projects for your track, submitted as files and a GitHub repository and marked by a trainer out of 100. It currently runs the Python Specialization Challenge, and more projects are on the way.

What the lab is
Open Project Lab in the sidebar. Currently the lab runs the Python Specialization Challenge: two specializations, Data Engineering and Data Science, AI & Analytics, each with four one-day projects. Expect more projects and tracks to be added over time; new ones appear on the lab page as they are published. Every project has a business scenario, learning objectives, a checklist, downloadable datasets and starter code, deliverables and a submission guide. Published briefs can also be read without an account at /projects.
Your track comes from your class
Which projects you can submit depends on the track your class puts you on as a student, not on anything in your profile. If you are in two classes on different tracks, the class you joined most recently counts. If the lab says You have not been assigned a specialization yet, ask the training team to set your track.
Join a project
Press Join this project on any published project to follow it at your own pace, and it is added to your Tasks, due on your class's deadline (signed out, it reads Sign In to Enroll). Once your class is given a schedule for your track you are enrolled in its days automatically. Joining by yourself does not let you submit for marks: that needs the training team to put you on the track in your class.
Do and submit a project
Each day opens at 00:00 Nairobi time and is due at 23:59 that day, unless your trainer set other times. Before then its card reads Not yet released.
  1. Read the scenario and download the datasets and starter code under Resources.
  2. Tick the Progress checklist as you go. It is only for you: it awards no marks.
  3. Push all your work — code, notebooks, outputs and a README explaining the project — to a public GitHub repository of your own. Files are not uploaded to Squad: the repository is your submission.
  4. Under Submit your solution, paste the repository link, like https://github.com/username/project-repository. A link with /tree/main or .git on the end is fine; it is saved as the plain repository link.
  5. Add notes if you like — your approach, what was hard — and press Submit Project. Squad checks with GitHub that the repository is public and has at least one commit, which takes a few seconds.
After you submit
Your project shows Submitted. Until a trainer opens it you can replace it by submitting again; the old one shows Replaced before review. Once it reads Under review it is locked. When it is marked you see Approved or Changes requested, your score out of 100, your trainer's reason for each mark and their feedback on the project page — and you are emailed the same, unless you turned email notifications off. Approved is final unless your trainer reopens it.
Late work and resubmitting
After the deadline you can still submit: every project takes late work, and the submission is marked Late for your trainer, who still reviews it. When your trainer requests changes you may always answer them, even past the deadline, unless the project does not allow resubmissions. If you are in two classes on the same track, the later deadline is yours.
What each status means
Not yet released: the day has not opened for your class. Not started: open, nothing ticked. In progress: at least one task ticked. Overdue · submit late: past the deadline with nothing submitted — it can still be submitted, and will be marked Late. Submitted: in, waiting for a trainer. Under review: a trainer has it. Changes requested: read the feedback and use Submit again. Completed: approved.
If a submission will not go in
The page says what is wrong. A GitHub profile link: open your repository and copy that link instead. A link to an individual file, issue, or commit: submit the repository's main page. We couldn't access this repository: check the spelling, and in the repository's Settings make sure it is public — a private repository looks the same as a missing one. Your repository appears to be empty: commit and push your files, then submit again. GitHub is taking too long, or is temporarily unavailable: GitHub is busy, not your link — wait a minute and press Submit Project again. Never send your project files to a trainer over chat or email instead.

Running the Project Lab (trainers and admins)

For a class's instructors and support staff, who review its submissions, and for Owners and Admins, who publish the projects, set tracks and release them to a class.

Who can do what
An Instructor or Support member of a class reviews that class's submissions; Owners and Admins review every class and are the only ones who can open Manage the Project Lab. Guests never review. Nobody reviews their own submission, and staff cannot submit — use a separate student account to try the student side.
Set up a class
Everything is in Manage the Project Lab, reached from Trainer tools on the lab page.
  1. Projects: open each brief and press Publish. Under Who can read it once published, choose Everyone (the public site too) or Members only. Until then a brief is a draft only staff can see.
  2. Tracks & trainers: pick the class, select students and use Set track for selected — Data Engineering or Data Science.
  3. In the same tab, make each trainer Instructor (reviews) or Support (reviews).
  4. Schedules: Release a track to a class with a Start date (Day 1), and choose whether late work and resubmissions are allowed. Day N opens on the start date plus N − 1.
Review a submission
The review workspace lists submissions from your classes, newest first, filtered by status, class, specialization and project; late ones are marked Late.
  1. Open a submission. It becomes Under review, and the student can no longer replace it.
  2. Open the repository (it opens in a new tab) and read the code, its README and the student's notes. The submission shows the default branch and the latest commit GitHub confirmed when it was submitted.
  3. Where the project asks for them, open the report, demonstration video and slides links listed under the repository.
  4. Mark each criterion of the project's rubric — always out of 100. Most projects use Correct functionality /35, Python fundamentals /30, Code organization /15, Error handling /10, Documentation /10; a project with its own rubric shows its own criteria. Where the project offers bonus marks, give them in the Bonus box: they are shown beside the score, never added into the 100. Under each mark, say why — the student is emailed every mark with your reason beside it.
  5. Press Approve, or write what needs to change and press Request changes — feedback is required to request changes.
Re-check a repository
Re-check link asks GitHub about the repository again and refreshes its latest commit. If GitHub says it has been deleted, made private or emptied, the submission shows Repository unavailable — in the list and on the submission. If GitHub could not be reached, it says so and keeps the last result; that says nothing about the repository. Re-checking never changes a status, a mark or a decision: those stay yours. A commit date is the committer's own clock, so it shows the repository has work in it, not who wrote it or when. Submissions made with uploaded files before submissions became GitHub-only are labelled Legacy and keep their files.
Email students about their projects
Owners and Admins: in Review submissions, set the filters to the students you mean — a class, a specialization, a project, a status — and press Email students. Choose Students on this list for the submissions shown, or Everyone enrolled for everybody on those projects whether or not they have submitted (status does not narrow it). It shows how many students and who before anything is sent. Write a subject and a message — **bold**, a line starting "## " for a heading and lines starting "- " for a list — and add a CC if you want a copy of each; each student gets their own copy addressed to them by first name, with a link to their projects, and replies come to you. Send test to me first, then Send, and confirm. If a submission arrives while you write, the count changes and you are asked to check the list again before it sends. Every email is recorded.
Reopen, re-mark and export
Reopen takes an approval back so the student may submit again; the approval and its marks stay in the history. If you see already reviewed or replaced, the student submitted again or another trainer marked it first: reload and mark the current attempt. Export results (CSV) downloads the current filter with every criterion, the total, the reviewer and the feedback.
See who is enrolled and how it is going
Overview shows active challenges, assigned students, submission and completion rates, the average score, pending reviews and performance by project. Enrolled lists everyone on a track — name, email, class, whether they Enrolled themselves or were Assigned by track, their days, submissions and approvals — with search and a CSV export. The enrolled count on a project includes both.
Change dates safely
Releasing a track to the same class again moves its dates and never touches a submission. A project's schedule cannot be removed from a class once anybody in it has submitted; change its dates instead. A file resource that is not public can only be downloaded by signed-in people, even on a public project.
When a student is stuck
Check three things: their track, their class's schedule, and their submission's status. Not part of your specialization yet: set their track. Not been released to your class yet: release the track, or the start time has not come. (A passed deadline never blocks anyone: late work is always accepted and tagged Late.) Resubmissions are not allowed: allow them on that schedule. A repository refused as missing or empty: it is private, misspelt or has no commits, and the student must fix it on GitHub. Told to try again shortly, many students at once: GitHub is rationing our checks — ask the platform team to set GITHUB_TOKEN. A submission a trainer cannot see was made under a class they do not review, or was replaced — check Enrolled, and filter the queue by All. If none of that explains it, send the platform team the person's email, class, the project's track and day, the exact message with a screenshot, and the time in Nairobi.

Your account

Presence, notifications and settings.

Your profile: your photo, your title, your cohorts and your links.
Presence
Your avatar shows whether you are online. It updates on its own as you open and close Squad.
Notifications
The bell collects your notifications. Open it to read them, and mark them read one at a time or with Mark all as read.
Email notifications
When you are away, Squad emails you about direct messages and @mentions of you that you have not seen. It waits 5 minutes first, skips anything you read in the meantime, and sends at most one email every 15 minutes, listing what you missed with a link to each. @all and class tags never send email. Turn it off in Settings → Notifications by unticking Email me about direct messages and mentions.
Profile and appearance
Your avatar opens the account menu: View profile, Light, Dark or System, Settings and Sign out. Settings edits your profile, sets the theme (Match my system follows your device), turns email notifications on or off, changes your password, and shows the devices you are signed in on.

Keyboard shortcuts

  • Open search from anywhere⌘K / Ctrl+K
  • Send the message you are writingEnter
  • Start a new line without sendingShift+Enter
  • Close the dialog or panel that is openEsc
  • In a call: mute or unmute your microphoneM
  • In a call: turn your camera on or offV
  • In a call: raise or lower your handH
  • In a call: open or close the chatC

Still stuck?

Write to the Squad team and say what you were trying to do. Screenshots help.