A team member is a person in your Organisation Chart. They exist whether or not they can sign in — that is how the chart, the tribe directory and your website team page get their names. Giving one a login is a separate, deliberate step.
What a team member login can do
Much less than an administrator, which is the point. On each person, Manage Access offers:
- Edit Profile — maintain their own details and photo.
- Access CRM, with CRM Visibility set to their own records or the whole tribe's.
- Create custom pages and customise main website pages.
- Access network store.
The screen puts it well: grant access to specific functionality without giving somebody full administrative access to the tribe. A salesperson who needs their own CRM records and nothing else is exactly this.
One switch that does nothing
The other switches on that screen are real, but they are defaults — they pre-fill what a bulk invitation grants, rather than changing anybody already set up.
Inviting in bulk
Invite Team Members lets you filter by tribe, role and account status, pick who to include, write a message and set the access they all receive. People who already have a login or have no email address are excluded automatically and the dialog tells you how many. Use Send Test first.
Switch on Automatically invite new team members and anybody added later with an email is invited using those saved settings. Imports deliberately never trigger it, so loading a spreadsheet cannot email your whole network.
Automatic linking, and where it stops
A team member is linked to an existing login automatically when the email matches somebody who already has access to your organisation.