What statement correctly describes locking permissions to a project?

Locking content permissions is a specific administrative action performed at the project level in Tableau Server. When permissions are locked, all workbooks, data sources, and other content published to that project will inherit their permissions directly from the project. This ensures a consistent security model across all assets within the project. The administrator or project leader achieves this by navigating to the project's permissions settings and changing the "Content Permissions" setting from its default state of "Customizable" to "Locked".

A. Locking permissions is a per-project setting and does not require a global enablement on the Tableau Server Settings page.

C. The default setting for content permissions in a newly created project is "Customizable" (unlocked), not "Locked," to allow for granular control by content owners.

D. Locking permissions is a distinct project-level setting that governs inheritance. It is not a permission role (like Viewer or Publisher) that is assigned to a user or group.

1. Tableau Server Help, "Lock Content Permissions": This document explicitly states, "In the project's Permissions dialog box... In the Content Permissions in Project dialog, select Locked (recommended) or Customizable, and then click Save." This directly validates that the action involves changing the setting to "Locked".

2. Tableau Server Help, "Use Projects to Manage Content Access": This guide clarifies the default behavior: "When you create a new top-level project, permissions are customizable ('unlocked')." This directly refutes option C. It also describes the two models (locked vs. customizable), confirming that locking is a setting, not a role (refuting D) or a server-wide configuration (refuting A).