Team Members

How Lead360 helps

Team Members controls who can enter a sub-account and which roles or permissions shape their access. Clear membership and least-privilege assignments reduce accidental exposure while giving staff the tools required for their actual responsibilities.

When to use this area

Use Team Members to invite, review, update, suspend, or remove staff access and to audit ownership when responsibilities change.

Before you begin

• Verify the person, business email, employment or contractor status, and required sub-account.
• Choose the smallest role and permissions that support the job.
• Plan ownership transfer for assigned contacts, conversations, tasks, calendars, and integrations.

Add a team member

1. Use the staff member's correct name and work email.
2. Assign the smallest role and permissions needed for their job.
3. Connect only the calendars, channels, conversations, pipelines, and locations they manage.
4. Ask the person to confirm access before relying on the assignment.

Change or remove access

1. Review ownership of calendars, appointments, conversations, automations, and channels first.
2. Reassign live responsibilities before deactivating the user.
3. Remove access promptly when responsibilities change.

Review regularly

Audit administrators, inactive users, shared credentials, calendar ownership, channel membership, and data permissions on a regular schedule.

Use Ask360 here

Ask360 can list authorized staff context, resolve a team member by full name or work email, explain roles, and prepare one reviewed invitation or access change when supported. It never requests a password, signs into Google, removes an owner, or changes permissions without an exact accepted review.

Confirm the result

A completed Team Members workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Confirm invitation or membership state.
• Test access with the intended role where possible.
• Review privileged areas, developer credentials, external connectors, and record ownership after a change.

Troubleshooting

A user sees too much

Review role inheritance, agency-level access, sub-account membership, team assignments, and feature-specific permissions.

Removing a member breaks work

Transfer ownership, calendars, automations, credentials, channels, and scheduled responsibilities before removing access.