Answers.Body: <p>Have you checked the <a href="http://buildwithcraft.com/docs/users#user-groups" rel="nofollow noreferrer">user group permission settings page</a>? There you should be able to select which Asset Sources users in a specific user group are able to view, upload files to, etc. If at least one Asset Source is selected then the Assets navigation item will appear for users in that group, otherwise it will be hidden.</p>
  
  <p><img src="https://i.sstatic.net/r7BP2.png" alt="Asset Source permissions"></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:21:52.663Z
Answers.Text: That's the problem; I do not want to have users allowed to access all *other users* asset resources - which this does. I want them to be able to upload files, but not view these sources. That's not an applicable option from what I can tell.
Answers.UserDisplayName: Matt Wilcox
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:23:14.257Z
Answers.Text: I.e., I want each user silo'd into their own folders. I do not want them able to see other resources belonging to anyone else. This works with how it's set up with the exeption that they can't upload assets *except* in a Matrix field.
Answers.UserDisplayName: Matt Wilcox
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:25:59.237Z
Answers.Text: @MattWilcox how does this work in a Matrix field? Does the modal show the asset source panel on the left? Or is there a special *upload only modal*, that doesn't show anything besides the red upload button?
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:28:09.467Z
Answers.Text: That's where I think the problem lies, it's the proper UI for the function you're requesting, that is still missing. I think all you can do is to make a feature request for it.
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:30:39.547Z
Answers.Text: if you check the "Restrict uploads to a single folder?" field and then set the "path to subfolder" to {author.username} then you should be able to restrict folders to the the entry's author. or {currentUser.username} may be better depending on what you're trying to achieve.
Answers.UserDisplayName: Ben Croker
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T15:01:58.583Z
Answers.Text: @BenCroker - that is how it is set up already. I can't upload files as a member of Users, unless I give Users the 'View Source' privilege; which then adds the Assets tab and they can view everything. Not what I want. :(
Answers.UserDisplayName: Matt Wilcox
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T15:34:21.493Z
Answers.Text: Here's my experience as a mini screencast, logged in as a restricted user type (no assets privileges):
  http://viewcreative.co.uk/DELETEME/uploading.gif
  
  And here's the filetype set up and permissions:
  http://viewcreative.co.uk/DELETEME/permissions.gif
Answers.UserDisplayName: Matt Wilcox
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T17:45:53.870Z
Answers.Text: ok i see. probably best to report this as a possible bug (or inconsistency) to P&T.
Answers.UserDisplayName: Ben Croker
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-12-03T14:19:18.807Z
Answers.LastActivityDate: 2014-12-03T14:19:18.807Z
Answers.UserDisplayName: Ben Croker
Body: <p>I've two user groups; admin and user. The User group does not have access to the Assets tab, which stops them from just browsing all the assets that anyone might have uploaded - which is what I want; no random looking about in the Assets resources.</p>
  
  <p>I've a field type 'Featured Image' that is an asset; and it is restricted to a single upload folder, file type image, with an upload location set to {slug} - this means it will upload files into a folder named the same as the slug for the entry in which it's being used.</p>
  
  <p>It works fine for admins who have privileges to see Assets. I can not upload anything in this field with a user of type User.</p>
  
  <p>This behaviour makes Asset fields essentially useless unless the user group also has privileges to view (and upload/edit) all assets site-wide. Because 'upload' is a child privilege of 'view assets' I can't give the upload rights without also giving them 'browse all the assets everywhere' rights.</p>
  
  <p>I'd like these restricted users to be able to upload in that field.</p>
  
  <p>Oddly, I have a Matrix field called Gallery which has an asset field inside it, set to file type image, single upload directory; {owner.slug}/gallery/</p>
  
  <p>That asset field works fine for these users, and they are able to upload into it.</p>
  
  <p>Anyone have any ideas?</p>
  
  <p>I'd hoped this would be fixed in 2.3, alas it seems not, unless there's something I need to change?</p>
  
  <p>Here's my experience as a mini screencast, logged in as a restricted user type (no assets privileges): <a href="http://viewcreative.co.uk/DELETEME/uploading.gif" rel="nofollow">http://viewcreative.co.uk/DELETEME/uploading.gif</a> And here's the filetype set up and permissions: <a href="http://viewcreative.co.uk/DELETEME/permissions.gif" rel="nofollow">http://viewcreative.co.uk/DELETEME/permissions.gif</a></p>
  
