Frequently asked questions

Teamflow will be available on 1 November 2026, on iOS and Android.

Sign up with an email address and a password. The account is ready immediately. In production, the password must be at least 8 characters, with lowercase, uppercase, a digit and a special character.

Yes. The service is for adults. By opening an account, you confirm this. Details in the terms of use.

Open Profile, then Preferences. The app supports French, English, Spanish, Italian, German and Portuguese.

With no team, the Team screen offers Create (you become lead of an organisation and a root team) or Join (code from a manager). Email invitations appear first. Documentation and Calendar stay greyed out until a team is validated.

The team lead has a 4-character code (letters A–Z and digits 1–9, no O or 0), regenerable in team settings. They can also add a member by email (+ button).

Joining by code stays pending until the manager taps Validate. Until then: no members, documents, calendar or team lists.

Accepting an email invite in the app is already validated. Entering the code stays pending. If the account already exists and a manager adds you by email, membership is validated at once.

Your upline, your downline, and same-level teammates. A gold star is the manager of the shown team; a silver star means they lead another team.

By design: you do not see cousins’ downline (side branches). Only their manager, or an ancestor, sees that depth.

Yes. Organisations are separate: no sharing between them. In one organisation you lead only one team. You can be a member of several teams in the same organisation.

A manager cannot join (or be added to) a downline member’s team. Joining a cousin team or another organisation remains allowed.

Only the team manager. An ancestor may browse a subordinate’s library or calendar and grant access, but not write.

The manager or an ancestor grants access to other teams in the same organisation. It is not a copy: recipients see the same file. A new child team does not inherit automatically. A granted folder covers the whole subtree (including files added later).

“All” covers teams you lead, your memberships, and events you were granted. It is not an automatic dump of the downline.

A personal list is only yours, in the active organisation. A team list is for the lead and members of that team (an ancestor has no access unless enrolled). Checklist or kanban is chosen at creation, then fixed. Kanban v1: no drag-and-drop. Rename or delete the list: creator or manager.

A member leaves without deleting the team (they can return with the code). A lead can leave only if the team is empty (no other members, no child teams).

Profile → Security, by retyping your email. This is a logical erasure. If you led a team, subordinates are attached to the parent team. Your documents and events become inaccessible; other people’s remain. Details in the privacy policy.