> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/templates/with.md).

# with.bind (scope binding)

`with` is a **template controller** that creates a new binding scope for its content. It’s useful when you want to “zoom in” on an object so you don’t have to repeat a prefix like `user.` everywhere.

## Basic usage

```html
<template with.bind="user">
  <h2>${firstName} ${lastName}</h2>
  <p>${email}</p>
</template>
```

The inner template’s binding context becomes `user`, so `firstName` resolves as `user.firstName`, etc.

You can also put `with.bind` on a real element:

```html
<section with.bind="user">
  <h2>${firstName} ${lastName}</h2>
</section>
```

## “Shape” a small context object

Sometimes you don’t want to pass the whole object through — just a few values (or renamed values):

```html
<template with.bind="{ profile: user.profile, canEdit: permissions.admin }">
  <user-profile profile.bind="profile"></user-profile>
  <button disabled.bind="!canEdit">Edit</button>
</template>
```

## Updates and lifecycle

* `with` does **not** add/remove DOM like `if` or `repeat`.
* When the `with` value changes, Aurelia **re-binds** the existing view to the new scope (it does not recreate the view).

## Gotchas

* `with` expects an **object**. If your value can be `null`/`undefined`, guard it:

  ```html
  <template with.bind="user || {}">
    ${firstName}
  </template>
  ```
* Prefer `<let>` when you only need a couple of local aliases and don’t need to re-scope a whole block.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aurelia.io/templates/with.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.