Customer login
There is no direct connection with customer right now in commercial spaces. It would
be very good if customer could enter space with special
'customer' (predefined by admin for ex.) login and get access to limited number of tools: dashboard, messages, wiki and tickets. Customer must have possibility to view project progress, edit wiki and leave comments.
Agile needs direct and everyday customer interaction!
anonymous
shared this idea
We had a three stage implementation plan. In the first stage, we implemented a “Watcher” role. You can assign customers to this role on the team page.
In the second stage, we implemented custom permissions for tools. You can set “None”, “Edit”, or “View” permissions for your customers/watchers in individual tools.
We just released the third stage, a Support tool, which provides a customer with a viiew of his or her own tickets. Customers can go to the Support tab and enter a ticket (a service request, or a bug report, etc.). This appears as a normal ticket in the team’s ticket tool. However, the customer can only see his or her own tickets in the Support tool.
10 comments
-
Adminasinglenet
(Admin, Assembla)
commented
We have released private Wiki and Messages. These can be hidden from "Watcher" users, just like in Basecamp. So, we have implemented all of the requests - permissions to show and hide specific tools, and private messages and wiki pages.
-
Adminasinglenet
(Admin, Assembla)
commented
We are working on a plan to have "private" tickets, wiki pages, and messages, as requested. This might take a little while because it makes the alert system more complicated, and we want to be sure it is reliable.
-
Adminasinglenet
(Admin, Assembla)
commented
In the Support tool, each customer can only see the tickets that he or she submitted. You can share the full view in the Tickets tool if you want.
-
blacksea
commented
Thanks for making progress on this. I didn't get a chance to try, but can multiple users be designated as "customers" and they all can see each others tickets?
-
Adminasinglenet
(Admin, Assembla)
commented
We added the Support tool so that users will have a view of their own tickets. Let me know if this is useful in your case
-
Adminasinglenet
(Admin, Assembla)
commented
I want to support this idea. I am resisting adding permissions to individual tickets or wiki pages, because I think that this will make the security hard to understand. How do you know who will see a particular wiki comment? You probably won't pay close attention. If you need public and private wiki pages, you can create two spaces. The public one is free.
-
blacksea
commented
cont'd
with Assembla as Dev. our customer facing people then manually move appropriate items from basecamp to Assembla. -
blacksea
commented
I had a chance to discuss with Assembla support the following idea and wanted to run it by community: we feel that customer portal should almost be a standalone app with Wiki/Tickets. Not everything that is being discussed with the customer ends up as Dev ticket and certainly not every Dev ticket should be seen by the customer, Right now we are using Basecamp as customer facing solution
-
hunterz
commented
I agree with blacksea's comment - especially in the wiki, the granularity of what a customer sees has to be different. As an intermediate solution it would just be nice to have the option of adding a separate globally accessible wiki.
-
blacksea
commented
need granular control over information that customer can see -- some tickets/wiki pages are appropriate for them to see and others are not
