Set permissions at Project Group level

[camlafit]

Hi

Could be nice to set permission also to project group level. Actually we can provide permission only to a project. When a team want managed some project, we need to set permission project by project.
At project group, teams could be manage/create/delete related project.

Thanks

[zepich]

Hi @camlafit

Thank you very much for your suggestion. Yes, that's a great idea!

We will add this functionality in a future version.

Kind regards,
zepich

[camlafit]

To complete, could be interesting to add some others ptions as domain root.
As this we can provided a shared hosting with a direct restriction to a group and their domain space. Maybe should be an another idea.

[zepich]

Hi @camlafit

Thank you very much for your feedback. I don't understand exactly what you mean. Do you mean an option to add the permissions based on the email domain?

For example: an user "test@example.com" will automatically has access to the mosparo project group "Example" because this domain is set in this group?

Kind regards,
zepich

[camlafit]

Hello

Sorry for the misunderstanding.
I've set a an instance with two domain and mosparo accept both domain without any complain from any project set and it's great.

My purpose is to restrict some sensitive information to a specific folder.
If we can manage them at group level, we could force a folder to a specific/list domain. Then we could prevent some information leaks.
We could also set some administration information as smtp part.

As exemple, I have a mosparo instance and two subdomain mosparo.domainA.tld and mosparo.domainB.tld to this instance.
When a project is set, we can targe both mosparo domain.
For exemple In group level we could restrict folderA ans its subprojects to only mosparo.domainA.tld

I hope to have to precise my ·thought :)

[zepich]

Hi @camlafit

Thank you very much for your clarification. I summarize it in my words:

Let's say we have a user A who can log in to mosparo.domainA.tld and view the projects for domainA, and a user B who can log in to mosparo.domainB.tld and view the projects for domainB. User A should not know that there is a user B (and domainB.tld), and user B should not know that there is a user A (and domainA.tld). Right? Or did I miss anything?

But... with just the restrictions at the group level based on the domain, user A would be able to log in to mosparo.domainB.tld, since the restrictions are based on the domain, meaning user A has full access to everything in domainB.tld if user A uses domainB.tld to log in. Or do I miss something?

But my main question is: What is your endgoal with that? When I read your message some hours ago, I read it pretty fast and understood first that your goal is to have one mosparo installation, but in a way that user A and user B do not know that there is a different user (or project). Comparable with a WordPress Multisite installation, where you have one WordPress installation but multiple websites.

If that's your main goal, then I think we can solve that with a different approach and without project group access levels.

Kind regards,
zepich