Hide the Code from End user after deployment

Normal users do not have access to the Appian designer and cannot see or modify your application.

Yes, Basic user do not have access of Appian designer, but i want to restrict the other users in different org, when i Deploy my Application in there org.
i want that they can just use the Functionality without any data modification.
Or can we Hide the Application access.

Then, depending on what "data modification" means in your application, you have to configure process models and/or actions, site pages, related actions etc. in a way that fits your requirements. Check: docs.appian.com/.../securing-applications.html

Is your question whether you are able to deploy your application at your customer's site and prevent them from seeing the expressions/components etc that went into the app?

Hi suryanshuj0001 If you are deploying an application to a different organization's environment, and if that environment has some Admin users then definitely they will be able to view/modify/delete your the application related data once it's deployed to their env.

Out of interest, why do you want such restrictions post deployment of an application to the other organizations environment?

As per my understanding, let's say you are working on a client based application (on Offshore model, and development is happening in your own organisation's local server) and now you want to deploy this application to the target environment (i.e. your client's env) in such case you cannot restrict the admin users from viewing the code because, they may want to opt some other organisation for their application support activity and that's what they are paying for, also they will have some administrator user to keep an eye on system alerts if in case something goes wrong.

It's obvious that, the basic users will have only viewer access to your application but you can't restrict an Administrator(of target env) from viewing your code once it's deployed to their org env.

Hi suryanshuj0001 If you are deploying an application to a different organization's environment, and if that environment has some Admin users then definitely they will be able to view/modify/delete your the application related data once it's deployed to their env.

Out of interest, why do you want such restrictions post deployment of an application to the other organizations environment?

As per my understanding, let's say you are working on a client based application (on Offshore model, and development is happening in your own organisation's local server) and now you want to deploy this application to the target environment (i.e. your client's env) in such case you cannot restrict the admin users from viewing the code because, they may want to opt some other organisation for their application support activity and that's what they are paying for, also they will have some administrator user to keep an eye on system alerts if in case something goes wrong.

It's obvious that, the basic users will have only viewer access to your application but you can't restrict an Administrator(of target env) from viewing your code once it's deployed to their org env.