crew
folk is multiplayer — let a friend's folk do things for you, and yours for them, privately and only with a tap to approve.
most of the time folk works just for you. crew is what lets folk work between you and the people you trust.
add a friend who's also on folk, and once they say yes, your folk can ask their folk to do something — and theirs can ask yours. the catch that keeps it safe: nothing happens without that person's ok, and you only ever find out whether it got done. you never see their stuff.
a quick example
say your friend maya knows all the good sushi spots. you text your folk:
ask maya's folk to find a sushi spot for friday
maya gets a little prompt showing exactly what you asked. she taps approve. her folk does the work — on her account, with her tools — and you get back a simple "done." you never see maya's calendar, her contacts, or anything her folk looked at. just the result.
adding someone to your crew
head to your dashboard at getfolk.app/dashboard/crew:
invite them
enter their phone number and a nickname — the name you'll use when you talk to folk later ("ask maya to…").
they say yes
their folk pings them to confirm, and the request shows up on their crew page. when they accept, you'll both see the link.
start asking
now you can delegate — from the dashboard or right in chat.
the other person has to be on folk already. if they're not, invite them to folk first, then add them to your crew.
asking a crew member's folk
once you're linked, there are two ways to ask:
- in chat — just tell your folk: "ask maya's folk to find a sushi spot for friday."
- from the dashboard — on maya's card, tap "ask maya's folk" and type the request.
either way, maya sees the exact request and has to approve it. she can tap
approve on her dashboard, or reply /crew-approve in her chat. once she
approves, it runs on her folk. you'll watch the status go from pending →
in motion → done — and when it's finished you can send a one-tap thanks.
who sees what
this is the important part. crew is built so the person asking only ever learns the outcome — never the other person's data.
| you (asking) | them (doing) | |
|---|---|---|
| the request you wrote | yes | yes — to approve |
| whether it got done | yes — done / declined / couldn't | yes |
| their data or their folk's work | never | yes, it's theirs |
| has to approve each time | — | always |
if a member's folk can't finish yet — say it needs them to connect an app first — the task is paused, not failed. only they see the reason, and they can retry. you're never shown a half-finished error.