Skip to content
Weavz
Menu

Professor Office Desk

A compact workspace for professors who want an AI assistant over teaching, advising, and academic coordination tools.

Built for professors and academic staff coordinating students, materials, and meetings

5 apps and tools · Everyday

Use this template

Sign in to preview and create this workspace. Account authorization and your plan limits still apply.

Setup documentation

Work you can try

Example requests for your agent after setup. Review drafts and confirm the intended accounts before any external action.

Prepare for office hours

“Review my office-hours calendar and relevant unread Gmail messages. Draft an agenda of questions and follow-ups with source links. Do not send replies or reschedule meetings.”

Expected output: An office-hours agenda grounded in messages and appointments.

Uses Gmail, Google Calendar

Set up, then try the first task

  1. Create a workspace from this template, or preview its setup in the dashboard.
  2. Connect the app accounts you want the agent to use. Check the requested permissions.
  3. Review the enabled actions. Add an optional approval rule if a particular action should ask first or be blocked.
  4. Connect your AI client or use your own agent, then try an example request.

Before you start

What does the Professor Office Desk template create?

A compact workspace for professors who want an AI assistant over teaching, advising, and academic coordination tools. It creates a configurable workspace with the listed integrations and Code Mode MCP access. You choose the accounts and permissions before asking your agent to act.

Does this template run an agent automatically?

No. A template prepares app access and workspace settings. Connect your accounts, attach an AI client or your own agent, and give it a task. Review the available actions and approval policies before enabling unattended work.

Are my connected accounts shared with other users?

Templates use per-user connections for supported account-based apps by default. Built-in files and state use end-user scope by default. Review connection strategies and access controls if your workspace needs shared accounts or shared state.

Related templates