Thanks for taking the time to provide this great feedback.  I always appreciate it when a client fully explores the system, then circles back and lets us know what they think we can do to make it even better.  That’s how things happen.  Be certain I’ve carefully read you comments and made my own notes.  Our challenge of course is to balance the needs of a diverse community while keeping the application approachable and easy to use.  There is (normally) a method to our madness.

Touching on a couple of your points:

“It would be nice to be able to have a start date, an end date, and a due date”.  You can see a derived start date in the timeline view by adding a duration to the task e.g. “due date” less “duration” is “when the task must start”.  Why was it done like this?  While adding those additional fields might seem helpful in planning, perhaps even critical at the time, we’ve found when it comes time to getting the work done they create unnecessary noise making the system more complex and less useful.  On an ongoing basis the current method is generally better at managing expectations with your team, managing the day-to-day workload and getting tasks completed efficiently.

“Published project blogs should be able to have password protection.“  All published blogs are secure and in effect have a pseudo password; we’ve just been a bit clever in how security is implemented to eliminate any training / management of logins for guests.  This is accomplished by using two factors: an obfuscated (un-guessable) web address in combination with the guest’s email address.

I finally decided to go with solve360 and I think that it is going to work well, but I am still interested in knowing if there are going to be more options than “read only” “modify” and “Add Comments”. 

I do graphic design and video work and it would be really helpful if I could have my clients add files to the project blog such as logos etc, but I really don’t want them to be able to delete things.

Is this something I can look forward to?

Welcome

A couple of quick points.  If a client deleted something you can undelete it under Workspace > Deleted Items.  You can also prevent clients from seeing any activity (making it impossible to delete) by editing the activity and checking the “Hide from Publish and RSS views” option.

We have plans to limit access based on workgroup > activity type but I don’t have information about if or how this will relate to published blogs.  I will pass your comment along to the team for consideration however.

I would like to second the security.. I would like to see more granular security capabilities. In a perfect world right down to the Field-on-the-Form.

I would not only like to be able to restrict customers but also internal users. We have to share the blog with the group and that gives every group member the ability to view and exit all the items in the blog. 

I would like see the ability limit the activities in a blog based on group roles.  I do not want all of my people to have the same ability in the blog.  I have different levels of users, and each needs to have different levels of Insert, View, Modify and Delete) As well as external users or customers in my case.