It is very important in any web application to correctly define access to each area of your application. If you need to restrict end-user access to specific areas, or operations in a web application, you must validate their permissions using roles and provide control access to screens, screen elements or actions, as required. In the ONEWEB platform, this can be achieved through the End User Access Management screen under the Application Setting menu.

Application owners can create various roles with various levels of access from the Add Role option on the Roles screen. To restrict end-user access to the screens of the application, the admin user must create permission objects for each screen and then add the appropriate permission and screen objects to the roles.

Once the roles are created, the application owner can assign the appropriate roles to each of the end-user to manage access.

When collaborating between different people to create an application, the most important thing for seamless development is to have a clear-cut division of work and responsibility. AppSpace allows users to achieve it through the Development Team access management screen.

The admin can manage the existing roles or create new roles from under the Access Control Menu.

When the admin adds a new role, the admin can choose the permissions and objects to be associated with that role.

All the components for which the permission is enabled can be viewed under the Object Component section on Access Control.

Once the roles and components are ready, the application owner can create a team and assign the roles and permissions. Use Add Developer button to add more users to the team.

When adding more team members, the admin can assign the roles and any additional permissions and objects to the team member.

Permissions can be used to restrict access at the module level or at the component level. For example, a user with access to only Forms, cannot view, create or edit the other module components of the App. They will have access to only view, edit or create forms. Also, they can view only the forms for which permission is not enabled.

But if the Forms have permission enabled on them, then only the user to whom the forms are assigned can view or edit them.

For e.g. If Permission is enabled on the UserRegistrationApproval Form, then the user with access to Forms can view/edit only the RegistrationMonitor Form by default.

For a user to have access to the UserRegistrationApproval form, it has to be specifically granted to the user. The admin can edit the user roles to add additional permissions.

AppSpace promotes collaboration between users to create an enterprise application. App owners can set permission at the module level or even at the component level for different users. AppSpace provides the Application settings menu for this.

There are two types of Application Settings - one for the End Users of the Application and another for the Development team. The owner or admin can set up permission and roles for the end-user as well as for the development team. This enables the owner to tightly control who has access to which component or what role. The admin or owner of the App can go to the Application Settings and manage his Development Team by adding more members to his App and assigning the roles.