> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/get-started/table-columns.md).

# Table columns

Reorder or hide the columns of a table, keep that layout on every device you sign in on, and — as an admin — set the layout and sort order your whole organization starts from.

Every table with a **Columns** button in its toolbar can be laid out the way you read it: drag the columns into the order you want, and switch off the ones you never look at.

Your layout is saved to your account, not to the browser, so it follows you to a second machine. It starts from whatever default your organization's admins have set.

Sorting works differently from the columns. Select the sort button in a column heading, choose **Asc** or **Desc**, and the list re-sorts for as long as you are looking at it — it is not saved to your account. What the [projects list](https://app.cogram.com/dashboard/projects) opens on is the order your organization's admins set, described below.

Each table keeps its own layout, so the order you set on the projects list has no effect on the documents register.

Tables with a Columns button today:

* [**Projects**](https://app.cogram.com/dashboard/projects) in the left sidebar, in list view — the button sits between the filters and the list/board toggle
* [**Projects**](https://app.cogram.com/dashboard/settings/admin/projects), [**Users**](https://app.cogram.com/dashboard/settings/admin/users), and [**Groups**](https://app.cogram.com/dashboard/settings/admin/groups) in Organization settings
* [**Workflows**](https://app.cogram.com/dashboard/agent/workflows)
* The documents register and the drawings register in [**Documents**](https://app.cogram.com/dashboard/documents), and the same two registers inside a project's own Documents tab

Board and schedule views have no columns to lay out, so the button appears in list view only.

## Change your own layout

1. Open the table and select **Columns** in the toolbar. The menu lists every column in the order the table shows them, left to right.
2. Drag a column by the grip on its left to move it up or down the list — up is further left in the table.
3. To move a column without a mouse, focus it with the arrow keys, then hold **Alt** and press **↑** or **↓**.
4. Clear a column's checkbox to hide it. Select it again to bring it back.
5. To hide or show every column at once, use **All columns** at the top of the list. A dash means some columns are hidden; select it to show them all.
6. Close the menu. Each change saves as you make it.

For example, to read a project's number before its name on the [projects list](https://app.cogram.com/dashboard/projects): open **Columns**, drag **Project number** to the top of the list, and close the menu.

**Expected result:** the table redraws in your order straight away, and the same order is there when you sign in from another computer.

One column in each table — the project name, a person's email, a document's file name — identifies the row. It has no grip, and its checkbox is fixed on: other columns move around it, and it cannot be hidden. Because it always stays, **All columns** shows a dash rather than an empty box even when every other column is hidden.

To undo your changes, select **Columns**, then:

* **All columns** brings back everything you hid, keeping your order.
* **Reset to organization default** (or **Reset to default layout**, when your organization has set none) drops your layout entirely.

## Set the default for your organization

Organization admins and owners see one more section in the menu. It applies to the table you have open.

1. Lay the table out the way your firm should see it, and sort it the way they should read it.
2. Select **Columns**. Under **For everyone in your organization**, **Now sorted by** names the order your firm is on today, and the save item names the one this click would publish — for example **Save these columns and the sort**, with **Sorted by Project number ↑** beneath it.
3. Select it.

**Expected result:** everyone in your organization opens the table on your sort, and everyone who has not laid that table out themselves sees your columns — including people who join later.

For example, to have every architect in the firm open the projects list by project number: sort the [projects list](https://app.cogram.com/dashboard/projects) by **Project number** ascending, then select **Columns > Save these columns and the sort**.

On a table Cogram cannot sort, the item reads **Save these columns** and only the columns are published.

Colleagues who have already laid the table out their own way keep the columns they set — a column default is a starting point, not a rule. The sort is different: it is the firm's, so everyone opens on it. Anyone can re-sort what they are looking at, and the list is back on your order next time they open it.

**Clear the organization default** removes the columns and the sort together. Anyone still on the default columns returns to Cogram's standard order, and everyone — colleagues with columns of their own included — goes back to the table's own sort.

## Ask the assistant

The assistant can do the same thing. "Put the project number before the name on the projects table" changes it for you; "…for everyone" sets the organization default, which the assistant can only do if you are an admin or owner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cogram.com/get-started/table-columns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.