Skip to content

Bring the class together. Keep the thinking visible.

Students collaborating around shared research, evidence, and a finished project

Support the work behind the outcome

Group work needs more than a shared deadline.

Students must coordinate roles, combine their contributions, and explain their decisions. Instructors need opportunities to discuss the process as well as the finished project.

Give each team a Room for its brief, Huddles, and working documents. Use review sessions to discuss contributions and reasoning. Students remain responsible for explaining and checking their work, including any AI assistance.

Research should survive a change of team.

When students graduate or collaborators move on, the reasoning behind an analysis can be harder to find than its final result.

Use shared documents and Huddles to record methods, decisions, and unresolved questions. For software projects, connect GitHub work to that context so the next researcher can follow how it developed.

Academic collaboration crosses boundaries.

A project can involve several departments or institutions, with different expectations for access, data handling, and AI use.

Invite collaborators into the relevant Room and agree what can be shared there. Before a pilot, involve the institution’s technology and accessibility teams in reviewing data handling, access needs, and permitted AI use. Keep restricted research and student records in institution-approved systems.

Give students room to explore without losing control of spend.

AI use can vary widely across students and projects, making class costs difficult to predict.

Use Room and user quotas to plan AI budgets for classes, teams, or students. Teachers with administrative access can review the Spend view and adjust quotas; other instructors can work with their workspace administrator. Plan an allocation for everyone taking part and review access needs as the work develops.

Make responsible AI use part of the assignment.

Students need clear guidance on when AI is appropriate, how to acknowledge its use, and how to check claims and sources. Instructors need to see the reasoning behind a polished result.

Keep the assignment’s AI-use rules and assessment criteria in a shared document. Use Huddles to review drafts, discuss evidence, and ask students to explain their choices. Students remain accountable for the work they submit.

Make the pilot useful for teachers as well as students.

A new tool takes time to learn. A successful pilot should help students develop skills and give instructors a workable way to guide and review their progress.

Start with one assignment and agree how you will assess learning, participation, and staff effort. Use shared documents to record feedback and refine the activity. Plan how final work reaches the institution’s existing learning platform or research repository.

A shared workspace for inquiry.

Bring students, instructors, researchers, and AI agents into the same discussion to develop ideas, review drafts, and build project software. Use Room and user quotas to set AI spending boundaries for a class or research team.

Features

Bring your next project into Webel.

  1. Set up the project

    Bring the assignment or research question, source material, and team into a Room. Agree learning goals, AI-use rules, access needs, and the budget with the people responsible for the pilot.

  2. Work through it together

    Discuss ideas, develop drafts, and review feedback in Huddles. Keep the reasoning behind changes alongside the work.

  3. Share the results

    Prepare a presentation, paper, or working prototype. Review learning and staff effort before expanding the pilot, and leave methods and next steps for the people taking the work forward.

Sign up