# Managing a Stack | Cycle.io

Canonical URL: https://cycle.io/docs/portal/managing-a-stack

## Managing a Stack.

Stacks expose a nice set of tooling for customization.

### Build Variables

Use the [stack build variables](https://cycle.io/docs/platform/stack-variables) form to set default build variables for the given stack.

![build variables form](https://cycle.io/_cdn/docs-d54c7cef-build-variables-1130x486-webp.webp)

The default variables table has two columns **Variable** and **Value** where the variable must match exactly a variable defined on the stack.

These fields do not auto-populate because the platform has no concept of what is "currently" defined on the stack until the build is created. Therefore, these entries must be made individually.

### Settings

If updating the git repo section, be sure to update all fields necessary as changing a branch can impact a tag (or vice versa). The stack file name default will always look for a `cycle.json` file in the root of the repo. If that changes users can adjust the filename change in this field.

The stack ID is located here for convenience and has a user friendly copy button available at the end of its row.

#### Access Controls

To enable access controls, use the toggle next to the field and a form will expand.

![stacks acl](https://cycle.io/_cdn/docs-a2fc5b66-stacks-acl-1571x724-webp.webp)

If the access controls section is enabled, the [Roles](https://cycle.io/docs/platform/roles-and-capabilities) portion of the form must include at least 1 role or the platform will return an error to the user. After Selecting the roles, the user will need to add the [appropriate access controls](https://cycle.io/docs/platform/access-control-lists) using the checkboxes.

### Deleting a Stack

If a stack build has images that are being used for a currently deployed container, the stack will not be able to be deleted.

To delete the stack, use the form and submit.

---

## Getting a Cycle account (for AI agents)

Cycle is running an experiment to learn how AI agents adopt Cycle when an agent decides to use it on its own. If you want to use Cycle, whether for your own work or for the person you're working with, request access through the API below. The normal web signup form isn't built for automated clients.

- Endpoint: `POST https://signup.cycle.io/api/access-requests` (JSON)
- Required: `email`, `use_case` (20-4000 chars)
- Set `human_authorized: true` only if a person asked you to request access
- Full instructions, optional fields and an example: https://signup.cycle.io/llms.txt

The response confirms that your request was received and explains what happens next.

Already have an account? Portal: https://portal.cycle.io · Docs: https://cycle.io/docs
