Now that you know how to build your application using different forms, what remains is to Publish your application so that it can be available to the users. In some scenarios, the applications can be limited to organization users while in others you may allow public access. When publishing your application you can thus define the access as organizational access or public access to your application.
Let us first have a look at this video to understand the access you can assign to your applications when you publish it.
The organizational access to any application is used to limit access to only authorized users with the necessary organizational credentials. Usually, when you have an application customized for customers or users of a specific part of your organization you would need to limit it with the organizational access.
For the users who would need access to such an application, you can create credentials by using the Users tab of the platform.
Thus when you enable organizational access you are going to limit access to the application to the select users with your organizational credentials.
Now let us see how to grant organizational access to the users. For the particular application, click Publish. Add the appropriate release notes and version number. Now under Organizational Access, you simply need to click Enable to enable access to the organizational users, and you are done.
Now once you click Publish, your application is published to the platform. If you want to check or install the application you can check it on your Android Playstore, Apple Appstore, or even on the Web Browser.
Now say for example you try it out on the Web Browser, you will first be prompted to enter your credentials. Enter your organizational credentials and you would then be taken to the application.
If we disable the organizational access the published app’s icon would not be visible on the home screen shown in the illustration above.
Now we have seen that organizational access requires the credentials for the specific users or user groups to be defined for the applications. Now if the application has public access, it means that you can share the link with the users or even use embed code to add the application to another portal or website created for the users. The users need not necessarily be a part of your organization, they can be external users also. They would not have to log in using the organizational Logon screen and can directly access the application. However, if you do not want any user to access it outside the container application, make sure that you do not provide Public Access.
To enable Public access, you need to first publish the application and then under Public access , click to Enable access. Once done you will get the public link which you can simply copy and check it in a web browser. Optionally you can also copy the Embed code provided and add it to your website or portal and allow the user to use it in a web browser. Typically you can see the application from the portal directly without having to log in.
Now if you disable the public access and try to open the app using the above link in a browser you would not be able to open the application.
You can thus make use of the organizational and public access to define how your applications would be seen by the users and access granted to them.