---
title: "Code pages and outside Quickbase"
slug: "code-pages-and-outside-quickbase"
updated: 2026-09-11T14:39:40Z
published: 2026-09-11T14:39:40Z
canonical: "help.quickbase.com/code-pages-and-outside-quickbase"
---
> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Code pages and outside Quickbase
> [!NOTE]
> Note
>
> This article pertains to the Quickbase updates that enhance security. Learn more about [posting a temporary token from a Quickbase field](/v1/docs/post-temporary-token-from-a-quickbase-field).
This article discusses changing your code pages in your Quickbase apps to meet the upcoming security changes and help keep your data secure.
Additionally, if you use our extensions from outside Quickbase, you likely need to implement a code page to continue using our extensions in the same way.
This article is written for people with the technical skills to change and implement code pages. If you have questions about changing any of these features to comply with our new security measures, submit a [technical support case](https://help.quickbase.com/docs/get-help-from-quickbase-technical-support).
## Use cases
### Existing code page
If you have an existing code page that uses our extensions, you need to implement a way to gather a [Temporary Authorization](https://developer.quickbase.com/operation/getTempTokenDBID) token and pass it to our extension through the body or form of the request. This must be done this way because of how our extensions interact with the Quickbase front end—they need to POST a token to us to consume while also redirecting the user, all in one call.
The following is an example of this code snippet, showing some temp-token logic:
To summarize, first gather the temp-token using the authorization call to the JSON API. This only works if the user has an ongoing session within Quickbase.
Next, create a *form* element in your DOM (if one is not already present) and add an input named *TempToken*, setting the value to the authorization token you received. Append that input to the form, and submit the form. Make sure you set the form's method to *POST* and, if you want to open the result in a new tab, set the form's target.
If you want to open the extension in a pop-up from here, use the form event *onsubmit* to set the target of the submission.
Otherwise, if you don't need to present the extension to the user and only need to call the extension to start a process, you can POST directly to the extension with the temp-token in the body, keyed as *TempToken*. You need to do some work to figure out how this works. Our suggestion is to manually create the body as described. However, another option is to use a form submission with *preventDefault* on the submission event and add further logic to complete the POST. Another method is to use a hidden iframe and set the form's target to the iframe—this way the redirect technically happens but is hidden.
### Dashboards and outside of Quickbase—bookmarks, links, etc.
If you are currently using an extension from a source outside of Quickbase, or in a place inside Quickbase that doesn't have access to temp-tokens (Dashboards)—you can use the following code page.
Create a new code page with the following code, and make note of the PageID:
```plaintext
Please wait while the page loads...
```
Next, go back to your Formula field, and change it to point to this code page instead. See the following images for the steps:
The formula should become:
Essentially, the extension URL must go into the *exturl* parameter (Base64-encoded), and you must set the *extdbid* parameter to the primary DBID used by the extension.
Remember to change the *PageID* in the code page URL to the correct PageID.
If you have questions about changing any of these features to comply with our new security measures, submit a [technical support case](https://help.quickbase.com/docs/get-help-from-quickbase-technical-support).