1. Permission overview from the UI #

In the app, you manage permissions through project sharing and user access settings.

• Admin and Editor are broad access roles that are typically set in the account management area.
• View only is a read-only role for users who should not make changes.
• Scoped access is used when you want to grant rights only for specific projects or collections.

2. Assigning access to a project #

Use the project Share dialog to give someone access to a single project.

• Open the project you want to share.
• Click the Share button or open access settings in the project header.
• Select the user and choose View only, Upload only, Edit, or No access.
• Save your changes to update the user’s access to that project.

3. Using scoped access correctly #

Scoped access is best when a user should only access a few projects or collections.

• Open user management as an administrator.
• Select the user and set their role to scoped if available.
• Pick the exact projects or collections they should see.
• Choose View, Upload, or Edit for each item.

4. What each access level means #

• View: the user can read project content but cannot upload or change anything.
• Upload: the user can add files and view project content.
• Edit: the user can change project contents and settings.

5. Managing collection access #

Collections let you share several projects at once.

• In user management, choose the collections the user should access.
• Assign the appropriate level for each collection.
• That level applies to all projects in the selected collection.

6. Handling storage access #

Storage access is often configured separately from project sharing.

• If a user needs to work directly with files, enable storage permissions in their profile.
• Read allows browsing and downloading files.
• Write allows uploading and changing files.
• Write access usually includes read access automatically.

7. Public and upload-only sharing #

Some projects support public sharing or upload-only access.

• Use public sharing when you want outside users to access the project without logging in.
• Select View only to let them see content only.
• Select Upload only to let them send files without seeing details.

8. Common permission workflows #

• Start with View only if you are unsure what someone needs.
• Use Upload only for users who should add documents but not edit settings.
• Use Edit for trusted users who need to update the project.

9. Troubleshooting permissions in the UI #

• If a user cannot open a project, check the project Share dialog first.
• If they can open but not upload, they are likely set to View only.
• If they should upload but cannot, verify their storage write permission.

10. Best practices #

• Prefer project- or collection-specific sharing instead of broad global roles.
• Give the minimum access needed for the task.
• Review permissions regularly, especially upload and edit rights.