Hello Zoom team and community,

I’d like to request two enhancements for Zoom Docs that would significantly improve document security, data governance, and collaborative workflows:

1. Password Protection for Zoom Docs

It would be extremely helpful to have the option to password-protect individual documents. This feature would allow creators to restrict access even if a link is shared more widely than intended, adding an extra layer of security for sensitive or confidential information.

Key benefits:

• Prevents unauthorized access via leaked or forwarded links

• Adds an additional access-control layer beyond workspace permissions

• Helps organizations comply with internal security policies and external regulations

2. Record-Level Permissions for Data Tables

For teams that use data tables within Zoom Docs, the ability to set role-based permissions at the record (row) level would be transformative. This means different users or user groups could have restricted visibility or edit rights on specific rows.

This would enable:

• Confidential or sensitive rows to be visible only to authorized roles

• Controlled editing rights to reduce errors or unauthorized changes

• More flexible workflows for HR, finance, operations, research, and client-based work

• Improved data governance without needing separate documents or tables

These enhancements would make Zoom Docs a stronger fit for organizations that handle sensitive information while still leveraging the collaborative structure of Zoom’s ecosystem. Password protection addresses document-level security, while record-level permissions enable fine-grained control inside shared documents, providing a more enterprise-ready experience.

Thank you for considering these suggestions. I’d love to see Zoom Docs evolve with stronger permission controls, and I’m happy to provide additional context or use cases if helpful.

1. Reason for Rollup Reference Limitations in Formulas & Future Support Roadmap

Is the current inability to reference a Rollup column within a Formula (resulting in a #REF! error) an intended architectural decision designed to prevent performance bottlenecks (e.g., cascade updates) or circular dependencies? We would appreciate clarification on the technical reasoning behind this limitation. Furthermore, are there ongoing optimizations to address this, and if so, when can we expect this feature to be supported in your roadmap?

2. Schedule and Roadmap for Zoom Data Table API Re-release

Access to Zoom Data Table API endpoints is essential for our external automation and system integration plans.

Could you please share the specific schedule or roadmap regarding when the Zoom Tables API will be re-released or made officially available to developers?

Hi,

I'm trying to set up a project plan in Zoom Data Tables, and can't find a way to make dependent tasks.  For example, if row 1 had an end date of 10/10/25, I would want to make the next row's start date of 10/11/25.  Is there currently a way to configure this, or would this be a feature request?

Is there a fix to print a clean-looking Zoom document with a header that includes a data table? 
I've printed and distributed a PDF with a data table from Zoom Docs on Chrome for the past four months.  Recently (last week), the data table has been pushing itself 1 page down from where the header of the document is. No matter what I try, using different web engines, computers, deleting cookies, or changing print settings (page size, borders, scale, etc.), nothing seems to work. To add to this, the new PDF export also doesn't support data tables. 

If anyone has a workaround for printing a PDF with a data table, I'm all ears. 

All I know is that it was working two weeks ago, and now it's not. 

A field type that could be added to Zoom Docs data tables that would dramatically increase its viability would be a lookup field. A lookup field that references a related table to automatically populate values. Users can select a record from a related dataset, and the lookup field will fetch and display a specified field (e.g., name, ID, status) from that linked record. This enables dynamic relationships between tables, reduces data entry duplication, and ensures data consistency across documents. Currently, when you create a relation, it displays the text of the primary field, but it would be beneficial if you could choose any field from the related data table.

Currently, resolved comments are page-wide, but I would like to see an option in the record view of a data table to view resolved comments specific to that record. Can someone from the Zoom team chime in and let me know if this feature is in the works or I'd be happy to discuss if additional information is needed. Zoom Docs has the potential to be one of Zoom's best products imo and I see that new features are quickly being implemented which I appreciate.

Whenever I group by date, whether its year or by month it is ALWAYS one behind.

So if the date is 9/15/2024 and I have it grouped by month, the date above it will show "August 2024," and if i have it grouped by year, the date above will show "2023."