1. Decide what should be shared
Tool configs, credentials, state backends, VCS integrations, and notifications usually belong at organization or project scope.
2. Create the project intentionally
Use projects to reflect environment boundaries, team ownership, or domain boundaries.
3. Create or reuse shared configuration
Define reusable tool configs, credentials, state backends, and VCS integrations before wiring the workspace.
4. Create the workspace with intent
Choose the exact source repo URL, branch, and source root that Forgecroft should execute.
5. Choose execution mode deliberately
Use managed for quickest setup. Use agent when execution must stay inside your environment.
6. Validate credentials and backend
If the first plan fails, inspect credentials, backend bucket or path settings, endpoint, region, and attached configs.
7. Run the first plan
A successful plan is proof that source, execution mode, credentials, backend, and tool configuration are all aligned.