Entry ID comes first, then up to six property columns, then Last modified and Created as relative times (“1 year ago”).
The table shows at most six property columns — the first six by display order, whatever they are. To change which six appear, move the ones you want into the first six positions in Display sections and order. Every property, columned or not, is still visible on the entry itself — click a row to open it.
A cell with no value shows —. List values are joined for display, and a localized property shows the value for one language — the tenant’s default when the source carries it, otherwise the first language found in the source.
The search matches anywhere in the entry ID, not just the beginning — searching 0324 finds 715332-0324. It searches entry IDs only, not property values.
Click a column header to sort. Entry ID and Last modified always sort. Property columns sort only when the property has the Indexing capability — the rest render as plain headers with a tooltip saying why, because the search index can only order on what it indexes. Created never sorts: the index does not keep a creation timestamp.Sorting is applied by the backend across the whole source, not just the rows already loaded.
Refresh re-runs the query. It is worth pressing after an import: entries appear as the background job writes them. While an import you started is still running the widget polls on its own and shows Import is in progress.
A source with no entries shows No entries with an Import data button. CSV is the only format that can be imported from Studio. Another option is to use the Ingest API
