workspaces
Use case
Move from scattered work to shared outcomes
Keep files, context, AI assistance, and collaborators together from the first idea through the next iteration.
Unify data and AI work in a single environment
Your persistent home for projects, files, tools, and outcomes.
Bring notebooks, SQL, Python, files, configurations, AI-generated artifacts, and agent development assets into one governed workspace. Instead of spreading work across disconnected tools, teams can organize, build, reuse, and continue data and AI work from a shared environment that keeps project context intact.
- Organize work by workspace, folder, and file
- Keep notebooks, SQL, code, agent assets, configurations, and outputs together
- Resume work with persistent project context
- Reuse existing artifacts instead of recreating them
Give AI the context to become a teammate
Transform Tera from a general assistant into a collaborator grounded in your work.
Within a workspace, Tera can use the files and project context the user is permitted to access. Tera can help explain or improve work, reference relevant assets, and create supported artifacts directly in the shared environment rather than operating as a disconnected chat experience.
- Ground responses in workspace files and project context
- Reference notebooks, SQL, and other project assets
- Create supported artifacts directly in the workspace
- Keep AI-assisted work connected to the project
Bring people, tools, and governance together
Collaborate securely without losing control of project work.
Workspaces bring collaboration, compute, permissions, project assets, and AI development workflows into the same governed environment. Teams can share workspaces with the right people, work across notebooks and editors, and build solutions collaboratively while maintaining governed access as work moves from exploration to delivery.
- Share workspaces with designated team members
- Assign Owner, Editor, or Viewer access
- Use governed access across workspace assets
- Connect project files with notebooks, editors, and compute
Create once, use across connected experiences
Use the same files, context, and assets across connected AI experiences.
Workspaces provide a shared layer for notebooks, coding environments, AI tools, Tera, and connected AI Studio experiences. The same project files, permissions, agent assets, and context can move across development workflows, reducing duplication and making it easier to transition between building, testing, and operationalizing AI solutions.
- Use shared files and assets across connected AI experiences
- Apply a consistent permission model across project work
- Carry project context between development workflows
- Support both data exploration and AI solution creation
Collaborative data and AI development
A team starts a project in a workspace and organizes notebooks, SQL files, configurations, and supporting assets in one place. Team members work with shared access while Tera helps explain code, reference project context, and create supported artifacts. Because the project remains in the same governed environment, permitted teammates can find the work, understand its context, and continue without manually transferring files between disconnected tools.
swap_horiz
Less tool switching
groups
Shared project context
handshake
Easier handoffs
photo_filter
Governed AI assistance
FAQs
Teradata workspaces FAQ
What is Teradata Workspaces?
What is Teradata Workspaces?
Teradata Workspaces is a persistent, file-based environment for organizing and working on data and AI initiatives. It brings project files, supported tools, collaboration, and Tera context into one governed working space.
What can teams keep in a workspace?
What can teams keep in a workspace?
Teams can organize supported files such as notebooks, SQL, Python, configurations, skills, and generated artifacts in folders. The exact file types available may vary by release.
Does Workspaces replace notebooks, editors, or development tools?
Does Workspaces replace notebooks, editors, or development tools?
No. Workspaces provides the shared environment and project context in which supported notebooks, editors, Tera, and other connected experiences can work with the same files and governed access.
How does Tera work within a workspace?
How does Tera work within a workspace?
When used in a workspace, Tera can work with the files and context the user is permitted to access. Tera can help users understand and improve work and, where supported, create artifacts directly in the workspace.
How does Workspaces support collaboration?
How does Workspaces support collaboration?
Workspaces lets teams share a common project environment and build on the same files and context. Role-based access helps control who can view, edit, or manage the workspace.
Who is Workspaces for?
Who is Workspaces for?
Workspaces supports people who analyze data, write SQL or Python, work in notebooks, build data and AI solutions, or collaborate on enterprise projects.
How does Workspaces help reduce tool switching?
How does Workspaces help reduce tool switching?
Workspace files and project context are available across supported connected experiences, helping users continue work without repeatedly exporting, importing, or recreating project assets.
Is work in a workspace governed?
Is work in a workspace governed?
Workspaces supports governed access through workspace membership, roles, and policy controls. Tera and connected tools operate within the permissions available to the user.
Turn individual work into a shared foundation for data and AI innovation
See how Teradata Workspaces helps teams organize project work, collaborate with context, and build on governed enterprise data.