Tags: <assets><users>
Title: Why can't users upload files in this asset?
ThreadText: # Why can't users upload files in this asset?
  
  (Asked by: username_0 on 2014-12-03)
  
  I've two user groups; admin and user. The User group does not have access to the Assets tab, which stops them from just browsing all the assets that anyone might have uploaded - which is what I want; no random looking about in the Assets resources.
  
  I've a field type 'Featured Image' that is an asset; and it is restricted to a single upload folder, file type image, with an upload location set to {slug} - this means it will upload files into a folder named the same as the slug for the entry in which it's being used.
  
  It works fine for admins who have privileges to see Assets. I can not upload anything in this field with a user of type User.
  
  This behaviour makes Asset fields essentially useless unless the user group also has privileges to view (and upload/edit) all assets site-wide. Because 'upload' is a child privilege of 'view assets' I can't give the upload rights without also giving them 'browse all the assets everywhere' rights.
  
  I'd like these restricted users to be able to upload in that field.
  
  Oddly, I have a Matrix field called Gallery which has an asset field inside it, set to file type image, single upload directory; {owner.slug}/gallery/
  
  That asset field works fine for these users, and they are able to upload into it.
  
  Anyone have any ideas?
  
  I'd hoped this would be fixed in 2.3, alas it seems not, unless there's something I need to change?
  
  Here's my experience as a mini screencast, logged in as a restricted user type (no assets privileges): <http://viewcreative.co.uk/DELETEME/uploading.gif> And here's the filetype set up and permissions: <http://viewcreative.co.uk/DELETEME/permissions.gif>
  
  **Tags:** assets, users
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-12-03. Score: 2
  
  Have you checked the [user group permission settings page](http://buildwithcraft.com/docs/users#user-groups)? There you should be able to select which Asset Sources users in a specific user group are able to view, upload files to, etc. If at least one Asset Source is selected then the Assets navigation item will appear for users in that group, otherwise it will be hidden.
  
  ![Asset Source permissions](https://i.sstatic.net/r7BP2.png)
  
  > **Comments:**
  > **username_0**: That's the problem; I do not want to have users allowed to access all *other users* asset resources - which this does. I want them to be able to upload files, but not view these sources. That's not an applicable option from what I can tell.  
  > **username_0**: I.e., I want each user silo'd into their own folders. I do not want them able to see other resources belonging to anyone else. This works with how it's set up with the exeption that they can't upload assets *except* in a Matrix field.  
  > **username_2**: @username_0 how does this work in a Matrix field? Does the modal show the asset source panel on the left? Or is there a special *upload only modal*, that doesn't show anything besides the red upload button?  
  > **username_2**: That's where I think the problem lies, it's the proper UI for the function you're requesting, that is still missing. I think all you can do is to make a feature request for it.  
  > **username_1**: if you check the "Restrict uploads to a single folder?" field and then set the "path to subfolder" to {author.username} then you should be able to restrict folders to the the entry's author. or {currentUser.username} may be better depending on what you're trying to achieve.  
  > **username_0**: @username_1 - that is how it is set up already. I can't upload files as a member of Users, unless I give Users the 'View Source' privilege; which then adds the Assets tab and they can view everything. Not what I want. :(  
  > **username_0**: Here's my experience as a mini screencast, logged in as a restricted user type (no assets privileges): http://viewcreative.co.uk/DELETEME/uploading.gif  And here's the filetype set up and permissions: http://viewcreative.co.uk/DELETEME/permissions.gif  
  > **username_1**: ok i see. probably best to report this as a possible bug (or inconsistency) to P&T.  
  
  ---
  
  