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.

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.

Audit Cell History in Fabric Plan shows who changed a planning cell, what changed, and when, and lets you undo any user’s change by restoring an earlier value. It is available now with the Native Planning Engine, in Public Preview.

Point-in-Time Restore

Return any selected cell to a value recorded by any user at any point in its available history.

Choose an entry from the cell’s timeline and restore that exact value. The restoration is captured as a new auditable change, so recovery does not break the history.

Key Capabilities

Important compatibility note: Cell History is available only with the Native Planning Engine. It relies on the engine’s file-based architecture in OneLake and is not supported by the previous planning engine.

Cell-Level Context with Point-in-Time Recovery

Fabric Plan already provides a detailed audit experience. The Data Input tab captures sheet-wide data activity: tag, action, row, column, old value, new value, user, and timestamp. The Reports tab captures report changes such as scaling, columns, and formatting.

Cell History complements those broad views with a focused, actionable timeline for the value a planner has selected. The row, measure, period, user, action, and value transitions are presented together, directly beside the planning grid. A planner can then select any recorded entry and restore that exact value to the cell.

Select the January Quantity Forecast for Canada › Home › Essential (6.30M) and open its complete change story in context.

Fabric Plan grid with the Cell History panel open beside a selected Quantity Forecast cell
Cell History opens beside the selected planning value and presents its recorded changes in sequence.

Two Views for Two Different Tasks

Report Audit explains how the report changed. Cell History explains, and can restore, one planning value.

Comparison of report-level audit changes and the cell-level change history for one value
Illustrative tables. Values are included to explain the interaction, not as benchmark data.

How Fabric Plan Cell History Works

Cell History is available for a leaf-level data-input cell. Select a specific intersection of business context and time, such as Canada, Home, Essential, January 2026, Quantity Forecast, and open Cell History. The side panel keeps that complete coordinate visible while it lists the recorded changes from newest to oldest.

Canada › Home › Essential › 2026 › January › Quantity Forecast

Example Change Sequence

Cell History timeline showing Bulk Edit, Allocation, Delete, Restored, Reset, Copy Paste and Initial Value entries
Illustrative timeline for one cell, newest first, back to its earliest recorded state.

Each entry identifies the mechanism that produced the change. A leaf value may have changed through direct input, an allocation from a parent, a bulk update, or pasted values. Cell History keeps those actions distinct.

Recorded Change Types

Change typeWhat it means
Initial ValueThe earliest recorded state of the cell, before any tracked change.
AllocationA value entered at a parent or subtotal was distributed down to this leaf cell.
Manual InputA planner directly edited this leaf-level value in the grid.
Bulk EditThe cell changed as part of a multi-cell update configured through Bulk Edit.
Copy PasteThe value was pasted from another grid range or from outside the planning experience.
DeleteThe planned value was removed, leaving the leaf cell blank until another action supplied a value.
RestoredA user intentionally returned the cell to one of its recorded historical values.
ResetThe cell returned to its configured default, or to blank when no default exists.

Filter by User, Action, or Time Period

A cell can accumulate many changes. The filter panel narrows the list while the selected cell remains fixed.

Example Filters

Show only allocations made by a specific user, isolate deleted values or manual inputs, or limit the list to a selected date range.

Cell History Actions filter listing Initial Value, Manual Input, Allocation, Bulk Edit and Delete
The Actions filter includes Delete, allowing users to isolate when planned values were removed.

Restore Any Recorded Value from Any Point in Time

Use Changed By, Actions, or Time Period to locate the exact entry. Select it and choose Restore to return the leaf cell to that recorded value, regardless of which user originally made the change. The restoration is recorded as another change in the cell history.

ActionWhat it does
RestoreReturn the selected cell to a specific value from any point in its available history.
DeleteRemove the current planned value. Cell History records the old value changing to blank as a Delete action.
ResetRemove the current planned input and return the cell to its configured default. If the default is blank, the cell returns to blank.

Using Cell History

  1. Select a leaf-level input cell. Choose the exact row, measure, and period whose value needs explanation.
  2. Open Cell History. The side panel is automatically scoped to that data point and displays the number of recorded changes.
  3. Read the timeline. Review the old and new values, action type, user, and timestamp for each change.
  4. Filter when necessary. Narrow the timeline by Changed By, Actions, or Time Period.
  5. Restore the selected point in time. Return the cell to that exact historical value; the restoration is added to the audit trail.
  6. Reset when needed. Return the cell to its configured default or blank state.

How Cell History Fits with Audit

The two experiences are complementary. Audit is designed for broad review and export, while Cell History is designed for focused investigation and recovery at the selected leaf-level cell.

Audit vs. Cell History

CapabilityAuditCell History
ScopeEntire report history across data-input and report-configuration activityOne selected leaf-level cell
Change contextReport-wide records for review and governanceWho changed it, What changed, and When
Undo and RestoreNot supportedUndo a specific change by restoring its selected historical value
ExportExport the entire report history to ExcelCell-level history export is not supported
Data Input audit table showing sheet-wide actions, rows, columns, old and new values, users and timestamps
The Data Input audit remains the comprehensive sheet-wide record across planning activity.
Reports audit tab showing report configuration changes such as scaling and column updates
Report-level changes remain in the Reports audit tab. Cell History focuses on the value itself.

Practical Result

Cell History turns audit information into a recovery workflow. A planner can see whether a value came from a direct edit, allocation, bulk update, paste, or deletion; identify the user and time; and restore the exact recorded value from any selected point in the cell’s available history.

The feature is intentionally narrow: it applies to a selected leaf-level input cell. Sheet-wide data changes remain in Data Input audit, and report configuration changes remain in Reports audit.

Feature details reflect Fabric Plan at the time of writing.

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.