Team Members

Purpose

This page manages existing team user accounts so access, roles, and accountability stay accurate.

Prerequisites

• Users must already exist in the tenant/team.
• Role and permission model should be defined.
• Admin-level permissions are typically required for updates.

Main Actions

• View current team members.
• Update member roles or access levels.
• Activate/deactivate or remove access as needed.
• Confirm ownership for operational responsibilities.

Field/Status Reference

• Member Name: User identity used across assignments and logs.
• Role: Permission scope for what the user can do.
• Status: Active/inactive participation state.
• Joined At: When the user was added to the team.
• Last Seen: Recent activity indicator.

Workflow

1. Open the member list and locate the user.
2. Review current role and responsibility fit.
3. Apply needed role or status changes.
4. Confirm impact on assignments/workflows.
5. Save and communicate important access changes.

Connections

• Impacts ownership across checklists, tasks, and logs.
• Works with Invite People for user lifecycle management.
• Role changes affect visibility and actions on other pages.

Common Mistakes

• Giving broader access than needed.
• Leaving inactive users with active permissions.
• Changing roles without checking downstream workflow impact.

Troubleshooting

• If role edits fail, verify your own permission level.
• If a user cannot access expected pages, review role mappings.
• If assignments break after a change, reassign ownership explicitly.

Quick Tips

• Follow least-privilege access by default.
• Review team access regularly (for example monthly).
• Document why major role changes were made.