Back to Blogs

PowerTable Column Access: Column-Level Security by Role

Lumel
Nov 2026

On this page

A logistics organization manages employee, warehouse, and shipment information across multiple locations. While different teams work with the same data, they do not all need access to every column.

Row-level security controls which records each user can see, but on its own it cannot restrict columns. Anyone with access to a record could see every column in it, including salaries and other sensitive details. That gap made it hard to share one table safely across teams.

PowerTable Column Access closes that gap by bringing column-level security to PowerTable. You can control who can view, insert, or update each column, role by role, while every team keeps working in the same shared table.

Here’s how it works in a logistics organization.

In this post:

1. Control Which Columns Users Can Access

One shared Employees table serves three teams with different needs.

Consider a logistics organization with 50 employees managing operations across five warehouses: Newark Gateway Logistics Park, Atlanta Southern Distribution Center, Chicago O’Hare Freight Hub, Dallas Lone Star Logistics Hub, and Los Angeles Pacific Port Terminal.

The Employees table contains Employee ID, Employee Name, Designation, Department, Work Email, Hourly Rate, Monthly Salary, Salary, Performance Rating, Is Active, and Warehouse Assignment.

  • HR Team: Needs access to employee details, including salary and hourly rate information.
  • Warehouse Managers: Need employee and operational information relevant to their warehouse.
  • Logistics Coordinators: Need basic employee and warehouse information to coordinate daily operations.

Without column-level access, users may be able to view or modify information that is not relevant to their responsibilities.

Column Access gives each column three permissions per role. Read shows or hides the column. Insert controls whether a user can enter a value in a new row. Update controls whether a user can change a value in an existing row. Settings apply to all roles or to specific roles, and when a user has several roles, an access is granted if any of those roles grant it.

2. Hide Sensitive Columns from Specific Roles

Turn off Read for a column, and it disappears for that role everywhere in PowerTable.

Problem: The HR team needs Salary, Hourly Rate, and Monthly Salary, but Warehouse Managers and Logistics Coordinators should not see them.

What changes: You can turn off Read for specific columns and roles. The column is hidden from the grid and from other product areas where columns can be selected, and Insert and Update are disabled for it.

User roleColumn access
HR TeamCan view all columns
Warehouse ManagerSalary, Hourly Rate, and Monthly Salary are hidden
Logistics CoordinatorSalary, Hourly Rate, and Monthly Salary are hidden
Access by role

What each role sees

HR view of the Employees table with Hourly Rate, Monthly Salary and Salary columns
HR view: Hourly Rate, Monthly Salary, and Salary are visible.
Logistics Coordinator view of the Employees table with Hourly Rate, Monthly Salary and Salary hidden
Logistics Coordinator view: the same table, with Hourly Rate, Monthly Salary, and Salary hidden.

How to configure

  1. Navigate to Security › Column Access.
  2. Under Select Table, choose Employees.
  3. Under Access applies to, choose Specific Roles.
  4. Add the Logistics Coordinator role and turn off Read for Salary, Hourly Rate, and Monthly Salary.
  5. Add the Warehouse Manager role and turn off Read for the same columns.
  6. Select Save Changes.
Column Access tab for the Logistics Coordinator role with Read off for Hourly Rate, Salary and Monthly Salary
Column Access for the Logistics Coordinator role. Read is off for Hourly Rate, Salary, and Monthly Salary, and Insert and Update are off for every column. Use Copy from another role and Reset to default to simplify configuration across similar roles.

3. Control Which Columns Users Can Update

Turn off Update for a column, and users can still see its values but can no longer change them.

Problem: Warehouse Managers need to keep the Is Active status of their team current, but should not change other employee details such as Department or Designation. Logistics Coordinators only need to view employee details. HR must keep the ability to update them all.

What changes: Update is controlled independently for each column. With Read on and Update off, the column is view only.

User roleDepartmentDesignationIs Active
HR TeamView and UpdateView and UpdateView and Update
Warehouse ManagerView onlyView onlyView and Update
Logistics CoordinatorView onlyView onlyView only
Access by role

What it looks like

Message shown when a Logistics Coordinator tries to edit the Department column
When a Logistics Coordinator tries to edit the Department column, PowerTable shows a message that the column is restricted for editing.

How to configure

  1. Navigate to Security › Column Access and select the Employees table.
  2. Choose Specific Roles and select the Warehouse Manager role.
  3. Keep Read enabled, and turn on Update only for Is Active.
  4. For the Logistics Coordinator role, keep Update off for every column.
  5. Select Save Changes.
Column Access tab for the Warehouse Manager role with Update on only for Is Active
Column Access for the Warehouse Manager role. Update is on only for Is Active, and Read is off for Hourly Rate, Salary, and Monthly Salary.

4. Combine Column Access with Row-Level Security

Pair Column Access with row-level security to control both which records and which columns each user can reach.

Problem: Each Warehouse Manager should see employees only from their own warehouse. The Dallas Warehouse Manager, for example, should not see records from Newark, Atlanta, Chicago, or Los Angeles. Column Access controls columns, not rows.

What changes: Row-Level Security (RLS) decides which records a user can access, and Column Access decides which columns. A policy limits the Dallas Warehouse Manager to records where Warehouse Assignment is Dallas Lone Star Logistics Hub, and Column Access hides Salary, Hourly Rate, and Monthly Salary for the Warehouse Manager role.

Access requirementResult
Warehouse-level accessOnly the 10 Dallas employee records
Column-level accessSalary, Hourly Rate, and Monthly Salary are hidden
Result

What it looks like

Warehouse Manager view showing the 10 Dallas employees with Hourly Rate, Monthly Salary and Salary hidden
The Dallas Warehouse Manager sees only the 10 employees assigned to Dallas Lone Star Logistics Hub out of the organization’s 50 employees. Salary, Hourly Rate, and Monthly Salary are hidden.

How to configure

  1. Navigate to Security › Column Access and select the Employees table.
  2. Choose Specific Roles and configure the Warehouse Manager role.
  3. Turn off Read for Salary, Hourly Rate, and Monthly Salary, then save.
  4. Configure an RLS policy that restricts the Warehouse Manager’s access to records belonging to the assigned warehouse.
  5. Attach the policy to the Warehouse Manager role.

PowerTable Column Access: Security That Reaches Every Column

Column Access completes PowerTable’s security model. Together with row-level security, it controls both which records and which columns each role can view, insert, and update.

One shared table. The right access for every role, down to the column.

Ready to secure your shared tables?

Feature details reflect Fabric Plan at the time of writing.

Share on:

Comments

0

Leave a Reply

More from the blog

Microsoft, Azure, Copilot, Excel, Fabric IQ, Microsoft Entra, Microsoft Fabric, Microsoft Teams, OneLake, Outlook, Power Automate, Power BI and SharePoint are trademarks of the Microsoft group of companies. IBCS is a registered trademark of IBCS Association. All other trademarks are the property of their respective owners.

This community is operated independently by Lumel. Nothing on this site constitutes a representation or warranty by Microsoft.
arrow-left