digibandit
Broadly speaking, a bug is an unintended software error whereas a feature is a suggested/planned improvement. This post was marked by the original poster as a bug. The misunderstanding about only technical contacts being able to edit contacts aside, I would agree the issue about technical contacts being able to lock themselves out is indeed a bug. This has now been fixed in develop and will be included in the next release.
It was then suggested: This should be a separate checkbox imo; "Contact Manager". Further, I want a customer portal option that you can see (assets, contacts, etc), but not touch (edit, modify, etc) does one exist? We don't have a contact manager role or any sort of read-only, so you were suggesting a new feature.
There is a lot of this, any ideas on how to avoid this becoming a growing problem as you and your platform grows?
The forum can get quite busy at times and discussions can get buried. We are usually fairly on top of bugs and support requests, but features can be open for many months or years. I do try and go through old threads when I have time. I would say the majority of people don't use the search and then start threads requesting the same features, which then get merged in, so they do get collated eventually. Alternatively, if people do use the search, they can drop a like or comment on the thread to show their support. Once we've committed to a feature, we'll usually tag the thread appropriately and add it into TaskFlow.
This brings me back to this thread. How likely is it that someone interested in a new feature relating to better permission options for client contacts would see this thread titled "Bug On client portal Technical > Contacts" and think it would contain the suggestion they wish to make? I think that's fairly unlikely?
The scope of this discussion is a bug in relation to contact permissions, I believe that a question about contact permissions is warranted but I'm deferring to you, so what is your call, would you like me to create a separate request?
As I said, discussions and questions are very welcome. I engaged with your discussion, gave an overview of the current available options and then said: feel free to raise a separate thread suggesting this as an enhancement. I then found the thread that had been raised and tagged you in it.
You will see I have given the same advice to other community members when they raise threads with multiple feature requests. Separate threads for separate things will help keep track of what is outstanding, what is done, and what won't be implemented.
So in answer to your question, yes, please raise a separate feature request for this (or simply add a comment onto the feature thread already raised).