×
This forum has been locked. Please submit new Feature Requests on GitHub: github.com/Jensen-Technologies/component-creator-issues/issues
Access control for Component Creator itself.
Erik van Doorne
Fresh Boarder
Posts: 9
9 Jahre 11 Monate her #518
von Erik van Doorne
Access control for Component Creator itself. wurde erstellt von Erik van Doorne
Hello,
As I have a small company I have 2 colleagues and a couple of external freelancers whom I am sharing access to Component Creator with. I would l ike ot have the option to exclude projects from certain users. So a subscription to CC would then need multiple login accounts with different options for access per account. That way I can 'hide' projects from freelancers andor colleagues who should not have access to them.
Regards from
Erik van Doorne
As I have a small company I have 2 colleagues and a couple of external freelancers whom I am sharing access to Component Creator with. I would l ike ot have the option to exclude projects from certain users. So a subscription to CC would then need multiple login accounts with different options for access per account. That way I can 'hide' projects from freelancers andor colleagues who should not have access to them.
Regards from
Erik van Doorne
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
Søren Beck Jensen
Administrator
Posts: 81
9 Jahre 11 Monate her #526
von Søren Beck Jensen
Søren Beck Jensen
Founder, Component-Creator.com
Søren Beck Jensen antwortete auf Access control for Component Creator itself.
Hi Erik,
Thanks for the suggestion (and the other ones in your email that we still haven't had the time to properly consider).
I understand the need for this feature request, but from a business point of view it would be a poor solution for us.
We are already aware of some JDay groups who are considering (or might already be) buying a subscription together and sharing the access. With your added features it would make it a lot easier and almost guarantee this kind of group purchasing.
A solution would be to limit the number of active components a user can have, but we also feel this would be a poor choice.
Thanks for the suggestion (and the other ones in your email that we still haven't had the time to properly consider).
I understand the need for this feature request, but from a business point of view it would be a poor solution for us.
We are already aware of some JDay groups who are considering (or might already be) buying a subscription together and sharing the access. With your added features it would make it a lot easier and almost guarantee this kind of group purchasing.
A solution would be to limit the number of active components a user can have, but we also feel this would be a poor choice.
Søren Beck Jensen
Founder, Component-Creator.com
Bitte Anmelden oder Registrieren um der Konversation beizutreten.
Ladezeit der Seite: 0.049 Sekunden