Current Behavior
People see:
Expected Behavior
The should see this!
Which is very very essential for usage of the platfrom. Why cannot they do so?
Checking internally, will get back to you.
Is this something that worked before, or is this more of a feature request? Because it is by design that only admins can create internal projects and add apps to it. Project owners are allowed to add apps to private projects (and depending on your organization settings, everyone is allowed to create private projects).
In our case we create internal projects of real projects.
This way everybody can open/see Internal (public) projects and use them.
It is true that by design only admins can create internal apps.
However it should be possible to add apps to projects (internal projects) by users. Otherwise there is a lot of overhead/administration for admins.
So we would really really really want an options that user may add apps to projects.
Otherwise the entire system will not be usefull.
It would mean:
- A new project (business project) starts
- Users check if project is present
- It is not, so they create one (private)
- Another user also is on the same project, but doesn’t see it.
- It creates his/her own project
- Data is split acros projects.
- No collaboration is present.
So instead we use internal projects but now:
- A new project starts
- Nobody can create an internal projects, so admins need to do it.
- We create a project
- User see the project and opens it
- There are no apps, or the correct app isn’t there
- No idea what to do, so they create their own or skip viktor or they notice us.
- We add apps to the project, but only those that are usefull
- In other words, complete chaos….
What we want:
- Optionally allow users to create internal projects
- Optionally but required, users are allowed to add apps to their project (internal or private)
If it isn’t possible, I am afraid that we will loose a lot of users that aren’t that pro-active in finding the admins.
Hi @Johan_Tuls,
This is very interesting, and opens up a few more questions from me. Reading your reply it seems that right now you are also choosing to use internal projects for 2 reasons:
- Users currently cannot see private projects they are not already a part of
- There is lots of overhead on environment admins to manage users on private projects and internal projects.
My question is: would this potentially also be solved for you if:
- All users could always see all projects, even the ones they are not already in?
- Users could see projects they are not already in, but they cannot enter/use it. They can see who owns the project and request access
- If you are the owner of a private project, and someone wants to join then you get that request (not the environment admin)?
Also tagging @tvantil in this conversation because this is good input for her work around this topic.
Could be, there is always a trade-off between accesability and robustness.
So in the case of private project with visiblity the accesability is better, but still not optimal as it requires a request acces. So you have to wait untill you can start.
However private apps, do provide certain safety on who can edit/join.
So yes it would help, however in our case:
If in this screen a checkbox was added,:
- Users may add apps to internal projects
Would be enough to solve the problem.