Skip to main content
Support Documentation

Common Library Permissions

  • July 14, 2025
  • 0 replies
  • 284 views

There are times when permissions within Appspace impact different aspects of the platform, and understanding how, where, when, and why is important. In some instances, users may encounter a 403 Forbidden error when attempting to upload content, which prevents the content from successfully uploading. The only exception to this behavior is if the user specifically designates a private library during the upload process; in this particular case, the upload will succeed.

The root cause of this particular issue is when the user does not have access to write to the common library. When a piece of content is uploaded and a library is not specified, the upload will default to the common library, resulting in the error if the user does not have permissions. 

For more information on this options, see Add Users, Send User Invitations, & Manage Users/User Groups.

 

Step-by-Step Guide

 

  1. Log in to the Appspace console.
  2. Click Users from the ☰ Appspace menu.
  3. On the Users dashboard, click the All Users ellipsis, and select Configure Common Library.
  4. Users-Common-Library.png
  5. Select the Permissions for the library:
    • Admin only
    • Everyone can read & write
    • Everyone can read only
    • Custom access (assign permissions to specific user or user groups)

 


 

Example

  1. Have a location admin (or lower permissions) user enable the read-only permission for the common library.
  2. Navigate to a channel.
  3. Attempt to upload an image. 
  4. View the error.
  5. Attempt to upload an image to the specified library.
  6. View the successful upload and where the image file ends up in the libraries.
  7. Change the read-only configuration back to read-write, and everything should work successfully.

 

Note: The common library configuration needs to be configured by the account owner and cannot be adjusted by location admins.