ChatGPT for Edu K-12: Workspace Settings Guide
Introduction
This guide outlines the recommended workspace settings for K-12 districts, explaining what should be enabled, what should be restricted, and why. It provides the security, governance, and credit-usage rationale behind each configuration decision to help ensure safe, cost-effective deployment. Permissions
| | |
| | |
All Early Access Features | | Not included in service agreement |
| | |
| | |
Share chats with workspace | | Allows for easy collaboration |
Member and Group Visibility | | |
| | |
View workspace members and groups | | Allows for visibility to share GPTs |
| | |
| | |
Allow members to use memory | | ChatGPT will be more helpful by remembering details |
| | |
| | |
| | |
| | Unlocks ability to use Canvas features (edit code directly in chat) |
Canvas code network access | | Allows you to run code directly from Canvas |
| | |
| | |
| | Allows ChatGPT to use sources from the web |
| | 5 Deep Research queries/day included |
| | |
| | |
| | |
| | 3 Image Generation queries/day included |
| | |
| | |
Advanced Voice Capabilities | | Allows voice interactions with ChatGPT |
Allow members to share screen/video | | Voice is enhanced with extra context |
| | |
| | |
| | Requires credits to consume |
Device Code Authentication | | Requires credits to consume |
| | |
| | |
| | Requires credits to consume |
| | |
| | |
| | Refer to state laws on recording |
Allow ChatGPT to reference past notes | | Refer to state laws on recording |
| | |
| | |
Allow Code Edits on MacOS | | Requires credits to consume |
| | |
| | |
Redirect auto router to thinking mini | | Routes to lighter model when reasoning needed |
All other model permissions | | Requires credits to consume |
| | |
| | |
| | Allows for customization and users to build for repeatable tasks |
Publish GPTs to workspace | | Limit to administrators or particular role to make available GPTs easier to navigate |
| | Keep district information within workspace |
Allow all third party GPTs | | Keep district control of which GPTs get brought in |
Allow owner approved GPTs only | | Allows owner to decide to bring in GPTs from external sources |
| | |
| | |
Create and manage Projects | | Allows for users to group together chats with shared context |
| | Great tool for collaboration across teams/departments |
| | |
| | |
Allow members to use apps | | Decide which additional apps to include for context |
| | Allows for custom app integration if interested in connecting to district system |
Credit Limits
Recommended workspace settings
For all workspaces, set the default workspace limits here as follows: ● Usage alert: 1 credit/week
● Hard cap: 2 credits/week
This helps admins monitor usage early and prevents users from exceeding included features by default.
Important: Workspace limits are not automatically inherited by custom roles. If you use custom roles, you must manually apply the same limits unless you intentionally want those roles to have higher allowances.
If your workspace has not purchased credits
Keep the default workspace settings in place:
● Usage alert: 1 credit/week
● Hard cap: 2 credits/week
If you create custom roles, manually set those same limits on each role to maintain the default restrictions.
If your workspace has purchased credits
Start with the same default workspace settings:
● Usage alert: 1 credit/week
● Hard cap: 2 credits/week
Then use custom roles for users or groups who need additional credits.