How do I setup 'Temporary Training Artifacts' project with 'Editor' permissions for all users?

Ask the Community
, ,
1

Hi everyone,

I am planning to set up a new project named “Temporary Training Artifacts” to facilitate an upcoming hands-on training session.

To ensure a seamless experience for all participants, I need to configure the project so that all users (or the ‘Everyone’ group) have ‘Editor’ access by default. This will allow them to create, edit, and collaborate on data artifacts within this specific project.

I have a few questions regarding the best practices for this setup:

  1. Namespace & Permissions: What is the recommended way to grant ‘Editor’ roles to all users without compromising the security of other production namespaces?

  2. Automated Cleanup: Since these are “temporary” artifacts, are there any built-in Foundry features (or scripts) to automatically archive or delete this project after the training ends (e.g., in 30 days)?

  3. Resource Limits: Are there any concerns regarding resource consumption (Compute/Storage) if a large number of users start building datasets simultaneously in one project?

If there’s a standard template or a specific “Sandbox” area I should use instead of creating a new top-level project, please let me know.

Thanks in advance for your help!

2

Hey!

  1. The simplest and cleanest solution here is to create a new Project containing all the training resources, then set the Project’s default role to Editor (when viewing the Project, look for the lock icon near the top-right corner; you’ll see a section called Roles, click on the Manage button there then look to the bottom-right corner of the page where you can set the default role). Permissions on Foundry are granted on the project-level and propagate to all contents of a Project.
  2. There isn’t an out-of-the-box script or feature to archive or delete projects, but when you manually go to delete the project at some point in the future, you can just delete the Project from the root and it will move all of its contents to trash.
  3. To an extent, yes. Foundry instances by default typically have just one or two usage accounts (and corresponding resource queues). If there’s a lot of user activity on the platform during the training (from your trainees and from regular users), they will naturally compete for the same compute resources. If the amount of jobs/builds submitted around the same time require more resources than are available, jobs/builds will simply get queued until resources are released from earlier jobs/builds.
1 Like
3

Thanks josh!
You saved my days!