<p>Assets aren't technically multi-site, in that it's currently not possible to limit Volumes to specific Sites, and all uploaded Assets will be available across all Sites, regardless of which Site it was uploaded from.</p>

<p>Assets <em>titles</em> and custom fields can be translated, though. So the purpose of the Site selector in the Assets index is to have the titles and any custom field values render with a specific Site's translations.</p>

CC BY-SA 4.0
2019-08-13T15:15:20.357Z
Ah, then it makes sense. So to separate them per site I just create a Volume per site as well and I can restrict access via there. Thanks!
jishi
CC BY-SA 4.0
2019-08-13T09:26:35.633Z
2019-08-13T09:26:35.633Z
Mats Mikkel Rummelhoff
<p>I'm kind of confused about the site selector under Assets, because from what I can gather it actually doesn't do anything? See this screenshot, top left:</p>

<p><a href="https://i.sstatic.net/vAX04.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/vAX04.png" alt="enter image description here"></a></p>

<p>I was first under the impression that I would only see assets that have been uploaded for a specific site, but that doesn't seem to be the case. Every user seem to see all content for a volume, meaning I would have to create a volume per site in order to separate them? </p>

<assets><sites>
What purpose does the site-selector under assets fulfill?
# What purpose does the site-selector under assets fulfill?

(Asked by: username_0 on 2019-08-13)

I'm kind of confused about the site selector under Assets, because from what I can gather it actually doesn't do anything? See this screenshot, top left:

[![enter image description here](https://i.sstatic.net/vAX04.png)](https://i.sstatic.net/vAX04.png)

I was first under the impression that I would only see assets that have been uploaded for a specific site, but that doesn't seem to be the case. Every user seem to see all content for a volume, meaning I would have to create a volume per site in order to separate them?

**Tags:** assets, sites


---

## 1 answers

### Answer by username_1 on 2019-08-13. Score: 3 | Accepted answer

Assets aren't technically multi-site, in that it's currently not possible to limit Volumes to specific Sites, and all uploaded Assets will be available across all Sites, regardless of which Site it was uploaded from.

Assets *titles* and custom fields can be translated, though. So the purpose of the Site selector in the Assets index is to have the titles and any custom field values render with a specific Site's translations.

> **Comments:**
> **username_0**: Ah, then it makes sense. So to separate them per site I just create a Volume per site as well and I can restrict access via there. Thanks!  

---

