Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shared folder functionalities #1181

Open
Samvdg opened this issue Jan 18, 2023 · 0 comments
Open

Shared folder functionalities #1181

Samvdg opened this issue Jan 18, 2023 · 0 comments

Comments

@Samvdg
Copy link

Samvdg commented Jan 18, 2023

Is your feature request related to a problem? Please describe.

I am sad there is so little customization to shared folder functionality you can really do.

I am trying to make dynamic shared folders per customers company_id. This way users have their own (in my case per project) private folder and their own organisation

I tried to change this but i am not logged in before this gets loaded

(i tried looking through the issue list to see if someone has requested the same kind of question but couldn't find it. I am probably just unaware of a certain functionality (i am a junior))

I have scowered the Laravel wiki and a bit of googling for a couple of hours now and still can't really understand why the shared folder config gets loaded without authentication while the private folder does. Could you possibly tell me where i could find a proper explanation of the order of loading authentication, middleware and config in laravel? The wiki didn't really help me understand the order.

After looking a bit more i am pretty sure it has to do with the multiuser middleware

Describe the solution you'd like

Having more cuztomization options for the shared folder (1 function like the userField function is fine as long as i can reach the logged in user.

Sorry if this is an easy question or if i missed something

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant