Video chapters
- 0:00 Welcome
- 0:13 How Workspace works
- 0:42 Part 1 · A space for the project: explained
- 1:01 Part 1 · A space for the project — New private workspace, members, an outside guest
- 2:06 Part 2 · Talking and sharing: explained
- 2:23 Part 2 · Talking and sharing — Mentions, a room, a file, a thread, a pin
- 3:09 Part 3 · The plan and the work: explained
- 3:27 Part 3 · The plan and the work — Agenda, tasks, status, comments, history
- 4:30 Part 4 · Meetings: explained
- 4:46 Part 4 · Meetings — Schedule the homepage review
- 5:27 Part 5 · Everyone's side: explained
- 5:44 Part 5 · Everyone's side — The guest joins, Leo works, Maya sees the results
- 6:59 Wrap-up
Written guide
Workspace Navigation and Personal Views
Cedar & Form is preparing a new print collection. Maya coordinates the launch, Alex prepares the artwork and a customer reviewer checks the proof. Workspace gives that work a shared place: a conversation supplies context, a task supplies ownership, an agenda connects the work to a document, and a meeting gives people a time to decide. We will build those relationships and return through another person's account to check them.
Use a training organization with Workspace access, two active colleague accounts and an optional customer or external test account whose inbox you control. In this course, Maya and Alex mean those actual accounts; replace example addresses such as [email protected] with the real test addresses selected in the people picker. Prepare a harmless PDF named Cedar collection proof.pdf in the file manager and a genuine test meeting link from your meeting provider. Workspace stores a joining link; the form does not create a Zoom, Meet or Teams room. Select future dates when following the example; the illustrative target is 16 October 2026.
Open Workspace from Appmint's sidebar. If the rail is collapsed, use Expand. Home is the personal starting point; Inbox / Mentions brings attention back to conversations; My Tasks, My Calendar and Recent Files collect personal work across joined spaces. These are different from the Tasks, Calendar and Files panes inside one workspace. A public space you merely read is not automatically a joined personal workspace.
Start on Home and then open My Tasks. An empty Nothing assigned to you is a valid result before we assign anything. A load failure with a retry control is a different condition: retry the request and check access before concluding there is no work. In Search everything, type Cedar and press Enter. The Search drawer groups task and activity results. Later, use this exact search to reopen the records we create. Preserve the workspace name when opening a result so you know which shared context you are reading.
The instructions below describe the current documented controls. They are a manuscript draft: persistence, invitation delivery, effective access and the completed collaboration still require a live walkthrough.
Workspace Creation, Conversations and Privacy
Beside Workspaces, choose New workspace. Enter Name Cedar & Form — Autumn collection and What it is for Prepare the collection proof, review it with the customer, and record approval work. Select Private for this customer-facing exercise. A public workspace can be read by people in the organization; joining lets them post. Private means invited or added people only. A room inside the workspace is an organizational subdivision, not a separate access boundary: members can see the workspace's contents.
Separate 4 October owner-only rehearsal: Course collaboration lab 20261004, with Private checked and Members empty. It illustrates these fields; it is not proof Alex was invited or gained access to the Cedar workspace. Use your own name and members for the exercise above.
Leave Ends on (optional) blank while learning. A date here makes the whole space stop being readable at that time; it does not delete the records. That differs from a member's access end date, which affects that person, and an individual item's expiry. For a time-limited review, choose a future date only after the whole task and follow-up period are understood.
In Members, search for Alex and select the correct account by its email. Each selected row shows the person, an external flag and Access ends on. Keep Alex internal and leave their access end blank. Choose Create. The expected result is the newly named workspace opening with its panes, membership count and private indicator. Reopen it from the rail to check the name and description persisted. If you see Give it a name, supply the Name; repeated Create clicks do not cure validation.
For a lighter discussion, the Conversations heading has New conversation with the same name, purpose, privacy and expiry choices. Conversations default private and their composer omits task and agenda creation; choose the full workspace when those objects are central to the work. Direct messages use Direct messages → New message or Messages, or the Message button beside an active member. This route opens the messaging interface; do not search for a direct-message checkbox in the workspace creation drawer.
Members, External Guests and Access Expiry
Open Members in the Cedar workspace. Existing rows identify the owner, external members, invited people and expired membership. invited means acceptance is still pending; it is not proof of delivered mail or successful login. Add the customer by searching Add someone. If you need temporary access, first choose Set access end, select a future date and time, then pick the person: choosing a person triggers the add request immediately. For an outside reviewer, type a real controlled external address and select the invite result. The intended guest scope is this workspace, not organization-wide browsing.
As a workspace administrator, use a non-owner row's admin, member or guest control to change access type. Leave Alex as member and choose guest for the external reviewer. Admin controls are not shown for changing the owner's own role. Role changes and access-end changes are saved through their controls; revisit the row and Activity to check the resulting membership event. Do not assume that “guest” makes individual messages private from other workspace members.
Test visibility in separate signed-in browser sessions. Alex should see the private Cedar workspace after membership is active; a colleague not added should not discover it. The reviewer must actually accept the invitation and open the workspace before guest access can be called verified. Also try browsing other public spaces from that external account; the access service intends external people to see only spaces they are named in. If an invitation remains pending, verify the exact email, the receiving account and the delivery/invitation service with the administrator. There is no demonstrated resend workflow in this Members panel.
To understand the public alternative, create a harmless second workspace named Cedar team announcements with Private unchecked. From an internal nonmember account, use Browse public workspaces and conversations, then Read. The bottom bar explains Join to post. Choose Join, verify the composer appears, and post a test message. Joining changes membership; merely opening Read does not.
For removal, use Remove on a non-owner member row and confirm Remove. Their earlier posts stay in history. A non-owner member can instead choose Leave this workspace and confirm Leave. Test the removed person's access again: in a public space an internal nonmember may still read, so removal alone is not a confidentiality control. Use a private space for the restricted review.
Rooms, Messages, Mentions, Replies and Shared Files
Select Activity. The header describes everything, newest first. Use New room, type proof-review, and press Enter. Open that room before composing so the post belongs to it. Enter @[email protected] Please check the crop on the autumn collection proof. using Alex's real account email after the @ sign. Use Attach a file, choose Cedar collection proof.pdf in the file manager, confirm the selected file, then Send. The keyboard shortcut is Command+Enter or Control+Enter; ordinary Enter can remain part of the message.
Check the posted card for its author, text, room context, timestamp and attachment. Open the attachment and verify it is the intended proof. Then check Inbox / Mentions as Alex. A saved card is not delivery proof; the second account's visible mention is the useful handoff check.
On the post choose Reply. Write Crop checked; the right margin needs another 3 mm. and Send in the Replies drawer. Return to the parent card and inspect its reply count. Threaded replies keep that decision beside the original proof. Hover over a card to reveal Pin; select it and later Unpin to reverse the choice. A pin marks an item for the workspace; it does not grant access to somebody who lacks membership. Use Older to load earlier activity when necessary.
A message may be sent with files even if its text is empty. Files inside the space and Recent Files in the personal rail provide another route back to shared material. Open Files and inspect the same card, then follow its file link. A linked task or meeting on an activity card opens the corresponding detail drawer; use the linked record title rather than recreating a second record from its description.
The composer also offers item expiry. Leave it unset for decisions that need to remain available; apply a short expiry only to a disposable test post and verify its later disappearance separately. To remove an incorrect test post, the author or administrator can choose Delete and confirm. The UI explains that a removed card stays in the timeline while its content goes. It is different from deleting the workspace, and deleting a post should not be used as a substitute for correcting a task's status.
Workspace Tasks and Activity History
Inside the workspace, use Tasks → New task, or New task in Activity's composer. Enter Title Prepare autumn collection proof; in Details, enter Export the approved crop to Cedar collection proof.pdf. Attach the revised PDF and record which version the customer should review. Select Alex in Assign to, set Due to 14 October 2026 (or a future training date), and choose No agenda for now. Add the proof file through Files. Leave item expiry unset and choose Create task. A title is required; the form reports Give the task a title if it is blank.
Open the new task. Its title, author, room, Status, Due, Assigned to, Agenda, Description, Files, Comments and History are the operational record. In Alex's session, open My Tasks and find the same title. Use the status button and its Move to menu to select In progress. Later select Done after attaching the revised proof. These task statuses describe this shared piece of work; they do not by themselves approve an AI action or run a staged Workflow definition.
Owner-only rehearsal: Verify reusable media in the reader is Done, assigned to Video Lab, with creation, In progress and Done history. No attachment or comment was added in this example. The Cedar proof task and Alex's separate-session access still need their own readback; this image demonstrates where to inspect status and history.
To update the description, choose Edit, change the text and Save. Title edits save when focus leaves the title. Due, assignment, agenda and status controls save when changed. Reopen the drawer after each meaningful change and read History, which lists status/assignment changes, time and actor. Add a comment explaining Revised PDF attached; right margin corrected. so another person can understand the result without reconstructing the conversation.
In Tasks, switch between Board and List. Board supports dragging a task into a visible status column; the detail status menu is the precise alternative. Use Search tasks, Open / Closed / All, Every agenda / No agenda, and the person filter to narrow the list. A completed task disappearing from Open is expected. Select Closed or All and use List when searching terminal statuses such as Approved, Rejected or Canceled that do not each have their own board column.
For a blocked proof, select Blocked, explain the missing asset in Comments, and keep the assignee visible. Once the asset is supplied, change back to In progress and verify history records the recovery. If Alex is absent from the picker, return to Members and verify active membership before retrying. If a drag fails, read its error and reopen the task; do not assume the optimistic movement saved.
Shared Agendas, Documents and Task Progress
An agenda here is a project page with linked tasks, not merely the talking points of a meeting. Open Agenda → New agenda. Enter Title Autumn collection launch, Summary Customer proof review and final artwork handoff, select Maya as Lead, and set Target date to 16 October 2026. In Page, write Scope: autumn print collection. Acceptance: revised proof attached, customer review recorded, final artwork task complete. Choose Create agenda.
Open the agenda card. Its Page and task board share the view. Edit the document to add Review notes: check margins and product names, then choose Save page. This is distinct from the metadata Save action. Close and reopen the agenda to verify the text survived. Edit agenda changes Name, Summary, Lead, Target date and Status; choose Save after those edits. Status choices are Active, Paused and Done. Paused is useful when the customer has not supplied an essential asset; it does not automatically resolve the tasks.
Return to the proof task, choose Autumn collection launch in Agenda, and reopen the agenda to see the linked task. Create a second task there named Deliver final artwork, assign Alex and set a due date before the target. Tasks created in the embedded board belong to this agenda. When a workspace has exactly one agenda, the new-task form may preselect it; inspect the Agenda field rather than relying on an assumed default.
Separate Media guide review rehearsal: the agenda is still active, its completion count is 1/1 and Closed is selected. The task card is outside this visible board area; use List or open the task to inspect its identity. A 1/1 task count does not itself mark the agenda Done—Mark done is still available.
The agenda card and header show done/total progress and any overdue count. Move the proof task to Done, leave final artwork open, and compare the numerator and denominator. The Mark done action has a confirmation that explicitly warns when tasks remain open: they stay as they are. To finish the exercise faithfully, close the final artwork task after its actual handoff, then Mark done and confirm. If you marked the agenda done too soon, use Edit agenda to return Status to Active, save, finish the remaining task and mark it done again. Reopening an agenda is different from reopening each task.
For practice, add Winter collection with its own document, lead and one task. The check is not simply that another card exists: the Winter task must appear under Winter while the Autumn task counts remain unchanged. This tests whether you can use the agenda relationship deliberately.
Meetings and Calendar
Return to Activity, select the proof-review room and choose New meeting. Enter Title Autumn proof review, Starts 15 October 2026 at 10:00 and Ends at 10:30, adjusted to future dates in your environment. The form uses the browser's time zone and stores it with the meeting. Read the saved time-zone label; do not assume a colleague in another location sees an identical wall-clock time.
Inspect Invite before saving. It initially includes eligible workspace members other than the organizer, excluding pending invited members. Remove people who do not need this review and add the active customer reviewer. Paste a genuine test provider URL in Meeting link. In Details, enter Review the revised proof. Confirm margins and product names. Read the Autumn collection launch agenda first. Attach the revised PDF using Files and choose Schedule.
The expected chain is an Activity event linked to a meeting record, a Calendar entry in this workspace, and an appropriate My Calendar entry for the invited account. Open the meeting title or linked record to inspect the drawer. Use Join to check the URL reaches the intended meeting service; this does not verify that a call was held. Inspect invitees and their displayed invitation status in the read-only participant view. This interface does not supply the RSVP buttons described by some older materials, so do not invent an Accept operation.
As an editor, change Starts and Ends to reschedule. Title and Meeting link edits save on leaving the field; Details → Edit → Save saves the description. Changes to Invited and Files use their own controls. Reopen the meeting and inspect the calendar from the invitee account after the change. Preserve both old and new timestamps in the production evidence so a notification claim can be checked independently of the saved record.
To cancel a disposable meeting, choose Cancel this meeting, read the confirmation, then Cancel meeting. The journal retains the record and the calendar title identifies cancellation; the drawer becomes read-only. Do not describe this as deleting the history. If scheduling reports Pick when it starts or It has to end after it starts, correct those fields and retry once. A server error about no meeting reservation definition requires the organization administrator to run the supported initialization/provisioning route; changing the meeting title will not fix it. That provisioning dependency must be demonstrated in the target organization before a finished course can claim this path works.
Workspace Analytics and AI Approval Cards
Open the workspace's Analytics pane after creating the example tasks. Open tasks counts new, pending, in-progress and blocked tasks; compare it with the open Tasks view. Overdue identifies tasks past their due date. Items is a count of journal items rather than completed business outcomes. Active members is measured over the last 30 days, against total membership. The charts Tasks by status, Tasks by assignee, Items by type and Activity per week let you inspect the distribution behind those totals.
Use a disposable past-due task to investigate Overdue. Create it with yesterday's due date, reopen it to see the overdue marker, and inspect Analytics. Then complete or legitimately reschedule it and recheck the task and count. Keep the original timestamp and the change in the evidence. A failed-load state is not a zero, and a count alone cannot establish that the customer reviewed the proof. Open the corresponding task, file and conversation to understand what happened.
A team workspace can also contain an AI employee approval card created by that system. This is conditional material: a normal manual message is not an approval. When a real card exists, inspect its employee, proposed action, summary, amount if supplied, and Waiting for a decision status. An authorized administrator may select Approve or Reject. Reopen the corresponding work item in AI Employees' Approvals view and confirm the same decision. Then inspect the action's actual business record or output separately; Approved is permission to proceed, not proof of execution.
If the card says Only an admin can decide this, use the authorized administrator account. If another reviewer already decided in another window, refresh the card and follow the existing decision rather than attempting a second one. The card's conflict handling synchronizes with the work item. This course covers finding and reviewing such a card, not fabricating one or claiming the AI runtime has completed an untested action.
Workspace Settings, Archival and Access Recovery
As an administrator, open the workspace's Settings gear. Change What it is for to include Autumn review completed, then Save. Reopen Settings and verify it persisted. Name, Private and Ends on are also editable; direct-message contexts do not expose the privacy checkbox. Before changing a private workspace to public, understand that internal organization users may gain reading access. Make the test with harmless content and verify from a nonmember account.
For a disposable reviewer's access, set an imminent future end time on their Members row. Record it, wait until after that time, then reopen the space in the guest account. Check both the disappearance/access response and the retained history in the administrator's session. A browser still displaying an old page is not an effective-access test; reload and attempt a new read. If access appears wrong, compare the actual account email, membership status, external identity and expiry before changing unrelated organization permissions.
Once the example is complete, Settings offers Archive. Its confirmation says the workspace leaves everyone's list and nothing is deleted. Use this only after preserving the training records and choose Archive. Check the rail in both sessions. The server supports restoration, but this settings panel does not expose a demonstrated Restore control; retain the workspace ID and ask the administrator for the supported restore route if needed. Do not promise a menu that is absent, and do not use archival as evidence that every existing deep link has been denied.
Finish with three independent checks: Alex can find the completed task and its history before archival; the customer account sees only the intended workspace while active; and the agenda/meeting/task records agree on what was actually completed. To repeat the process independently, create a private Winter collection workspace, one agenda and one assigned task, invite the controlled reviewer, schedule a short meeting and change its time. You should be able to locate each object from the personal rail and the shared context, and explain which choice controls access, ownership, progress and time.
BusinessMade Workspace: Conversations, Tasks, Meetings and Shared Agendas — supporting guide
Understand the records and results
Explanatory diagram, not an application screenshot. Guest expiry and room privacy must be checked separately from organization access. It explains the distinctions used in the steps below; it does not establish a completed live workflow.
Overview
Open Overview → Workspace in BusinessMade. We will organize collaboration, shared tasks and reports while keeping membership and private messages deliberate.
BusinessMade navigation and scope
The /workspace route mounts the shared Workspace app. AI employee Chat opens /workspace?chat=
Prepare collaboration without confusing access scopes
Use a real colleague account from your BusinessMade organisation for the internal example. Organisation access is managed in Admin → Users and Roles & permissions; membership in a particular workspace is managed inside that workspace. Selecting a business location does not make a private conversation branch-private. Choose the workspace’s membership and visibility deliberately.
Start with a private training workspace and harmless files. The detailed examples below use Cedar and named colleagues only to keep records recognisable; substitute your own names and chosen people. Sending an invitation or posting to a joined conversation reaches other participants, so a private draft is not interchangeable with a sent message.
Capture gap: no matching BusinessMade Workspace session images were available in the inspected retained collection. The shared component and BusinessMade route are verified in source, but Appmint screenshots are not substituted as proof of this product’s navigation, membership or outcomes.
01. Workspace Navigation and Personal Views
Context
Workspace brings conversations and shared work together. Personal views help you find your own mentions, tasks and calendar without opening every space.
Action overview
Open Workspace. Visit Home, Inbox / Mentions, My Tasks, My Calendar and Recent Files, then search for the intended space.
Follow the steps
Use a training organization with Workspace access, two active colleague accounts and an optional customer or external test account whose inbox you control. In this course, Maya and Alex mean those actual accounts; replace example addresses such as [email protected] with the real test addresses selected in the people picker. Prepare a harmless PDF named Cedar collection proof.pdf in the file manager and a genuine test meeting link from your meeting provider. Workspace stores a joining link; the form does not create a Zoom, Meet or Teams room. Select future dates when following the example; the illustrative target is 16 October 2026.
Open Overview → Workspace from BusinessMade's sidebar. If the rail is collapsed, use Expand. Home is the personal starting point; Inbox / Mentions brings attention back to conversations; My Tasks, My Calendar and Recent Files collect personal work across joined spaces. These are different from the Tasks, Calendar and Files panes inside one workspace. A public space you merely read is not automatically a joined personal workspace.
Start on Home and then open My Tasks. An empty Nothing assigned to you is a valid result before we assign anything. A load failure with a retry control is a different condition: retry the request and check access before concluding there is no work. In Search everything, type Cedar and press Enter. The Search drawer groups task and activity results. Later, use this exact search to reopen the records we create. Preserve the workspace name when opening a result so you know which shared context you are reading.
The instructions below describe the current documented controls. They are a manuscript draft: persistence, invitation delivery, effective access and the completed collaboration still require a live walkthrough.
02. Workspace Creation, Conversations and Privacy
Context
A workspace and a conversation are different containers. Public or private visibility controls who can discover and participate; use the option that matches the intended audience.
Action overview
Choose New workspace or New conversation. Enter its name and description, select visibility and any end date, then Create and reopen it.
Follow the steps
Beside Workspaces, choose New workspace. Enter Name Cedar & Form — Autumn collection and What it is for Prepare the collection proof, review it with the customer, and record approval work. Select Private for this customer-facing exercise. A public workspace can be read by people in the organization; joining lets them post. Private means invited or added people only. A room inside the workspace is an organizational subdivision, not a separate access boundary: members can see the workspace's contents.
Leave Ends on (optional) blank while learning. A date here makes the whole space stop being readable at that time; it does not delete the records. That differs from a member's access end date, which affects that person, and an individual item's expiry. For a time-limited review, choose a future date only after the whole task and follow-up period are understood.
In Members, search for Alex and select the correct account by its email. Each selected row shows the person, an external flag and Access ends on. Keep Alex internal and leave their access end blank. Choose Create. The expected result is the newly named workspace opening with its panes, membership count and private indicator. Reopen it from the rail to check the name and description persisted. If you see Give it a name, supply the Name; repeated Create clicks do not cure validation.
For a lighter discussion, the Conversations heading has New conversation with the same name, purpose, privacy and expiry choices. Conversations default private and their composer omits task and agenda creation; choose the full workspace when those objects are central to the work. Direct messages use Direct messages → New message or Messages, or the Message button beside an active member. This route opens the messaging interface; do not search for a direct-message checkbox in the workspace creation drawer.
03. Members, External Guests and Access Expiry
Context
Members can include organization users and supported external participants. Roles and expiry control their access, which should be tested through the participant’s own account.
Action overview
Open Members, add the intended person, set the role and expiry, and save. Inspect the member list, then verify the participant can reach only the intended space.
Follow the steps
Open Members in the Cedar workspace. Existing rows identify the owner, external members, invited people and expired membership. invited means acceptance is still pending; it is not proof of delivered mail or successful login. Add the customer by searching Add someone. If you need temporary access, first choose Set access end, select a future date and time, then pick the person: choosing a person triggers the add request immediately. For an outside reviewer, type a real controlled external address and select the invite result. The intended guest scope is this workspace, not organization-wide browsing.
As a workspace administrator, use a non-owner row's admin, member or guest control to change access type. Leave Alex as member and choose guest for the external reviewer. Admin controls are not shown for changing the owner's own role. Role changes and access-end changes are saved through their controls; revisit the row and Activity to check the resulting membership event. Do not assume that “guest” makes individual messages private from other workspace members.
Test visibility in separate signed-in browser sessions. Alex should see the private Cedar workspace after membership is active; a colleague not added should not discover it. The reviewer must actually accept the invitation and open the workspace before guest access can be called verified. Also try browsing other public spaces from that external account; the access service intends external people to see only spaces they are named in. If an invitation remains pending, verify the exact email, the receiving account and the delivery/invitation service with the administrator. There is no demonstrated resend workflow in this Members panel.
To understand the public alternative, create a harmless second workspace named Cedar team announcements with Private unchecked. From an internal nonmember account, use Browse public workspaces and conversations, then Read. The bottom bar explains Join to post. Choose Join, verify the composer appears, and post a test message. Joining changes membership; merely opening Read does not.
For removal, use Remove on a non-owner member row and confirm Remove. Their earlier posts stay in history. A non-owner member can instead choose Leave this workspace and confirm Leave. Test the removed person's access again: in a public space an internal nonmember may still read, so removal alone is not a confidentiality control. Use a private space for the restricted review.
04. Rooms, Messages, Mentions, Replies and Shared Files
Concept diagram, not a screenshot or a completed-action record. A conversation audience and a task assignee are separate choices. Verify both.
Context
Rooms organize discussion. Mentions, replies, pinned messages and files give the team ways to retain context without creating another space for every message.
Action overview
Open the room, send a message and mention the intended member. Reply in its thread, attach a file and pin the relevant message. Reopen the thread and file as a member.
Follow the steps
Select Activity. The header describes everything, newest first. Use New room, type proof-review, and press Enter. Open that room before composing so the post belongs to it. Enter @[email protected] Please check the crop on the autumn collection proof. using Alex's real account email after the @ sign. Use Attach a file, choose Cedar collection proof.pdf in the file manager, confirm the selected file, then Send. The keyboard shortcut is Command+Enter or Control+Enter; ordinary Enter can remain part of the message.
Check the posted card for its author, text, room context, timestamp and attachment. Open the attachment and verify it is the intended proof. Then check Inbox / Mentions as Alex. A saved card is not delivery proof; the second account's visible mention is the useful handoff check.
On the post choose Reply. Write Crop checked; the right margin needs another 3 mm. and Send in the Replies drawer. Return to the parent card and inspect its reply count. Threaded replies keep that decision beside the original proof. Hover over a card to reveal Pin; select it and later Unpin to reverse the choice. A pin marks an item for the workspace; it does not grant access to somebody who lacks membership. Use Older to load earlier activity when necessary.
A message may be sent with files even if its text is empty. Files inside the space and Recent Files in the personal rail provide another route back to shared material. Open Files and inspect the same card, then follow its file link. A linked task or meeting on an activity card opens the corresponding detail drawer; use the linked record title rather than recreating a second record from its description.
The composer also offers item expiry. Leave it unset for decisions that need to remain available; apply a short expiry only to a disposable test post and verify its later disappearance separately. To remove an incorrect test post, the author or administrator can choose Delete and confirm. The UI explains that a removed card stays in the timeline while its content goes. It is different from deleting the workspace, and deleting a post should not be used as a substitute for correcting a task's status.
05. Workspace Tasks and Activity History
Context
Workspace tasks carry assignment, timing and status. The history shows how work changed; the card alone does not establish that the assignee received or completed it.
Action overview
Create a task with title, description, assignee and due date. Save, open its detail, update status and inspect its activity history.
Follow the steps
Inside the workspace, use Tasks → New task, or New task in Activity's composer. Enter Title Prepare autumn collection proof; in Details, enter Export the approved crop to Cedar collection proof.pdf. Attach the revised PDF and record which version the customer should review. Select Alex in Assign to, set Due to 14 October 2026 (or a future training date), and choose No agenda for now. Add the proof file through Files. Leave item expiry unset and choose Create task. A title is required; the form reports Give the task a title if it is blank.
Open the new task. Its title, author, room, Status, Due, Assigned to, Agenda, Description, Files, Comments and History are the operational record. In Alex's session, open My Tasks and find the same title. Use the status button and its Move to menu to select In progress. Later select Done after attaching the revised proof. These task statuses describe this shared piece of work; they do not by themselves approve an AI action or run a staged Workflow definition.
To update the description, choose Edit, change the text and Save. Title edits save when focus leaves the title. Due, assignment, agenda and status controls save when changed. Reopen the drawer after each meaningful change and read History, which lists status/assignment changes, time and actor. Add a comment explaining Revised PDF attached; right margin corrected. so another person can understand the result without reconstructing the conversation.
In Tasks, switch between Board and List. Board supports dragging a task into a visible status column; the detail status menu is the precise alternative. Use Search tasks, Open / Closed / All, Every agenda / No agenda, and the person filter to narrow the list. A completed task disappearing from Open is expected. Select Closed or All and use List when searching terminal statuses such as Approved, Rejected or Canceled that do not each have their own board column.
For a blocked proof, select Blocked, explain the missing asset in Comments, and keep the assignee visible. Once the asset is supplied, change back to In progress and verify history records the recovery. If Alex is absent from the picker, return to Members and verify active membership before retrying. If a drag fails, read its error and reopen the task; do not assume the optimistic movement saved.
06. Shared Agendas, Documents and Task Progress
Context
An agenda combines a shared document and linked tasks. Its completion should agree with the actual task progress.
Action overview
Create an agenda, set its lead and target date, save the document and link the intended tasks. Update one task and inspect the agenda’s progress.
Follow the steps
An agenda here is a project page with linked tasks, not merely the talking points of a meeting. Open Agenda → New agenda. Enter Title Autumn collection launch, Summary Customer proof review and final artwork handoff, select Maya as Lead, and set Target date to 16 October 2026. In Page, write Scope: autumn print collection. Acceptance: revised proof attached, customer review recorded, final artwork task complete. Choose Create agenda.
Open the agenda card. Its Page and task board share the view. Edit the document to add Review notes: check margins and product names, then choose Save page. This is distinct from the metadata Save action. Close and reopen the agenda to verify the text survived. Edit agenda changes Name, Summary, Lead, Target date and Status; choose Save after those edits. Status choices are Active, Paused and Done. Paused is useful when the customer has not supplied an essential asset; it does not automatically resolve the tasks.
Return to the proof task, choose Autumn collection launch in Agenda, and reopen the agenda to see the linked task. Create a second task there named Deliver final artwork, assign Alex and set a due date before the target. Tasks created in the embedded board belong to this agenda. When a workspace has exactly one agenda, the new-task form may preselect it; inspect the Agenda field rather than relying on an assumed default.
The agenda card and header show done/total progress and any overdue count. Move the proof task to Done, leave final artwork open, and compare the numerator and denominator. The Mark done action has a confirmation that explicitly warns when tasks remain open: they stay as they are. To finish the exercise faithfully, close the final artwork task after its actual handoff, then Mark done and confirm. If you marked the agenda done too soon, use Edit agenda to return Status to Active, save, finish the remaining task and mark it done again. Reopening an agenda is different from reopening each task.
For practice, add Winter collection with its own document, lead and one task. The check is not simply that another card exists: the Winter task must appear under Winter while the Autumn task counts remain unchanged. This tests whether you can use the agenda relationship deliberately.
07. Meetings and Calendar
Context
Meetings combine participants, timing and a joining destination. Calendar display and invitation delivery are distinct checks.
Action overview
Create the meeting, set participants, date, time and joining link, then save. Open the calendar entry and meeting detail. Test joining, then demonstrate an edit or cancellation on the disposable meeting.
Follow the steps
Return to Activity, select the proof-review room and choose New meeting. Enter Title Autumn proof review, Starts 15 October 2026 at 10:00 and Ends at 10:30, adjusted to future dates in your environment. The form uses the browser's time zone and stores it with the meeting. Read the saved time-zone label; do not assume a colleague in another location sees an identical wall-clock time.
Inspect Invite before saving. It initially includes eligible workspace members other than the organizer, excluding pending invited members. Remove people who do not need this review and add the active customer reviewer. Paste a genuine test provider URL in Meeting link. In Details, enter Review the revised proof. Confirm margins and product names. Read the Autumn collection launch agenda first. Attach the revised PDF using Files and choose Schedule.
The expected chain is an Activity event linked to a meeting record, a Calendar entry in this workspace, and an appropriate My Calendar entry for the invited account. Open the meeting title or linked record to inspect the drawer. Use Join to check the URL reaches the intended meeting service; this does not verify that a call was held. Inspect invitees and their displayed invitation status in the read-only participant view. This interface does not supply the RSVP buttons described by some older materials, so do not invent an Accept operation.
As an editor, change Starts and Ends to reschedule. Title and Meeting link edits save on leaving the field; Details → Edit → Save saves the description. Changes to Invited and Files use their own controls. Reopen the meeting and inspect the calendar from the invitee account after the change. Preserve both old and new timestamps in the production evidence so a notification claim can be checked independently of the saved record.
To cancel a disposable meeting, choose Cancel this meeting, read the confirmation, then Cancel meeting. The journal retains the record and the calendar title identifies cancellation; the drawer becomes read-only. Do not describe this as deleting the history. If scheduling reports Pick when it starts or It has to end after it starts, correct those fields and retry once. A server error about no meeting reservation definition requires the organization administrator to run the supported initialization/provisioning route; changing the meeting title will not fix it. That provisioning dependency must be demonstrated in the target organization before a finished course can claim this path works.
08. Workspace Analytics and AI Approval Cards
Context
Analytics summarizes the workspace’s actual activity. An AI approval card links to a specific work request and should be decided in that context.
Action overview
Open Analytics and compare task and overdue counts with the workspace. Where a genuine AI approval exists, open its linked request, inspect it and make the intended decision.
Follow the steps
Open the workspace's Analytics pane after creating the example tasks. Open tasks counts new, pending, in-progress and blocked tasks; compare it with the open Tasks view. Overdue identifies tasks past their due date. Items is a count of journal items rather than completed business outcomes. Active members is measured over the last 30 days, against total membership. The charts Tasks by status, Tasks by assignee, Items by type and Activity per week let you inspect the distribution behind those totals.
Use a disposable past-due task to investigate Overdue. Create it with yesterday's due date, reopen it to see the overdue marker, and inspect Analytics. Then complete or legitimately reschedule it and recheck the task and count. Keep the original timestamp and the change in the evidence. A failed-load state is not a zero, and a count alone cannot establish that the customer reviewed the proof. Open the corresponding task, file and conversation to understand what happened.
A team workspace can also contain an AI employee approval card created by that system. This is conditional material: a normal manual message is not an approval. When a real card exists, inspect its employee, proposed action, summary, amount if supplied, and Waiting for a decision status. An authorized administrator may select Approve or Reject. Reopen the corresponding work item in AI Employees' Approvals view and confirm the same decision. Then inspect the action's actual business record or output separately; Approved is permission to proceed, not proof of execution.
If the card says Only an admin can decide this, use the authorized administrator account. If another reviewer already decided in another window, refresh the card and follow the existing decision rather than attempting a second one. The card's conflict handling synchronizes with the work item. This course covers finding and reviewing such a card, not fabricating one or claiming the AI runtime has completed an untested action.
09. Workspace Settings, Archival and Access Recovery
Context
Settings and membership changes affect the space’s continuing use. Archive changes its normal visibility; do not assume it proves every deep link is inaccessible.
Action overview
Open workspace Settings and save the intended change. Remove a disposable member or archive a practice space, then verify the supported visibility behavior from another account.
Follow the steps
As an administrator, open the workspace's Settings gear. Change What it is for to include Autumn review completed, then Save. Reopen Settings and verify it persisted. Name, Private and Ends on are also editable; direct-message contexts do not expose the privacy checkbox. Before changing a private workspace to public, understand that internal organization users may gain reading access. Make the test with harmless content and verify from a nonmember account.
For a disposable reviewer's access, set an imminent future end time on their Members row. Record it, wait until after that time, then reopen the space in the guest account. Check both the disappearance/access response and the retained history in the administrator's session. A browser still displaying an old page is not an effective-access test; reload and attempt a new read. If access appears wrong, compare the actual account email, membership status, external identity and expiry before changing unrelated organization permissions.
Once the example is complete, Settings offers Archive. Its confirmation says the workspace leaves everyone's list and nothing is deleted. Use this only after preserving the training records and choose Archive. Check the rail in both sessions. The server supports restoration, but this settings panel does not expose a demonstrated Restore control; retain the workspace ID and ask the administrator for the supported restore route if needed. Do not promise a menu that is absent, and do not use archival as evidence that every existing deep link has been denied.
Finish with three independent checks: Alex can find the completed task and its history before archival; the customer account sees only the intended workspace while active; and the agenda/meeting/task records agree on what was actually completed. To repeat the process independently, create a private Winter collection workspace, one agenda and one assigned task, invite the controlled reviewer, schedule a short meeting and change its time. You should be able to locate each object from the personal rail and the shared context, and explain which choice controls access, ownership, progress and time.
Verification notes
The /workspace route mounts the shared Workspace app. AI employee Chat opens /workspace?chat=
Shared UI procedures are authored from the actual component mounted by the BusinessMade route registry. The changed wrapper/navigation has been source-inspected; new BusinessMade session, customer/provider outcomes and permission tests remain unperformed.