Skip to main content
Multiple users collaborating on the same project might not all have the same level of access to External Data Volumes (EDVs). EDVs added to the project must not be accessible to users without volume access, and under no circumstance will a user without volume access to an EDV be able to mount that EDV in a supported execution. However, you can manage the visibility of the EDV in the application. To do this, use the levels of censorship to choose between security and discoverability needs.
  • Full censorship. Only the existence of any inaccessible EDV is made known to the user; the quantity and any metadata (such as name or description) is not made known to the user. This is the level for those that want the highest level of security.
  • Inactive censorship. Inaccessible EDVs are made known to the user; the EDV metadata (such as name and description) is made known to the user. This is the level that promotes discoverability. With discoverability, users can escalate to you to gain volume access. This is the default level of censorship. See Mount an External Volume to see what your users see.
To set the level of censorship, use the ShortLived.ExternalDataVolumesFullCensor feature flag.