Admin Guide
FoloMeet · for the people who manage forums, members, and meetings
Why those two come first: tasks belong to meetings, meetings belong to forums, and who may see what is decided at the forum.
1Register the people
Open Manage in the left menu. The top card is Members.
- Enter Name — the name people use at the office is enough.
- Enter Organisation email — must end in
@organisation.example. - Choose Role: Member or Admin.
- Click Add member.
Then ask each person to sign up themselves
Send them the app’s address, then ask them to:
- Click No account yet? Sign up
- Enter their organisation email — exactly the same as the one you registered
- Create a password of at least 8 characters
Done. Their name links automatically to the row you created.
2Create forums
Forum is a home for meetings that follow on from each other — for example "Digital Team" or "Literacy Festival". Not a single meeting, but the series.
It does two things:
- Unfinished tasks carry over to the next meeting in the same forum, and don’t leak into other forums.
- Visibility is decided here. Members only see the forums where their name is ticked.
In Manage → Forum: enter its name, click Add forum. Then tick everyone who may see it.
3Prompt for summarising a meeting from a recording
If the meeting is recorded, the flow goes like this — and everything up to the summary runs on your own laptop:
The prompt we use
Paste the meeting transcript into an AI (ChatGPT, Claude, or whatever you usually use), then give it this instruction. The meetings are held in Indonesian, so the real prompt is in Indonesian; this is its translation:
1. Group the discussion into themes (policy, tutorials, reviews,
recommendations & strategy, or any other theme you pick up from context).
2. Use the context of the conversation to make sense of odd words and typos
from speech-to-text. Check with me if an odd word is truly stuck and hard
to understand — don’t just guess.
3. Summarise EVERYTHING that was said — leave nothing out.
4. Add a section "Bottleneck Analysis & Strategic Recommendations" based on
the problems you picked up from the meeting. Back up each problem and its
recommendation with evidence: name the relevant theory, framework or research
finding and explain why it applies. Don’t invent theory names or
sources — if you’re not sure, present it as an opinion, not as a theory.
5. Add a table "Glossary — Interpreting Odd Words in the Transcript".
6. Output as a Google Doc (.docx).
7. Create ONE table "Rencana Tindak Lanjut" (action plan) with exactly these columns:
No | Tindakan | PJ | Tenggat
(action | owner | deadline)
- Each action starts with a verb. Don’t use the "|" character inside a cell.
- Work out each owner as carefully as you can from the conversation: who was
assigned, who volunteered, and who looks after that area. If it is
still unclear, write "belum ditentukan" (not decided) and add it to the list
for me to confirm (point 2) — don’t just guess.
- Write each owner exactly as their name appears in the app: [copy from Manage].
One row per person — a shared task is split into one row for each person.
People who aren’t on that list are still written down by name.
- The deadline is an exact date written in Indonesian (e.g. "12 Okt 2026").
Don’t use day names, "besok" (tomorrow), "minggu depan" (next week) or
"akhir bulan" (end of month). If it really hasn’t been decided, write
"belum ditentukan" (not decided), never "segera" (soon).
[copy from Manage] with the member names
exactly as written on the Manage page. The app only recognises an owner whose
spelling matches: if Manage says "Rahmad", "Rahmat" is treated as someone
else and the owner column stays empty. A title in front is fine — "Mas Rahmad" is still
recognised as Rahmad.
The reason: a tidy meeting summary is full of tables — metrics, glossaries, attendee lists. If all of them were read, one document could produce over a hundred fake "tasks". Narrowing it to that one table is what keeps the result sensible.
The table format it recognises
The header row is recognised by two columns that each stand on their own: Tindakan ("Tindak Lanjut" or "Tugas" also work — all mean action/task) and PJ (or "Penanggung Jawab" — both mean owner). Other columns are up to you. Only the first table shaped like this is read — glossary, figures or tool-list tables are skipped.
.docx file can be
picked or dragged straight onto the Paste Meeting Notes page, and its content is read
inside your own browser. A summary in Google Docs is downloaded first via
File → Download → Microsoft Word (.docx).
|, such as one copied
straight from an AI answer.
4Record the tasks from a meeting
There are two routes. The first is much faster.
Fast route: paste the summary
Take the summary from the previous step. Open Paste Meeting Notes in the left
menu, then upload or drag the .docx file there (or paste
the text if its table uses vertical bars |), then click read. The app produces a draft task list, rather than saving it
straight away.
What it recognises: table rows, bulleted or numbered lists, member names anywhere in a row, and Indonesian dates, including words such as "besok" (tomorrow) or "minggu depan" (next week). Plain paragraphs are skipped on purpose.
- Name must be spelled the same as in Manage. If a row mentions two people, the first one named becomes the owner.
- "besok" (tomorrow), "Jumat" (Friday), "minggu depan" (next week) count from the day the minutes are uploaded, not the day of the meeting. Minutes uploaded a few days later get deadlines that shift with them — which is why the prompt asks for exact dates.
- English month names ("12 Oct") and "akhir bulan" (end of month) can’t be read; the deadline is left empty.
Manual route: one at a time
In Manage → Tasks: choose the meeting, enter the task title, pick the owner and deadline, click Add task.
The owner list only includes members of that forum. If the name you’re looking for doesn’t appear, they haven’t been ticked on that forum — go back to step 2.
5At the next meeting
Progress note
When moving a task to Done, Cancelled, or reopening it from Done, the app asks for a one-sentence note. Only those three moves — moving to "In progress" asks for nothing, so dragging cards during a meeting stays light.
The latest note shows right on the card. That’s what makes the board useful when it’s projected: "not started" tells you nothing, whereas "not started — waiting for data from the partner since Monday" tells you straight away what needs discussing.
Seeing a task’s journey
Tap the card to open its full history: every status move, its note, who moved it, and when — combined with the reminders that were sent. There, "reminded 4×" turns into dates you can point to when following up.
On the board, tapping the title edits it; tapping anywhere else opens the history; dragging moves its status.
Open FoloMeet in the left menu, and project the screen. That’s what this app is for: a meeting opens by looking at the previous meeting’s tasks, not by asking "so where did we get to last time?".
The leftmost column is deliberately Overdue, not "not started" — the first thing to look at is what didn’t get finished.
Cards can be dragged between columns to change their status.
6Creating a meeting by hand (rarely needed)
You usually won’t need this — pasting a summary already creates the meeting at the same time. Use it only if you want to register a meeting before it happens, for example to put the agenda up first.
In Manage → Meetings: choose the forum, enter the title and date, click Add meeting.
Only admins can open a new meeting. Regular members can still record tasks on meetings that already exist.
7Who can do what
| Action | Member | Admin |
|---|---|---|
| See forums where their name is ticked | ✅ | ✅ every forum |
| See tasks they hold | ✅ in any forum | ✅ |
| Change the status of their own tasks | ✅ | ✅ |
| Change the status of other people’s tasks | ❌ | ✅ |
| Change a title, owner, or deadline | ❌ | ✅ |
| Record a new task | ✅ | ✅ |
| Open a new meeting | ❌ | ✅ |
| Add members & manage forums | ❌ | ✅ |
| Change other people’s roles | ❌ | ✅ |
Making someone an admin
In Manage → Members, change the role on that person’s row. It takes effect immediately.
You can’t lower your own role, and the last admin can’t be demoted — either would lock everyone out of managing the app with no way back.
8When something goes wrong
| Symptom | Most likely cause |
|---|---|
| Signed in, but the screen is empty | Their name isn’t ticked on any forum. Open Manage → Forum and tick it. |
| "Only organisation email addresses can be used" | They signed up with an email outside @organisation.example. |
| Their name doesn’t appear in the owner list | They aren’t a member of the forum the task is in. |
| Can’t drag a card | The task belongs to someone else. Only its owner and admins can. |
| Asked to sign in again after already signing in | The session ended after a long idle time. Sign in again; the data hasn’t changed. |
| Forgot password | Click "Forgot your password?" on the sign-in page. The link goes to the organisation email. |