> ## Documentation Index
> Fetch the complete documentation index at: https://zite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Overview
> Bring your people, apps, and context together in one place to build and run the systems your team relies on.
A workspace is the project container for a Zite build. When you create a new app, form, or database, Zite provisions a workspace so the related pieces can live together.
Every workspace includes one database. You can then add as many apps and forms as the project needs, all connected to the same underlying data.
## What a workspace includes
Workspaces keep the operational parts of a project in one place.
Each workspace has one Zite Database for the records, tables, and relationships that power the project.
Add internal apps for your team and external apps for public pages, portals, or other shared experiences.
Add forms when you need to collect submissions, requests, files, approvals, or updates into the workspace database.
Add editors, manage the people who use each app, and configure database roles.
## Add apps and forms
A workspace can grow over time. Start with the app, form, or database you need first, then add more apps and forms as the workflow becomes clearer.
Apps can be:
* **Internal:** admin dashboards, team tools, review queues, operations panels, and other apps used by people inside your organization.
* **External:** public-facing apps, landing pages, client portals, partner portals, or other shared experiences that people outside your internal team can launch by link.
Because each workspace has one database, the apps and forms in that workspace can work around the same records instead of becoming separate projects.
## When to create another workspace
Use a new workspace when the project needs a separate database, a different team of editors, or a separate business system. Keep apps and forms in the same workspace when they should share data and be managed by the same team.
Common reasons to keep work in one workspace:
* An internal dashboard and public portal should use the same customer records
* A form should create or update records used by an app
* The same editors need to manage the database and apps
* Several apps represent different views of the same operation
Common reasons to create a separate workspace:
* The new project needs its own database
* A different team should manage editors, app members, and roles
* The apps and forms do not need to share records
* The project belongs to a different client, department, or business process
Related topics