hcengineering / hcengineering/platform

Guest cannot upload files to Drive despite having CreateFile permission

Open
#11,028 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
27.7k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Description

Hi Huly team,

I am using **Huly v0.7.426** and I have found what appears to be a permissions issue with Guest users and Drive.

### Current setup

I created a custom role for a **Drive space type** and assigned the following permissions, including:

* `CreateFile`
* read/access permissions required for the Drive

I then assigned this custom role to a **Guest user**.

However, the Guest user still cannot upload a file to the Drive using **“+ Upload File”**.

### Important comparison

I tested the exact same Drive and permissions with an Employee user:

* Employee + the same Drive role → **upload works**
* Guest + the same Drive role → **upload does not work**

Therefore, it does not appear to be a missing `CreateFile` permission in the Drive role. The difference seems to be the user's Guest status.

### Expected behavior

If a Guest has a Drive role containing `CreateFile`, I would expect the Guest to be able to create/upload files in that Drive, without giving the Guest Employee-level access to the rest of the workspace.

For example, I would like to achieve:

Guest / Client

* Access to one specific Drive → yes
* Read files → yes
* Upload files → yes
* Access to other workspace modules/spaces → no
* Employee-level permissions → no

Is there an additional Guest permission or security check that prevents `CreateFile` from working for Guest users?

If so, where is this permission configured?

If this is currently not supported, is this a known limitation or bug?

### Related functionality

I noticed that Huly already has configurable Guest permissions and Drive permissions, and that Guest Spaces were added in v0.7.423.

I would also like to ask whether there are plans for a more granular **Client/Customer role** where an administrator could define exactly which Spaces/modules a client can access and what they can do there.

For example:

**Client role**

* Drive A → read + upload
* Documents → read only
* CRM → access only to assigned records
* Tracker → no access
* HR → no access
* Chat → optional
* Other Spaces → no access

This would allow Huly to be used properly for external clients without giving them Employee access.

Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue in Huly v0.7.426 with the same Drive role for a Guest and an Employee, using “+ Upload File.” Trace the permission checks involved in Drive file creation and compare the Guest and Employee paths. Done means a Guest with CreateFile can upload without broader workspace access, or the limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.