A Team program is a Hub project made from the Team program template, for a group of freelancers or testers. Everyone reads and accepts one brief, then works in their own space: their instructions, their cards (one per tool), a private thread with the Lead, and their time. The Lead sees everyone's work, the hours, the ideas, a day-by-day timeline and a private scorecard. Members never see each other's spaces. This guide covers both sides, and Share an idea, which is on every aiKit page for everyone.
Buka Hub →In the Hub, press New project and pick the Team program template. The project gets a program page; a banner on the project, This is a Team program, opens it with Open the program. Programs you lead or belong to are also listed under Team programs at the top of Hub home.
The Lead is the owner or an admin of the Hub that holds the program (a team member who starts one leads it too). Everyone else on the program is a Member. Being on a program never adds a person to your Hub's people or projects: they see the program page and nothing else of your Hub.
People tab → Add a person: a name, the email of their aiKit account, and their area. Press Invite link on their row to copy a link and send it to them yourself; it works once, and pressing it again makes a new link and stops the old one. A person whose verified aiKit email matches the one you entered joins on their own the next time they open the Hub.
Edit changes a person's name, email or area; Remove takes them off the program (their cards stay, without an owner).
A new member sees only the brief at first. They tick I've read the brief, including the work log notice, and press I've read this; the date is kept. Until then nothing else opens for them and nothing is logged.
The Lead edits the brief on the Brief tab, with a live preview and a Who has read it list. Tick Ask everyone to read it again for a real change (new rules): each member reads it again before their space reopens. The same tab holds the Shared task of the week, one per line; week 1 shows first and they repeat after the last.
Open a card for its status, due date and checklist. A tool's checklist is its feature list from the Tool library (What you get) plus the standard steps: do the main job, ask for a change in your own words, try to break it, download and open everything, do it again on a phone. Reports on this card lists every report linked to it with its live status (Received, Looking into it, Being fixed, Live, please check, Fixed, Closed); each opens the report. Idea for this tool sends an idea that lands on the card. Open the tool goes to it.
The Lead can also Edit card (title, link, due date, owner, and the checklist as one step per line; ticks stay on steps whose words are kept) and Delete card.
A member presses Report a problem on the page where it happened, as usual. The report links to their card for that tool or page, and a card in To do or Working moves to Waiting on fixes. The thank-you note says which card it went to. A report from a page with no card is still in the program's reports.
Already reported (a member's tab) lists the open problems the whole program has found, titles and status only, never who sent them, with a search box, so nobody sends the same one twice. The Lead's Reports tab lists every report from the program; each opens the full report.
While a member who accepted the brief is signed in on aikit.ai, aiKit keeps a work log for them, as the brief says: the pages and tools they're on with active time (the page on screen and in use in the last few minutes), their checklist ticks and card moves, the reports and ideas they send, their time entries, the things they make in the tools, and the AI their work used. Nothing they type is kept by the log, only the page and the seconds. It doesn't run on any other site, and never for people who aren't on a program.
Timeline: pick a person and a day (the arrows step a day). Tiles show active time on aiKit, logged time, things made and AI cost to us; below, that day in order, grouped by tool or card, each line linking to the page, report or idea.
Scorecard: the week side by side for every member: active vs. logged time, cards covered, checklist steps, things made, reports per day, valid rate, hard to find (1–5 per report: Obvious, Solid, Hard to find), impact (reports that led to a fix), report clarity (0–3), follow-through (re-tests answered, Friday summary, brief), ideas sent and built, and the AI cost to us in dollars (what the AI providers charge for that person's work, not the tokens customers see). Each person gets a keeper grade, A to D, with a reason line; change it and add a private note. Under it, This week's reports lets you set a verdict (Valid, Duplicate, Not a bug, Can't reproduce) or a difficulty when the automatic one is wrong; a report much like an earlier one is flagged as a likely duplicate. How the numbers work explains every rule.
Share an idea sits next to Report a problem at the top of every signed-in page (a light-bulb icon on smaller screens) and at the bottom of the public website. Write the idea, add a sketch or screenshot if you like, and press Send idea; the page you're on goes with it. Signed out, an optional email lets us tell you when it's built.
Your ideas (/home/ideas) lists what you sent and its status: New, Planned, Built or Not now, with any reply. You hear back on the bell and by email when one is Built. aiKit admins see every idea there, as an inbox with the same buttons; a Team program's Lead manages that program's ideas on its Ideas tab.
Punya pertanyaan yang lebih singkat dan spesifik? Lihat FAQ.