Pod visibility policy
Controls whether members can create Open Pods or are limited to Restricted (private) ones.Useful for large organizations where members might inadvertently make a Pod visible to everyone without realizing the scope. Setting this to “Private Pods only” ensures that sharing is always intentional.Note: existing Open Pods are not force-closed when this policy is enabled. Editors can still switch them back to Restricted manually.
Pod files policy
Controls whether members can manually add files or linked data to a Pod’s Files tab.Useful for organizations with tight data governance rules, where knowledge in Pods should come exclusively from controlled, automated sources rather than ad-hoc member uploads.
Access a Restricted Pod as admin
When a workspace admin opens a Restricted Pod they’re not a member of, Dust shows a blocked page that hides the Pod’s name and content. To open the Pod, click Access as admin on that page. You join the Pod as a Member, not an Editor. On plans with audit logs, the join is recorded as aproject.admin_access_granted event.
Only workspace admins see the Access as admin button.