documentation accessible from the user context menu. Ensure that hyperlinks

are valid and lead to up-to-date materials.

1. Encourage the use of `coder support bundle` to allow workspace users to

There are a variety of Coder-native features to extend the configuration of your development environments. Many of the following features are defined in your templates using the [Coder Terraform provider](https://registry.terraform.io/providers/coder/coder/latest/docs). The provider docs will provide code examples for usage; alternatively, you can view our [example templates](https://github.com/coder/coder/tree/main/examples/templates) to get started.

Once stopped, a workspace may resume running by starting it manually, or via

user connection if automatic start is enabled.

Similarly to stopping, workspaces may be deleted manually or automatically by

Unhealthy workspaces are usually caused by a misconfiguration in the agent or

workspace startup scripts.

- [Connecting to your workspace](../../user-guides/workspace-access/README.md)

Once you're finished, you can stop your workspace.

- Creating workspaces with the [CLI](../reference/cli/create.md)

- Creating workspaces with the [API](../reference/api/workspaces.md)

Dormancy automatically deletes workspaces which remain unused for long

durations. Template admins configure an inactivity period after which your

workspaces will gain a `dormant` badge. A separate period determines how long

Enterprise admins may also configure failure cleanup, which will automatically

delete workspaces that remain in a `failed` state for too long.