What you’ll see
Your goal
Learn how workspace membership, permissions, task assignment, and shared history support a team handoff. This path reviews the Demo Account without adding users, changing access, assigning work, or signing in as another person.
What you need
Use the existing authorized Demo session. User-management settings may require elevated access; visible controls do not establish another person's effective permissions. Phone and email configuration are unnecessary for understanding human task ownership.
Read-only milestones
- Inspect membership. Open Settings → Users → Users (or choose User Management in the profile menu). Identify the membership list and Add User entry without creating or editing a member. The walkthrough observed this page, not the recipient experience of a new invitation.
- Read the access model. Open Permissions (the tab beside Users in Settings → Users). Inspect Access levels, What each access level can do, and Per-person overrides. Do not click permission cells or reset controls; they are settings, not demonstration filters.
- Keep policy claims narrow. The source explains that job titles map to access levels and that owners retain full access. It also warns that some switches are still being enforced as they roll out. A matrix viewed from an administrator session does not prove every route or action is blocked for a limited user.
- Find handoff context. Open the existing training lead's Notes, Tasks, and Activity. Identify where a teammate would read the request and prior work. Leave notes and records unchanged.
- Inspect assignment. In the observed Add New Task form, locate Assigned to and the task-description area. Do not select a person or AI assistant. Close without submitting. The useful distinction is between a clear human owner and an automated execution choice.
Your useful outcome now
You can describe a good handoff: what has happened, what should happen next, who is responsible, the due date, and which lead the work concerns. You can also identify which access questions need a later limited-account check rather than assuming the administrator view proves them.
Later operational exercise — not performed
For later
With appropriate authorization, create a task for an existing teammate, save the context on the correct lead, and verify the teammate can see it from their own authorized session. Have that person confirm the task is understandable before performing it. Separately verify any expected notification; a saved task does not establish inbox delivery. Adding a user or changing permissions is a separate administrative action.
For email handoffs, review Sender Profiles and Sending; shared From identity and copied-recipient rules should not be guessed from task ownership.
If something is missing
Troubleshooting
Check workspace, membership, task filters, and intended access scope. A default-looking permission control during loading is not proof of a persisted setting. Resolve loading failures before changing access, and avoid granting broader permissions merely to hide a task-visibility problem.
Continue with D — Follow-ups and H — Performance.