Great! I can always use some extra money. Or at least ways to makes them. I think these ways you present here Donald, prove that if we dig deep, we can find a lot of skills and resources we posses which we can use to make money. And some people think t…

#1 Kashflow does not have user permissions. This may be a reason for you not to buy the software – is so that's fine. Clearly lots of people don't care about this given Kashflow has customers.

#2 Kashflow are aware that this is a feature some people might want. They may add it in the future (as they agree there are reasons for having it) but it is not a priority now. There are features their users want more.

#3 Kashflow has a completly open API so another software company can create any sort of limiting aroud that API if they want. There seems to be a lot of misunderstanding about whan an API is and what it is for from Dennis.

#4 Even should Kashflow add user permissions to their system which I presume they will some day, assuming they keep a full API (which they would be crazy to change) then someone could still build a permission system on top of that API if they want that replaced whatever Kashflow had created.

#5 It seems that Dennis problem with the software has changed a lot from the FUD in the first post to it just being a matter of having to pay extra to someone else for a feature *he* belives should be included. Again, this is the exact eco-system I presume Duane is trying to create around Kashflow.

What a storm in a teapot!

Discloser: I am trying out Kashflow and considering being a customer – but not made my mind up yet.

However, my concern is, and always has been, that allowing a 3rd party to develop multi-level access as a very specific function, I am incurring an extra cost that should be part of the core offering from the main vendor (I don't know any other that has a separate charge for this) and in turn the main vendor is creating a problem for itself that exposes a level of risk I believe is unacceptable.

Sunir has written a very good comment in this which I have put out as a separate post.

Despite acknowledging the issue in our call, DJ chooses to argue about it rather than see that all but himself see this as an issue. That's a great shame because as I've said in a few places, this is easy to resolve. Buy the code.

I agree, David.

I would say that multi-level permissions are more valuable for a SaaS product even than for a desktop product – because of this.

The accessibility of the data in real time to users such as an accountant is one of the big pluses of SaaS.

So then the questions start cropping up as to which areas different users should be able to see.

Why would a business partner / a supplier need to see the bank reconciliation, which they probably wouldn't understand if it jumped up and bit them on the nose?

And sometimes it's useful to limit the areas an end user (business owner) can reach, such as journals.

So I would agree that multi-level user permissions are a big plus in the SaaS world.

If KashFlow are providing them, whether through the system itself or a third party, as an idea that's good news.

I'm not techie enough to know whether that service is secure having read this. I don't understand a lot of the terminology. But I have a high level of respect for Dennis's expertise and an amber light from him would probably, like Richard, send me running for the hills.

M