Keep the case open to challenge
Review the collaboration controls and the project process they support.
Edit on GitHubYou have mapped who can work in a TEA case and what a public reader sees. A team role manages the team. A case grant determines access to the working argument. Comments let a reviewer question an element. Live updates help open views notice changes. Import and backup move copies of case data; integrations let an authorised service make selected machine calls. Publishing makes a public snapshot on Discover.
Those controls support a process that begins before a case is complete. During deliberation, invite perspectives that can change the goal. During design, turn concerns into strategies and claims. During testing and evidence generation, bring in people who can assess methods and results. Share the working case with the people doing that work, and choose public content only after its limits can be explained.
You Can Now
By the end of this module, you will be able to:
Choose appropriate team roles and case permissions for a collaborator.
Use comments and live changes to invite and respond to review.
Explain how sharing a working case differs from publishing to Discover.
Plan who contributes and what is shared at each project phase.
Identify when import, backup or an API token supports collaboration.
Return to your practice case and write one question you would ask a reviewer before considering publication. Keep the answer with the case, then check whether the current argument supports it. Use the quick reference as you work on future cases.