> ## Documentation Index
> Fetch the complete documentation index at: https://docs.occtoo.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Edit a subscription
> Change the name, delivery target or event filter of an existing subscription.
On the subscription page, open the kebab menu and choose **Edit**.
The dialog is the creation form with the current values in it, minus the type step — the delivery type is fixed for the life of the subscription. To deliver the same events somewhere else in a different way, create a second subscription.
| Type | What you can change |
| ----------------------- | ----------------------------------------------------- |
| **Webhook** | Name, HTTPS endpoint, event filter |
| **Azure Storage Queue** | Name, connection string and queue name, event filter |
| **Azure Service Bus** | Name, connection string and entity name, event filter |
Editing the filter works exactly as it does at creation — see [Build the event filter](/guides/studio/events/event-filter).
## Azure credentials
The stored connection string is never returned, so its field opens blank. Leave it and the queue or entity name untouched and the stored configuration stays as it is.
Start replacing it and both fields become required together: a new connection string needs the queue or entity name that goes with it, and for Service Bus an `EntityPath=` in the connection string still has to match the entity name.
## What changes when you save
Click **Save changes**. **Cancel** discards everything, including changes to the filter.
Changing only the name or filter preserves the subscription's status and delivery starting point. The new filter is used when Occtoo next selects events for delivery. Events published before you save but still waiting to be processed can therefore match the new filter. Deliveries already selected keep their existing status and are not re-evaluated against it. Changing the filter does not replay events already processed.
Changing a webhook's endpoint cancels pending deliveries and returns it to **Pending verification**. [Verify the new endpoint](/guides/studio/events/verify-an-endpoint) to start delivery again. Events from before that verification point are not replayed.
Replacing Azure connection details cancels pending deliveries. For an active subscription, delivery starts again from the current event head. This also applies when you replace credentials for the same queue or entity, so credential replacement does not preserve the delivery backlog.
A request already in progress when you save may still complete.