User Permissions

it's both, isn't it?

First, you have to allow multiple users to login. Once you have set up that schema, you can then attach module access.

In #35, you say 'it will not be of much use' - you are possible wrong, but only if you start with full access! If you can track who logged in when and what they did, 'simple' multi user access is a leap forward in usability!

I am not sure where your client base is, at the moment, but if it is still a lot of micro businesses (2-3 man bands), I believe that they all probably access it to do multiple things. At present, they will use one login - in one of my businesses, there are 3 of us who add sales, clients supplier invoices etc. Just being able to track who does what (should it be required) would be a fantastic feature and is what true multi-user is about.

Once you have that sorted, then dig down with specific module permissions.

I am not teaching you to suck eggs, but, to me, that seems the more logical way to proceed, rather than diving into just using quotes.

Hi

I think the comment above is very interesting and would perhaps be a short term solution to the problem.

I had always pictured the idea of restricting certain users to certain aspects of the software, i.e. general assistants can add new customers and create new invoices, but can't access the supplier invoices for example - which is still the ideal scenario, although technical more tricky to release I would imagine.

However, if you could allow a second user to login (albeit with full access to the software) but all of there actions be logged so as the master user could view what they have been doing, then this would be a great intermediate step.

It would just mean that actions would become the responsibility of the individual users rather than everyone logging in with the same username and no way of knowing which member of staff has done what.

Like I say, the ideal solution would still be different permissions for different users, but the idea above would be a massive leap forward for Kashflow as an accounts tool in my opinion.

Thanks

Duane,

fully understood.

My thoughts were to do multi user access first (as this has had a few requests) THEN user permissions, as two separate actions/projects. However, from a development view, if it is better to combine MUA & UP (limited) from go, that's the way it is!

Hi Duane
Has there been any more progress on the multi user access?
Thanks

Hi All,
It seems like the KF team have this pretty much in hand, so I'll keep my implementation and priority opinions to myself at this late stage, but I'd simply like to register my desire for this suite of functionality.
Echoing a few points:
We are a small, multi-role team where several staff are required to edit and view data. Whilst (at this stage) we have little requirement for perms, audit is considered essential. Our workaround is to use the notes, but it's not elegant.
We certainly see the need for perms as we migrate more functionality in KF, ideally with some authorised workflow checkpoints, review/sign-off, approvals.

It strikes me though that MU & UP needs to go hand in hand with revision history. How else does one correct errors whilst maintaining traceability? Of course mistakes never happen out there, but they do in our world.

So Katie, I'm all peeled and watching this thread, eagerly
Keep up the great work, and great forum community.
Cheers

Hello,

Sorry to drag up old threads but I was just wondering how far along the multi user/user permissions was coming along?

Many thanks