I created a new Organization for my campus team and opened the workspace navigation menu. I expected an empty Organization, and I wanted to learn why initial resources were already listed.
What happened
I found a Default workspace and a pre-configured General Assistant Agent in my account upon first login. I opened the workspace and reviewed the Agent settings to determine if our team should use them.
What I tried
I looked through Organization settings to see whether our team is expected to build on these resources or replace them with our own. I wanted to clarify their operational purpose before adding institutional materials or inviting staff members.
Creating an Organization automatically generates a Default workspace and a General Assistant Agent. Both are ordinary resources your team can rename, reconfigure, or set aside in favor of your own, so treat them as a starting point rather than a requirement.
Why this happens
The initial workspace and Agent give your Organization a functional starting point immediately after setup, so a new administrator can explore platform features right away instead of configuring anything first.
What each one is for
Resource
Purpose
Behavior worth knowing
Default workspace
A place for general team collaboration from the moment the Organization exists
Auto-join is on, so people you invite to the Organization land here without a separate workspace invitation
General Assistant
Testing basic Chat interactions without configuring a custom Agent first
Carries a Built-in badge and picks up new Agent capabilities as they ship, so its feature set grows over time
What to do
Decide how you want Workspaces organized. Use the Default workspace for general team collaboration, or create separate Workspaces if your governance model requires administrative boundaries.
Review the General Assistant settings and system instructions before introducing institutional documents.
Create additional custom Agents using a blank setup, the Template Catalog, imported JSON, or the AI Agent Builder wizard.
Use the conversational Agent Builder editor to modify an Agent that already exists, and review its proposed changes before applying them.
If you would rather build your own
Both behave like any workspace or Agent your team creates, so the usual options apply:
Rename or repurpose the workspace to match how your campus organizes teams.
Rewrite the General Assistant instructions, switch its model, or adjust its settings the same way you would for any Agent you built yourself.
Leave them idle and build your own Workspaces and Agents alongside them.
Delete the General Assistant like any other Agent if your team prefers to start from its own configuration. This needs the Agent delete permission and prompts you to re-enter your password.
Archive the Default workspace once your own Workspaces are established. Archiving preserves existing history and is reversible, but it clears auto-join, so invite colleagues to a specific workspace afterwards rather than relying on Organization membership alone.
How to verify
The resources are listed. Open your Organization navigation menu, view the Workspace list, and confirm the Default workspace and General Assistant Agent appear in your account.
Members can use them. Verify that workspace members can access the Default workspace and initiate Chat sessions.
If it still does not work
If workspace resources do not appear, or return error messages, post your setup steps in a support topic. Keep private internal links, passwords, and institutional API keys out of the post, and include the redacted error details along with whether your Organization was created recently.