Skip to content
Lesson 3 of 4Written guide available

Invite people with the right access

Separate membership from access to client mail.

Video in production

Our team is recording this lesson. Start with the written guide and exercise below.

Read the lesson

The idea to put into practice.

Developers and designers may work mostly in projects and tasks; account managers handle client messages. Membership does not mean every person should read the shared Inbox.

Prepare an access plan before inviting people. Record each responsibility, needed work and whether client mail is necessary. Keep ownership clear when someone changes role or leaves.

Invitations are demonstrated in the preview. A displayed invitation is a preview state until live delivery is available. Check recipients and roles before a released invitation workflow.

A useful way to approach it

  1. List the owner, account manager and delivery team.
  2. Match people to responsibilities.
  3. Grant Inbox access where work requires it.
  4. Name the owner of access changes.

Try it with fictional work.

Plan access for an owner, an account manager and three designers. Explain how designers deliver without automatically needing client mail.

Before you move on

  • Roles are clear
  • Inbox access is intentional
  • Recipients checked
  • Access review has an owner

Check your understanding.

What should determine Inbox access?

Keep something useful.

Download the action sheet to reuse the exercise and checklist with your team.

Ready to move forward?

Try the exercise, check your understanding, then mark this lesson complete.

Progress is stored only in this browser. It does not sync between devices.

Written lessons are available now. Videos are coming soon. Connection-dependent exercises use demonstrations until live integrations become available.

Course material is prepared with AI assistance and reviewed for consistency with Tamaam’s product direction. Suggest a correction.