Skip to content

Managing Project Access

Project access is controlled per project. Access can be granted directly to a user or to a team.

Project permissions use three levels:

  • Read: view project content.
  • Write: contribute files and generation work.
  • Admin: manage project access and administrative project actions.

Open a project and use the team/access section to manage project permissions.

  1. Open the project detail page.
  2. Open project access controls.
  3. Add a user or team.
  4. Choose permission level.
  5. Save.
  1. Open project access controls.
  2. Locate the existing grant.
  3. Remove the grant.

If a team is granted access, current and future members of that team inherit that project access level.

Use these patterns to get more predictable results:

  • Keep inputs specific and scoped to one intent per generation request.
  • Save intermediate outputs often, especially before running major edits or regenerations.
  • Use review and assignment workflows early to reduce rework late in the lifecycle.

If results are not what you expected:

  • Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
  • Re-check selected options and audience/profile settings before re-running.
  • If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.

Different input context, settings, and model/runtime conditions can produce different outputs.

Regenerate when the core structure is wrong; manually edit when only wording, ordering, or style needs adjustment.

What is the best way to reduce iteration cycles?

Section titled “What is the best way to reduce iteration cycles?”

Start with clear scope, run smaller batches, and use review checkpoints after each major step.