Invite your team
Add two people before you add twenty. A rollout that starts with the whole company generates the same question forty times — and whatever confuses your first two colleagues is what your internal note needs to explain.
Find the member or team settings for your project. This is also where you will remove people later, so it is worth knowing the path.
Use a work address rather than a personal one. Leavers are easier to remove and access reviews are easier to pass.
Roles are easy to raise and awkward to lower. Start low; nobody minds being promoted.
Send a line outside the product. An unexplained invite email looks like phishing and gets deleted.
Fill this in: the real role names in Fotoslov — переводчик по фото and one line on what each may do. Mark any role that can delete data or change billing — those are the two people regret handing out.
Check that it arrived#
An invitation can fail quietly in three ordinary ways.
| Symptom | Usual cause | What to do |
|---|---|---|
| Nothing in the inbox after ten minutes | Filtered as spam, or held by the mail gateway | Ask them to search for the sender, and allow-list the domain |
| "This invitation has expired" | Invitations time out | Send a fresh one; do not reuse the old link |
| They land in a different workspace | They already had an account under another address | Invite the address they actually sign in with |
Checkpoint: each person can sign in, see the same project you do, and describe what they are allowed to change.
After the first week#
Review the member list once people have settled. Remove anyone added "just in case", and write down who owns access requests from now on. A named owner prevents the quiet drift where everybody ends up an administrator.