Community Files and Tasks - Article
Summary
Community Files and Tasks help a group turn conversation into practical work. Use Files for shared materials and Tasks for clear actions assigned to members. Keep resources organized, name the person responsible for each action, and use formal learning tools when the outcome requires submission, assessment, or certification evidence.
Use this article to:
- Organize and maintain shared Community materials.
- Understand the dependencies for editing supported files through Microsoft integration.
- Create tasks with clear assignees, dates, and expected outcomes.
- Distinguish collaborative work from formal learning requirements.
Decide where the work belongs
| Requirement | Use | Why |
|---|---|---|
| Share a template, working example, or meeting resource with a group | Community Files | The material belongs to the collaboration space and should be findable beyond one comment. |
| Ask a member to prepare, review, or follow up on something | Community Tasks | The action needs an assignee and a due date, not necessarily a formal learning result. |
| Deliver the maintained learning content of a course | Course content or the appropriate managed resource | The material should be governed as part of the formal learning experience. |
| Collect and evaluate required learner work | An Assignment module | Submission and assessment need a formal record. |
| Arrange a shared live working session | Community Calendar | Participants need a scheduled event and joining information. |
Files and Tasks must be enabled in the Community's feature settings described in Create and Manage Communities. Available actions also depend on the user's membership, ownership, and administrative permissions; review Community Membership and Access when the feature is visible but an action is unavailable.
Use Community Files
Open the Community and select Files. The shared file area supports uploading, folders, searching, filtering, downloading, and permitted file-management actions.
In the current interface, a file entry identifies its name, size, uploader, and upload date. Use that context to select the intended material rather than relying on the title alone.
| Action | Purpose | Good practice |
|---|---|---|
| Upload | Add one or more files to the shared area. | Use an approved file, recognizable name, and appropriate content for the entire Community audience. |
| Create folder | Group related working materials. | Use a small structure such as Preparation, Examples, and Meeting resources. |
| Search and filters | Locate material by the available file and discussion context. | Check filters when an expected file is not immediately visible. |
| Download | Obtain a local copy. | Remember that a downloaded copy will not automatically become the latest maintained version. |
| Rename | Make the file easier to recognize. | Include meaningful subject, language, or edition information where needed. |
| Manage tags | Improve findability through relevant labels. | Use consistent terms rather than separate tags for minor spelling variants. |
| Move | Place a file in the appropriate folder. | Keep the agreed structure understandable for existing members. |
| Replace | Update a file through the supported replacement action. | Review dependent conversations and tell members about a material correction. |
| Delete | Remove a file that should no longer be available. | Review whether it remains necessary as a working resource or retained record before confirming. |
Files attached to discussions and topics can be associated with their discussion context, helping members locate materials from a conversation. Discussions, Topics, and Community Facilitation explains how to keep that conversation structure useful. Do not assume that every upload must be rediscovered by scrolling through comments.
Keep one maintained resource
If a facilitator corrects a preparation workbook, use the maintained file location and explain the revision. Avoid leaving several similarly named copies across topics and folders without telling members which one applies.
Where the file's version-history controls are available, use them to inspect or restore an earlier replacement. Confirm that the required version exists before relying on recovery. Version history is not a substitute for an approved retention or backup process.
Edit supported files with Microsoft integration
When the relevant Microsoft integration is configured, supported files can be edited through the integrated experience instead of repeatedly downloading and uploading them.
An account may need to connect its Microsoft identity before direct file editing is available. If prompted, connect the appropriate Microsoft account and confirm that the file opens for editing. Permission to upload or download a file does not by itself establish permission to edit it through Microsoft.
| Dependency | What to confirm |
|---|---|
| Integration | The platform's Microsoft file-editing integration is configured and available. |
| Identity | The user has the required connected Microsoft account and access. |
| File support | The specific file type can be opened in the supported editing experience. |
| Collaboration process | Members know which shared copy is authoritative and how to confirm that their edits have saved. |
Use the Microsoft integration guide for setup and service-specific requirements. Do not promise that every uploaded format can be edited online.
Use Community Tasks
Tasks provide practical coordination within the Community. Any member can create a task and assign relevant members. Tasks are visible within the Community rather than serving as private messages to the assignee.
The task view includes search, task-selection controls, and a timeline. Check the selected period and filter before concluding that the Community has no tasks.
Create a task
- Open the Community's Tasks tab and select Create task.
- Enter a specific Title that describes the action.
- Set the optional Starts date/time when useful and the required Ends date/time.
- Check the time-zone selection.
- Select the required Assignee or assignees from the available members.
- Write the Description, including the expected result and any relevant materials.
- Review Notify assignee by email, then select Create.
The form can contain preselected dates and times. Replace these with the intended working period; a default is not an agreed deadline.
| Field | What to put there | Example |
|---|---|---|
| Title | A recognizable action and outcome. | “Prepare two anonymized examples for the handover workshop” |
| Starts | When the work should begin, if that information helps coordination. | The day after the preparation session. |
| Ends | The agreed due date and time. | The working day before the review meeting. |
| Assignee | The member or members expected to carry out the action. | The group representatives preparing the examples. |
| Description | Scope, expected output, links, and relevant boundaries. | “Use the shared template; remove customer and personal details.” |
| Notify assignee by email | Whether the selected assignees should receive the task notification. | Enable for a new action they need to notice outside their next platform visit. |
Follow up and complete tasks
Use the task overview and available task controls to review work and mark completion. Agree who is responsible for confirming that the result is adequate.
For a task with several assignees, explain how they should coordinate and who closes the loop. Do not treat the task as individual assessment evidence for every named person unless a separate validated learning process provides that evidence.
A completed Community task is not automatically a completed Course, passed Assignment, or issued certificate. If the action must count toward a formal learning outcome, configure the relevant Assignment, module, completion criteria, or Certificate requirement.
Practical designs
| Scenario and requirement | Recommended approach | Why and what to check |
|---|---|---|
| Workshop preparation | Store the current template in Files and create a task to prepare a short example before the meeting. | The action and resource have clear locations. Verify that the deadline precedes the session. |
| Customer implementation working group | Use folders for agreed working areas and tasks for specific follow-up actions. | Keeps collaboration manageable without claiming to replace a complete project-management system. |
| Peer review of a draft resource | Share one maintained copy, assign the review, and discuss the feedback in a focused topic. | Avoids competing versions and separates the review action from the conversation. |
| Assessed group project | Use Community Files and discussion for working material, then submit through a Group Assignment. | The learning result is recorded through the formal submission and assessment process. |
Protect the shared space
Upload only material appropriate for the Community audience. A private Community can still contain people from several organizations. Do not include confidential customer cases, credentials, or unnecessary personal details in filenames, task descriptions, or shared working documents.
Keep file names and folders understandable, and remove uncertainty about which copy is current. Technical ability to upload a file does not make it an approved file type or a suitable way to distribute software.
Verify the setup
| Verify | Expected outcome |
|---|---|
| Resource access | An ordinary member can find and open the intended material. |
| File editing | Where required, the connected user can edit a supported file and confirm the saved result. |
| Task responsibility | The assignee knows the expected output and deadline. |
| Formal evidence | Required assessment or completion is recorded separately through the appropriate learning process. |
Troubleshooting
| Problem | What to check |
|---|---|
| Files or Tasks is missing | Confirm that the feature is enabled for this Community and the user is an appropriate member. |
| A file appears to be missing | Check search, folders, and filters, then confirm whether it was renamed, moved, replaced, or removed by an authorized user. |
| A user can download but cannot edit a file online | Check Microsoft integration, account connection, permissions, and supported file type. |
| Members use different versions | Identify the maintained copy, explain which version applies, and review duplicate uploads or downloaded copies. |
| An assignee is not available | Verify Community membership and the selection scope. A person enrolled in a related activity is not necessarily already a member of this Community. |
| The task list is empty | Check the period shown on the timeline, task filter, and search before assuming no tasks exist. |
| A task notification did not arrive | Check the task's notification option, the assignee, Community system-email configuration, and user notification preferences; investigate delivery through Email Sending as needed. |
| Completing a task did not complete training | Community Tasks are not formal Assignment submissions or automatic certification criteria. Review the intended learning design. |
FAQ
-
Can Community members edit every file online?
No. Online editing depends on the configured Microsoft integration, the user's account connection and permissions, and supported file types. Upload or download access alone does not establish online editing capability.
-
Are Community Tasks private to their assignees?
No. Tasks are visible within the Community. Do not use a task description as a confidential message to one member.
-
Does completing a Community Task complete an Assignment?
No. Community Tasks coordinate practical work. Formal Assignment submission and assessment must be handled through the Assignment module.
-
Why does the task timeline show no tasks?
Check the selected period, task filter, and search. An empty current period does not prove that no tasks exist elsewhere in the Community timeline.
-
Should working documents be kept in comments or Files?
Comments can provide context and relevant attachments. Use Files as the maintained location for resources members need to find and reuse, and direct conversations to the correct current copy.