Applications
Create, manage, and scope what Canary tests.
An application is the product you test in Cofactor. It holds the environments you run against, the credentials and personas your flows log in with, and the context Cofactor builds up about how it works. Issues and runs are attributed to an application, so most work starts by selecting one.
01Create an application
Creating an application sets up its first environment in the same step.
- Enter the primary domain.
- Give it a clear name — issues and runs are attributed by it.
- Add the default environment: pick a preset name like
productionorstaging(or a custom one), and enter its URL. You can enter a bare hostname; Cofactor adds the protocol and validates the URL.
02Environments
Manage every environment from the Environments tab — long-lived (production, staging), local, VPC-backed, and sandbox-backed ephemeral environments all appear in one list with type, VPC status, last update, and expiry.
- Set a default environment so new runs and flows start where you work most.
- Set a default sandbox so one-click ad-hoc tests (including from Slack) launch against a preferred sandbox; you can still pick another at run time.
- Ephemeral environments appear automatically while a sandbox is running and disappear when it expires. Check the expiry on those rows before you run or share the URL.
- A flow runs only in environments it's eligible for. If a run is skipped, compare the selected environment against the flow's environment constraints, then adjust and rerun.
03Credentials, personas, and context
From the application you also manage how Cofactor signs in and what it knows:
- Credentials — the actual per-environment logins, scoped to the application.
- Personas — a shared identity (e.g.
Admin user) mapped to the right credential in each environment, so one flow runs everywhere. - Skill — structured knowledge about the app, edited and reviewed on its own tab.
Keep credentials aligned with your environments so flows sign in consistently across every environment type.