# Configuring persistence

### **CoherenceSync configuration**

The CoherenceSync editor interface allows us to define the Lifetime of a networked object. The following options are available:

* **Session Based.** No persistence. The entity will disappear when the client or simulator disconnects.
* **Persistent.** The entity will remain on the server until a simulating client deletes it.

![CoherenceSync inspector](/files/xwYD3JnQvvwbRdYEYNYm)

### **Persistence UUID**

Persistent objects need to be identified so that the system can know how to treat duplicate persistent objects. 

Manually assigning a UUID means that each instance of this persistent object prefab is considered **the same object** regardless of where on the network it is instantiated.  So, for example, if two clients instantiate the same prefab object with the same persistence UUID then only one is considered official and the other is replaced by the replication server.

### **Deleting a persistent object**

A persistent object can be deleted only by the client or simulator that has authority over it. For indirect remote deletion, see the section about [network commands](/0.5.2/authority/commands.md).

Deleting a persistent object is done the same as with any network object - by destroying its GameObject.

```csharp
Destroy(coherenceSync.gameObject);
```


---

# 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://docs.coherence.io/0.5.2/persistence/configuring-persistence.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.