Your input needed: adding access rights
One major gripe with the Mobile Web Server user management is adding the access rights for different applications. You know, going through all of the applications (such as Blog or Presence) and adding the rights one by one. In an upcoming release we will finally address this, and you can help us getting it right.
The current idea is roughly this:
- there will be a single ‘Add access rights’ page under Settings that includes all of the applications and their features
- within that page you can choose Users or Groups, and add rights to some or all applications (or clear all rights to start from fresh)
- there will be another page where you can check the current access rights for any given User or Group
The challenge with these new settings is that the amount of data requests must be kept to a minimum for speed and efficiency reasons, hence the two different pages for adding and checking the rights.
How does that sound? Any further ideas? Thanks in advance!
-Jukka
Make it collapsible menus so that you see applications and then you can see more specific features within those appear.
Also if you can make it so that you can configure users and security rights through a computer’s browser instead of on the device, that would be awesome too.
Thanks Stefan, good comments.
Access rights are handled via browser already, just adding/deleting users need to be done on the device. I doubt we can change this at this time.
Combine both: user creation/adding on the device and a page/pages on the device to put rights of users and groups to an MWS application similiar to the upcoming rights page you plan
this would be a great advantage. So I can offline set the rights and need no browser!
Another idea was to break down the rights not only to the MWS application. What I mean is, that the rights can be break down to object level, for e.g. not the whole calender application I can set rights for user or goups, so I can set rights for users and groups on a calender entry itself. So the dedicated user or group can see the entry they should see and anything more.
I am with the previous poster in that user/group and application management should be both on the device and the website.
On the device, add within settings Application Permissions, and then checkboxes for public access. Then a screen if public access is chosen that it would ask if its general or a specific contact is needed.
In terms of the webpage itself; a general security tab where the same checkboxes are there for each page (public access or not) and then a dropdown-multiselect list for which users and groups can access it.
Hi Jukka,
Setting page for access rights is a good idea - but my concern is about the speed. Bulk setting of access rights could be used instead of selecting one at a time.
Having such an option on the client side (i.e on the device) could be flexible too. How about asking them on the first launch ?
Br,
Pankaj