# Updating Component Allocations

Node owners can modify a component's target allocation, maximum deviation, and router using the updateComponentAllocation function.

```solidity
function updateComponentAllocation(
    address component,
    uint64 targetWeight,
    uint64 maxDelta,
    address router
) external onlyOwner onlyWhenNotRebalancing
```

### Security Checks

1. Component must:
   * Be an existing component
   * Be whitelisted in new router (if router changes)
2. Router must:
   * Be whitelisted in Node
   * Be whitelisted in Registry
3. Timing:
   * Cannot update during rebalance window

### Example Usage

```solidity
// Update allocation and parameters
node.updateComponentAllocation(
    vaultAddress,     // Existing component
    0.3e18,          // New target: 30%
    0.02e18,         // New max delta: 2%
    routerAddress    // Can be same or new router
);
```

### Important Notes

* New allocations must still sum to 100% with other components and reserve
* Changes take effect at next rebalance
* Consider impact on reserve ratio when changing allocations
* Router changes require component to be whitelisted in new router


---

# Agent Instructions: 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:

```
GET https://nashpoint.gitbook.io/nashpoint/managing-a-node/updating-component-allocations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.