---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Administering user access for deployed Creator Studio apps

# Administering user access for deployed Creator Studio apps {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

After users build apps in Creator Studio and you deploy them to production, as an admin, you are responsible for granting access to those apps to users.

## Assign user access in production {#creator-studio-administering-user-access-apps__section_lnp_nw3_v1c}

Applications must be deployed to the production instance, which is where you assign user access.

Users with the agent role are fulfillers, and should automatically get access to apps built in Creator Studio.

Assign users the agent role for the app's scope, for example, <kbd class="ph userinput">x_snc_jd_it_fulf_0.agent</kbd> for an app with the scope <kbd class="ph userinput">x_snc_jd_it_fulf_0</kbd>. For details on assigning roles to users, see [Managing roles](https://www.servicenow.com/docs/access?context=ua-creating-roles&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).

## Restricting user access to forms {#creator-studio-administering-user-access-apps__section_hdw_lc5_gbc}

By default, all users on the production instance get access to forms built in Creator Studio, but Creator Studio developers can choose from existing access criteria if they want to restrict access. The Available For and Not Available For form settings are lists of
User Criteria Records. For more information, see [Set security for items and categories](https://www.servicenow.com/docs/access?context=c_ServiceCatalogAccessControls&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

Developers can work with admins to define new access criteria for their app's forms to define the proper access from within Creator Studio. For more information, see [Edit the settings for a form in Creator Studio](https://servicenow-prod.fluidtopics.net/3eWx5qOWtDrhYcm6NLAGQw "Edit form settings if you need to change its basic attributes, such as its associated image or attachments are allowed.").

## Personas for apps built in Creator Studio {#creator-studio-administering-user-access-apps__section_rqw_2b5_gbc}

Requester
:   Someone requesting something, like a piece of equipment or permission to do something.

Fulfiller
:   Someone who works on requests. Fulfillers may also approve or deny requests, depending on any approval automation for the app.