Knowledge base and source traceability
The knowledge base is where GDDAO retains your organization's information. Understanding how it works explains why AI-generated content can be traced back to its sources.
Supported data types
- Documents: PDFs, Word documents, spreadsheets, and text files;
- Images: Photos and related image information;
- Audio and video: Recordings, videos, transcripts, and meeting excerpts;
- Webpages: URLs and captured webpage content;
- Folders: Folders for organizing documents, with configurable privacy and sharing scopes.
How information is retained
After a file is uploaded or imported, GDDAO:
- Parses text, images, or media;
- Produces summaries, transcripts, and searchable segments;
- Creates an index that AI can query and cite later.
Recordings can be transcribed again and revised. Web content can be saved and analyzed.
Finding the source of a figure later
Because all information is organized within the same knowledge base context, AI can cite sources directly when producing content. When you or a reviewer needs to verify a figure or statement, you can return to the relevant knowledge item and inspect the original document, photo, or transcript.
This is the key difference between GDDAO and a basic AI chat tool. The question is not only “What did AI say?” but “Which source supports this statement?”
Permissions and sharing: who owns and sees the data?
Access is restricted according to:
- Owner type: individual, project, or workspace;
- Workspace or organization scope;
- Project scope;
- Folder-level privacy and sharing settings.
Knowing a data item's ID does not let AI read it. Every access request is evaluated against these authorization scopes. You can invite an external collaborator to a specific project without exposing information from outside that project.
Next step
To understand how AI helps organize this information, read How AI collaborates.