Before the first sign-in
An administrator or team owner should confirm the correct email address, access level, and invitation process. Send instructions through a known channel. Explain how to recognize the organization’s real sign-in route and where to report a suspicious invitation.
Show the useful places
Introduce the team’s main discussion space, announcements, project records, and support contact. Explain which conversations are appropriate for a question and where final decisions are stored. A small map of three or four useful places beats a list of every channel.
Follow up after access
Check that the new member can find a recent decision, send a message to the right group, and adjust notifications. Review access after the first week. Remove temporary permissions that are no longer needed.
A first-week orientation
On day one, verify the invitation and show the new teammate the main team space, the location of current procedures, and a trusted support contact. Later, ask them to find the latest project decision and explain where they would post a question. This simple exercise exposes gaps in naming and access. At the end of the week, remove any temporary privileges and ask whether notification settings are manageable.
Choose the next step
| Situation | What to check |
|---|---|
| Invitation cannot be used | Verify the address, expiry, and identity requirements. |
| New member cannot find the team | Check membership and provide a short map of key spaces. |
| Temporary access was granted | Set an owner and a date for review or removal. |
A practical checklist
- Verify the person and their work email.
- Invite them with the appropriate access level.
- Show the main spaces and communication norms.
- Review access and unanswered questions after a week.