What is the recommended approach for managing permissions across multiple related objects?

• A. Place related objects into separate projects
• B. Use a global permissions group across all projects
• C. Place related objects and their writeback datasets in the same project
• D. Manage writebacks independently per object

Answer: (C)

Keeping related objects and their writeback datasets in the same project centralizes access control and ensures consistent permissions across all related assets. In Foundry, a project defines the scope of who can see and modify data, so placing both the objects and their writebacks together means a single set of roles or groups can govern access to everything involved. This avoids mismatches where someone could view an object but not the writeback, or conversely, be allowed to write back without appropriate read access. It also reduces the overhead of duplicating permission configurations across multiple projects.

Splitting them into separate projects would force cross-project permission management, leading to more complexity and potential gaps. A global permission group across all projects bypasses project-level governance and increases risk. Managing writebacks independently per object creates inconsistency and extra maintenance work.