PDA

View Full Version : Logins, Users and Roles



yvonne.milne
2014-04-17, 06:53
When you install the Lianja App Builder, one user is already created - the 'admin' user, with the same password: 'admin'. You don't need to use these login details when you start the App Builder - you will be logged in automatically - but, you do need them to log into the Lianja App Center or when you log out of the App Builder Home Workspace and want to login again without exiting the App Builder.

For more information on Users and Roles, please see the video (http://videos.lianja.com/video/71411733) or documentation article (http://www.lianja.com/documentation/documentation-index/300-user-roles-and-permissions).

When you Deploy, remember that you need to Deploy the system database along with your App, Data and Library scripts, so that your user and role data is available in the runtime environment. See the 'Deploying Users' section (http://www.lianja.com/documentation/documentation-index/300-user-roles-and-permissions) for more details.

Yvonne

tekhong
2014-04-17, 08:40
Hi Yvonne

From the video, it seems to me that the end user needs to have the App Builder to setup permissions for the app, page, section, etc

If this is correct, this would be a serious limitation as the the roles would have to be predetermined by the developer when the app is built.

What if the end user needs a new role that wasn't designed into the app?

Please advise

Thanks & Best Regards

barrymavin
2014-04-17, 09:01
Hi Tek Hong,

Permissions are specified by you when you design your app.

When a user is setup you specify what role(s) they have and consequently what permissions they have -- this is done when they login.

That then governs the permissions on what apps users can open and what pages, sections and form items they can perform CRUD operations on.

If the end user wants to redesign the functionality of your App by adding their own permissions then that customization is done in the app builder as they are changing the fundamental nature of what you have designed.

You as a developer dictate the CRUD operations based on roles. Your customer assigns those roles to their users.

Users can be added by the customer using either the App Builder or through some custom UI that you build into your App. The users and their roles are just stored in the system!sysroles table and these can be browsed in a grid and updated.

Subsequently if the user wants to add additional functionality to your base application they would do that using the App Builder as they are now building/extending the apps not just using them.

Thats how it works.

tekhong
2014-04-17, 10:44
Hi Barry

I our case, the roles varies by organization. Big companies have more roles and small companies have fewer roles. It is almost impossible for us as developer to anticipate what are the roles for a given client. In addition, that may change with time for a given client

Is there anyway that we can have the end user to define the roles they need and then set the the permission to access pages, sections, fields, actions based on those roles?

Your advice is much appreciated

Thanks & best Regards

barrymavin
2014-04-17, 10:52
I would need to look into it. Its an issue on web and mobile. You cannot have every part of the app configurable like that without taking a performance hit.

There are also "UI states" that you should investigate also.