How to Add a Column to a Table in Loop
You learn how to add a column to a table in Loop by clicking the plus icon on the table header. You can also hover between two existing columns to insert a new column right there. Teams often build shared workspace tables to track tasks, incidents, and release plans. When workspace roles are too broad, anyone can change the table structure or paste raw production data into shared pages. How to add a column to a table in Loop and set column types Loop stores tables as live components that sync
Human-in-the-Loop Approvals + End-to-End Encryption: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You learn how to add a column to a table in Loop by clicking the plus icon on the table header. You can also hover between two existing columns to insert a new column right there. Teams often build shared workspace tables to track tasks, incidents, and release plans. When workspace roles are too broad, anyone can change the table structure or paste raw production data into shared pages.
How to add a column to a table in Loop and set column types
Loop stores tables as live components that sync across different workspace pages and chat apps. When you edit a table, the app updates every linked page at the same time. To expand a table, move your cursor to the top border of any column header. A small plus button appears on the edge between two columns. Click that button to insert a blank column into the shared grid.
After you create the column, click its top header cell to name it and pick a data type. You can set the column to hold plain text, numbers, dates, user tags, or status labels. Choosing a specific column type helps the team keep shared records clean and structured. You can also drag the column header left or right to change its order in the table.
Workspace permissions decide who can add, move, or delete these columns. If a team member has edit rights on the page, they have edit rights on every table inside it. Anyone with page access can change column types or overwrite existing cell values.
What workspace roles solve and what they leave open
Native workspace permissions control who can open a page or edit a shared component. Teams can lock down specific pages so only certain groups can view or change the project tables. This setup stops unauthorized guests from reading internal notes or deleting project trackers.
Still, workspace roles only check who logs in to the document app. They do not control where the data inside those tables comes from. During an incident or support review, engineers often run queries against production databases and copy the results into Loop tables. Native workspace settings cannot stop someone from pasting real customer emails, phone numbers, or card numbers into a column.
Human-in-the-Loop Approvals + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Once sensitive records sit inside a shared table, every person in that workspace can read them. Also, database logs only show that an engineer ran a read query. Those logs do not link the database query to the workspace page where the data ended up. To prevent data leaks, teams must govern database sessions before records ever leave the production system.
Keeping sensitive database records out of shared tables
Good data hygiene starts at the database layer rather than inside the document editor. When engineers query production tables to gather stats for a team page, they should not pull raw personal data. Masking rules at the database session level rewrite sensitive fields like emails and card numbers in query results. Even if an engineer copies those results into a Loop table, the masked values stay safe to share.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Can I lock a single column in a Loop table so others cannot edit it?
No, permissions apply to the whole page or shared component rather than single columns. Anyone who can edit the table can also edit or delete any column inside it.
What happens to existing data when I change a column type in Loop?
The table tries to convert the existing cell values to match the new column format. If a text value does not fit a number or date format, the cell may show a formatting warning.
How do teams stop sensitive database records from ending up in shared tables?
Teams apply data masking during the database query session so results rewrite emails, phone numbers, and card numbers by default. Engineers can then copy the query output into workspace tables without exposing raw customer details.