LogoLogo
codatum.comSign InStart for free
  • Introduction
  • Getting Started
    • Quick Start
    • Concept (Further reading)
      • Why did we a choose Block Editor over Cell-based Editor?
  • Connect and Manage Data
    • Connection
      • Sync Table Metadata
    • Supported Warehouses
      • BigQuery
      • Snowflake
      • Other Warehouses
    • Catalog
    • Search
  • Data Exploration
    • Data Exploration Overview
    • Notebook
      • Doc Page
      • Grid Page
      • SQL Block
      • Version
      • Notebook FAQ
    • Chart
    • Explorer
    • Parameter
    • (Appendix) Cache
  • AI Assist
    • SQL Assistant
  • Sharing
    • Sharing Overview
    • Teamspace
    • Shared Notebook
    • Report
    • Public Link
    • Signed Embed
      • How to Set Up Signed Embed
  • Account Management
    • Account
    • Account Settings
  • Workspace & User Management
    • Workspace
  • User Management
    • Invitation
    • Group
  • Security
    • Security Overview
  • Audit logs
  • IP Access Control
  • Access control
    • Access Control Overview
    • Access Control for Workspace
    • Access Control for Resources
      • Access Control for Group
      • Access Control for Teamspace
      • Access Control for Notebook
      • Access Control for Connection
      • Access Control for Report
  • [Under Construction] Plan and Billing
    • Limit and usage
    • Downgrade and cancel
  • Best Practices
    • Advanced Control Structures in SQL
  • Other considerations
    • System requirements
Powered by GitBook

Reference

  • Privacy policy
  • Terms of service
  • JP Docs Site
On this page
  • Roles for Reports
  • Report Operations and Access Control Rules

Was this helpful?

  1. Access control
  2. Access Control for Resources

Access Control for Report

Report roles, operations, access control rules.

Roles for Reports

Reports are read-only documents. The ability to execute queries is determined by the settings of the report, not by permissions. Therefore, only the Viewer role exists.

Role name
Summary

report.Viewer

Can view the report and refresh the query results if the report allows refresh execution.

Report Operations and Access Control Rules

Operations
Required Roles

View report contents.

Comment on reports.

report.Viewer

Operations related to publishing a Report are influenced by the access scope of the original Notebook from which the Report is created.

Operations
scope: Workspace
scope: Teamspace
scope: Private
scope: Shared

Publish reports.

workspace.Editor AND connection.User *

teamspace.Editor AND connection.User *

connection.User *

N/A

Delete reports.

workspace.Editor

teamspace.Editor

-

N/A

Edit report settings.

workspace.Editor

teamspace.Editor

-

N/A

Change permission settings of reports.

workspace.Editor AND connection.User *

teamspace.Editor AND connection.User *

connection.User *

N/A

*:connection.User role means that these operations need the respective role for all connections within the Notebook. This applies to protected and private access levels. For the workspace access level, no specific connection role is required.

PreviousAccess Control for ConnectionNextLimit and usage

Last updated 8 months ago

Was this helpful?