The problem it solves
Traditional file-based workflows fragment your work: one person has the “final” version, another has “final-v2,” and a third is still editing the original. Google Product replaces this pattern with a single source of truth that everyone accesses simultaneously. Changes appear instantly for all collaborators, and nothing is ever lost.Core objects
Google Product is built around a hierarchy of objects. Understanding how they relate to each other helps you stay organized and in control of your work.| Object | What it is |
|---|---|
| Workspace | Your organization’s top-level environment. All projects, documents, and members belong to a workspace. |
| Project | A container that groups related documents around a shared goal or team. |
| Document | The primary unit of work — a page, file, or record where content lives. |
| User | Any person with access to the workspace, assigned a role (viewer, commenter, or editor). |
| Label | A tag you apply to documents to categorize them across projects. |
| Share link | A URL that grants access to a specific document without requiring a full workspace invitation. |
How data flows through the product
When you create or edit content, Google Product saves your changes automatically and in real time. Here is the typical flow:- You sign in to your workspace using your Google account.
- You open or create a project to organize a body of work.
- Inside the project, you create documents — the actual content you write, review, and share.
- Documents are stored in Google Drive and synced automatically, so they are always available from any device.
- You share documents with teammates by inviting them directly or generating a share link with a specific permission level.
- Collaborators edit simultaneously, and all changes are merged and saved automatically.
Object relationships
The hierarchy below shows how objects nest inside one another:A document always belongs to exactly one project, but you can apply labels to make it discoverable across multiple contexts without moving it.
Quick-reference summary
Workspace
The top-level organizational boundary. One workspace per organization or team.
Project
A logical group of documents. Use projects to separate teams, clients, or initiatives.
Document
The unit of content. Documents live in projects, can be shared externally, and maintain full version history.
User
Anyone with workspace access. Permissions are set per document or per project.
Label
Cross-project tags that help you filter and surface related content quickly.
Share link
A URL that grants read, comment, or edit access to anyone — no account required for viewers.
Next steps
Now that you understand the data model, learn about the features built on top of it:- Key features — what Google Product can do for you
- Workflows — common end-to-end user journeys