--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Explore # Exploring Creator Studio {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Exploring Creator Studio Creator Studio streamlines app creation by breaking it down into simple, manageable steps centered around handling requests. This facilitates efficient app development and management of user submissions. Show full answer Show less ## How Requests Are Stored Requests made by users are stored in tables within Creator Studio, where each row represents an individual request. This structured storage allows for easy review and management of requests. ## How People Enter Requests Users submit requests by filling out forms within your app. These forms capture all necessary information the fulfiller needs to process the request, such as the request details, requester's name, email, and request date. You determine the specific fields based on what information reviewers need to approve or reject requests. ## Key Roles * **Requester:** The individual submitting a request, such as for equipment or permissions. * **Fulfiller:** The person responsible for acting on requests, including approving, denying, or fulfilling them, possibly through automated approval workflows. ## Next Steps for ServiceNow Customers You can experiment with Creator Studio using your Personal Development Instance (PDI), where it is pre-installed via the Application Manager. This enables hands-on learning and app creation tailored to your organizational needs. Creator Studio makes creating apps easier by dividing their creation into simple steps. In this section, we'll explain each one. All the steps involve requests. So, we'll start by explaining how Creator Studio stores requests. Summary: After reading this section, you'll understand: * How requests are stored * How people enter requests * How your app automatically does things {#exploring-creator-studio__ul_ebx_2mf_s1c} ## Let's talk about storing requests {#exploring-creator-studio__section_zh1_gmf_s1c} When people make a request, we have to store it somewhere so someone can review it later. **Tables hold requests** Creator Studio stores requests in a table. Each row in that table is a request. Here's a simplified version of a table with three requests. Use cases: * My monitor stopped working. I need a new one. * I'm requesting a new mouse so I can have one at home and in the office. * My laptop is over four years old. I want to request a replacement. {#exploring-creator-studio__ul_ttx_cn3_t1c} **People enter requests using forms** How do people enter requests that eventually get stored in the app's table? They use your app to fill out a form. The questions on the form contain the information your fulfiller needs. In our app's table, questions are stored as part of the [record](https://servicenow-prod.fluidtopics.net/ZqGMKydkSeuIVVnjYgZtrw#gloss-record-creator-studio "A task or request that needs to be acted on. All rows in that table for an app are individual records. Records have different states depending on what actions have been taken."), which is composed of all the information on the form. {#exploring-creator-studio__table_edj_dl1_2bc__entry__4} | Request | Name | Email | Request date | |-|-|-|-| | I need a new monitor. | Sushma Singh | SushmaSingh@example.com | 04-05-2024 | | I need a new laptop. | Peter Smith | PeterSmith@example.com | 05-01-2024 | [ ] {#exploring-creator-studio__table_edj_dl1_2bc} In this example, the form has four fields: * Request * Requester's name * Requester's email address * Request date {#exploring-creator-studio__ul_ovv_ddg_s1c} These fields contain all the info the reviewer needs to accept or reject the request. You'll have to figure out all the information your reviewer needs to make a decision. Later, we'll show you how to create a form (using AI or on your own) in the section [Working with forms in Creator Studio](https://servicenow-prod.fluidtopics.net/rii3B__WyymcafhDHhOo4A "To add items or services to your catalog, you must create a different form for each thing being requested."). Key terms: 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. Okay, now you understand that requesters fill out forms to create requests and Creator Studio stores those requests in the app's table. ## Try Creator Studio on a PDI {#exploring-creator-studio__section_sdh_bvw_qbc} Want to play with Creator Studio on your Personal Development Instance (PDI)? It comes automatically installed from the Application Manager on your PDI. For more information, see [Personal developer instance guide](https://servicenow-prod.fluidtopics.net/zYU4E4RsssMJufmUKWiAaQ "ServiceNow offers free personal developer instances (PDIs) to Developer Program members to learn, explore, and experiment with the ServiceNow AI Platform.").