Projects are the primary container for your work in Summation — they hold your data, reports, dashboards, decks, knowledge, and chats with Addison.
A project is the primary container for work in Summation. It holds your data connections, files, reports, dashboards, decks, and chat threads with Addison. Almost everything you do in Summation happens inside a project, so creating (or picking) the right project is usually the first step.
A sample project home page named 'Sample Test Project'
Reports, dashboards, and decks are stored as Summation document files — the extension in parentheses is what you’ll see in the file browser and when working via the API:
Component
Description
Chat threads
Conversations with Addison, scoped to the project’s data
Organization-wide context Addison reads in every project
Files
Uploaded files (CSV, Excel, PDF, PowerPoint, and more)
What’s scoped to what. Chat threads, reports, dashboards, decks, and uploaded files belong to the project — create one here and it isn’t visible from another project. Tables and views are tenant-wide: you attach existing ones to control what Addison can see here — an empty project catalog means Addison has no data context — but they live outside any single project. Knowledge is shared organization-wide, so the same context applies everywhere Addison works.
Every user has a default project named “My Project”. When you chat with Addison, the project picker on the composer sets which project the conversation reads from and writes to; search and pick one. If you don’t pick a project, the chat uses your default project, and everything it generates (reports, dashboards, files) is saved there. The default project is exempt from the project-management actions on this page: its row in the list shows no ⋯ menu, its workspace shows a disabled lock in place of the project-actions menu, and the delete API returns 403 (“Only standard projects can be deleted”).
Your projects are listed at /projects; recent ones also appear on /home. Click a project to open its workspace at /projects/{projectId}. Right-click any project in the list to Open in new tab, Pin it to the top, Rename, Duplicate (copy), Share, or Delete it.
Go to /projects and click New Project (top-right). This immediately creates a project named Untitled Project — there’s no dialog — and drops you into its workspace with the title in inline-rename mode, ready for you to type a name.
Click the project title at the top of the workspace — a Click to rename tooltip appears; type the new name, and edit the “Add description…” field below it. Changes apply immediately across the product.
Click the title to rename
PATCH /v1/projects/{projectId}
Update a project’s name, description, or visibility. Changing visibility requires that you be an Owner or Manager. visibility accepts only private or public; setting it public shares the project org-wide with Editor access — there’s no view-only option on this endpoint, so use the Share dialog if you need org-wide read-only.
Open the ⋯ menu in the top-right toolbar and choose Delete. This is a soft delete: the project is removed from your workspace (the confirm dialog notes it clears the project’s chats, files, and workflows), but the underlying files and data are retained on the backend rather than erased. Tables and views (tenant-wide) and Knowledge (organization-wide) aren’t scoped to the project, so neither is affected.
Open the Share dialog from the ⋯ menu in the workspace’s top-right → Share (or by right-clicking a project in the list → Share). The dialog controls who can open the project and what they can do.
The Share dialog
Roles. Each person you add gets one role:
Role
Can do
Viewer
Open the project and see its contents — read-only.
Editor
Everything a Viewer can, plus create and edit the project’s data, reports, dashboards, and decks, and delete the project.
Manager
Everything an Editor can, plus manage sharing (add/remove members, change roles, change general access) and change the project’s visibility.
General access. Beyond the people you invite individually, you can open a project to everyone in your organization:
General access
Who can open it
Only those invited
Only the people added above.
Anyone in your org can view
Everyone in your organization, with Viewer access.
Anyone in your org can edit
Everyone in your organization, with Editor access.
Bring data into a project with + Import in the workspace’s top-right — either Upload Files or Data connections.
In the app
Via the API
Upload files. Add local files — CSV, Excel, PDF, PowerPoint, and more. Uploaded files are scoped to this project.
The Import menu
Attach a data connection. Link an existing tenant-wide Summation table or view, or a connector’s data, into this project — you’re referencing existing data, not creating a new connection. The data attached to a project is exactly what Addison can see there — attaching controls its data context, and an empty project catalog means Addison has no data to work with. Choose Data connections in the Import menu, then Link a source.
Link a tenant-wide data source into the project
POST /v1/projects/{projectId}/files/uploads
Create a presigned upload.
POST /v1/projects/{projectId}/files/uploads/{uploadId}/finalize
Finalize the upload.
POST /v1/projects/{projectId}/files/{fileId}/imports
Import the finalized file into an analyzable table — required before a CSV can be queried. The curated MCP tool is import_file_to_table.
Attaching a data connection links an existing tenant-wide table or view into the project’s catalog (the curated MCP tool is attach_catalog_entry):
POST /v1/projects/{projectId}/catalog-entries
Attach a table or view to the project’s catalog.
GET /v1/projects/{projectId}/catalog-entries
List the tables and views attached to the project.
POST /v1/projects/{projectId}/catalog-entries/{catalogEntryId}/refreshes
Refresh a catalog entry’s schema from its source table or view.
From inside a project, click Create (top-right of the file list) to make a new Report, Deck, Dashboard, or Folder. Whatever you create belongs to that project — it’s scoped to the project and listed in its file browser alongside your data and files.
Create a report, deck, or dashboard from a project
Artifacts
Reports, dashboards, and decks are artifacts — see the Artifacts section for how to generate, verify, share, and export each type.
⌘I
Assistant
Responses are generated using AI and may contain mistakes.