docs(table-management-settings): add navigate to table by ID section#1498
Open
george-dilthey wants to merge 1 commit into
Open
docs(table-management-settings): add navigate to table by ID section#1498george-dilthey wants to merge 1 commit into
george-dilthey wants to merge 1 commit into
Conversation
Contributor
george-dilthey
marked this pull request as ready for review
July 10, 2026 18:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a "Navigate to a table by its ID" section to
docs/table-management-settings.md. The section documents the URL patternhttps://app.clay.com/workspaces/{workspace_id}/tables/{table_id}that lets users open a Clay table directly when they have its table ID, explains where to find the workspace ID and table ID, and calls out the Origin metadata field (which surfaces table IDs on rows sent from other tables).Why
Intercom conversation #215475022070325: a customer (Alan Davis, Medallion) saw a
Table Idin the Origin metadata of a Clay record and could not navigate to that table — the search bar returned no results. A Clay support agent (Smit Vekaria) resolved it by sharing the URL pattern manually. The docs had no coverage of this URL pattern for end users.Source link(s)
https://app.clay.com/workspaces/201578/tables/<table_id>clay-base/apps/frontend/src/routes/ui-routes.ts:542-553—buildTableUriconstructs/workspaces/${workspaceId}/tables/${tableId};WorkspaceRoutes.tsx:140-149— ungated route, no feature flag or role check.#ent-firstround-clay(https://clay-hq.slack.com/archives/C06H1M96RL4/p1775574756817109); Mark Larson in#ent-a-lign-clay(https://clay-hq.slack.com/archives/C08MFKP3DL1/p1775215283952129).Uncertainties
None. The URL pattern is confirmed PASS by the verifier sub-agent with file:line code evidence. It is an ungated route available to all users.
Related observations
docsbot/doc-1080-intercom-tag-0710-84b4df15) addressed the same gap and was merged first. This PR has minor phrasing differences in the same section — a reviewer may choose to close this as superseded or merge it for the wording improvements.Closes DOC-1079