--- title: "QB Signatures messages and troubleshooting" slug: "qb-signatures-messages" updated: 2026-10-10T13:29:12Z published: 2026-10-10T13:29:12Z canonical: "help.quickbase.com/qb-signatures-messages" --- > ## 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. # QB Signatures messages and troubleshooting This article lists the messages you can see while setting up and using QB Signatures, grouped by where they appear. For each message you get the cause and what to do. Messages are quoted exactly as they appear on screen (including any typos), so you can search this page for the text you see. Common questions are answered at the end, in [Frequently asked questions](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-messages#faq). ## How messages appear - **When the window can't open for signing**, the **QB Signature** window shows the message instead of the signature pad, fields, and **Save** button. Close the window, fix the cause, and select the button on the record again. - **When a signature can't be saved**, a red message appears below the **Save** button. After a save error, the pad is turned off, so close the window and select **Sign Off** again. - **On the signature pad**, the pad's own message appears just below it, on the right. - **In the installation wizard**, messages appear in the red banner at the top of the step. Some messages about your account's authorization end with a support note from your account settings. ## When the signing window opens These messages appear when you select **Sign Off** or **Sign Off (Mobile)** on a record. Most of them are fixed in the button's formula by an app admin. See [QB Signatures formula URL parameters](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-formula-url-parameters). ### Button parameters | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *Invalid Parameters passed.* | The formula is missing a required parameter: **clientid** (inside *request=*), **appID**, **dbid**, **recid**, or **fafid**. Inside *request=*, a parameter name with the wrong capitalization, such as *appid* instead of *appID*, counts as missing. | Compare the formula with the parameters article. Inside *request=*, write each name exactly as shown there. | | *Please pass in valid clientid in the parameter!* | **clientid** is in the formula but has no value. | Copy your Client ID (*Q* followed by a number) from the **Sign Off** button the wizard created. | | *Please pass in valid Record ID in the parameter!* | The record has no Record ID# yet, usually because it hasn't been saved. It also appears if **recid** is empty in the formula. | Save the record, then select the button again. If the message continues, check *"&recid=" & [Record ID#]* in the formula. | | *Error ocurred : Insufficient field permissions - the token we are using does not have enough permissions to see the required fields.* | The user token saved during setup can't see one of the fields in the button. | Give that token's user access to the fields, or authorize the app again with a token for a user who has access (see [Authorization](https://help.quickbase.com/quickbase-extensions/docs/en/step-2-authorization)). | | *Invalid parameter passed - The field id - is not a field id of the file attachment field.Please pass in the field id of the file attachment field to display the link to the file.* | **fatermsfid** points at a field that isn't a file attachment field. | Change **fatermsfid** to the field ID of the file attachment field that holds your terms document. | | *Direct Call's URL is invalid.* | The **preqbaction** call isn't a valid address on your own Quickbase realm. | Build the call from *URLRoot()*, as in the **preqbaction** sample. Any other error from a **preqbaction** call also appears in place of the pad; check the call. | | *Error ocurred :* followed by technical text, for example *Object reference not set to an instance of an object.* | The formula has a problem QB Signatures can't describe more precisely. Common causes: - A field ID in **clist** doesn't exist on the table. - A plain URL has no **clientid**, so QB Signatures looks for *request=* and doesn't find it. - The *request=* value isn't valid, for example because part of it is outside *Base64Encode()*. | Check each field ID in **clist** against the table, and compare the formula with the samples in the parameters article. | ### Authorization Before the window opens, QB Signatures checks that your app is authorized for QB Signatures and that the user token saved during setup still works. | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *Quickbase Application - is not authorized to use QB Signatures.* followed by *There is no valid authorization record for client id: application id: for QB Signatures* | This app isn't authorized for QB Signatures under that Client ID. This happens when a button is copied to another app, or when **clientid** is wrong. | Run the installation wizard for this app (**Authorize New App** in the Extensions Portal), or correct **clientid**. See [Quickbase Extensions installation wizard overview](https://help.quickbase.com/quickbase-extensions/docs/en/juiced-add-on-installation-wizard-overview). | | A message that starts *Quickbase Application - is not authorized to use* and ends *The table passed in ( ) does not belong to the application passed in ( ).* | **dbid** names a table that isn't in the app given in **appID**, usually because one of them was typed in by hand. | Use *Dbid()* and *AppID()* in the formula, as the wizard does. | | A message that starts *Quickbase Application - is not authorized to use* and ends *User token ending with on the client profile is invalid. Please provide the valid user token.* | The user token saved during setup no longer works, for example because it was deactivated or deleted, or its user lost access. | Run the installation wizard again for this app and choose or enter a working token in [Authorization](https://help.quickbase.com/quickbase-extensions/docs/en/step-2-authorization). The new token replaces the saved one. | | *A user token is required to execute QB Signatures. We currently do not have a user token on file for your account.* | No user token is saved for this app. | Run the installation wizard for this app and enter a token in **Authorization**. | | A message that starts *We do not have sufficient permission to execute this add-on with the user token that we have on file ending with* | The token's user can't access the app. | Give the token's user access to the app, or authorize the app again with a different token. | | *Your Quickbase application - is Not authorized to use QB Signatures.* | QB Signatures is turned off for this app on your account. | Submit a [technical support case](https://help.quickbase.com/docs/get-help-from-quickbase-technical-support). | | A message that starts *Unable to get authorization details.*, for example *Unable to get authorization details. Quickbase Rate Limit Error Code : 429* | The authorization check couldn't be completed, often because Quickbase was briefly busy. | Close the window and try again in a moment. If it continues, submit a technical support case and include the full message. | ### Temporary tokens (enhanced security) When your account uses enhanced security, Quickbase sends a temporary token with the click, and QB Signatures checks that the signer can open the record. Both buttons the installation wizard creates send it: **Sign Off** through the *POSTTempToken* class and the *data-tempTokenDBID* attribute on its link, and **Sign Off (Mobile)** because the wizard creates it so it sends a temporary token. See [Change formula fields](https://help.quickbase.com/quickbase-extensions/docs/en/changing-formula-fields). | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *A temporary authorization token is required for this application. Please check your field settings or contact an App Administrator.* | No temporary token was sent. This happens with a **Sign Off** button whose formula lost the *POSTTempToken* class, with a button made by hand that doesn't send a temporary token, and when the signing URL is opened directly. | Open the record in Quickbase and select a button the wizard created. If the button was edited, an app admin should restore the *POSTTempToken* class and *data-tempTokenDBID='" & Dbid() & "'* from the [wizard's formula](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-formula-url-parameters#sample-url-code). | | *Your temporary authorization token does not have access to the requested record. Please contact an App Administrator if you believe you should have access to run this tool.* | The signer can't open this record in Quickbase, or *data-tempTokenDBID* names a different table. | An app admin should give the signer's role access to the record, and check that *data-tempTokenDBID* is *Dbid()*. | | *Your temporary authorization token has expired. Please try again or contact an App Administrator.* | The temporary token is only valid for a short time. | Close the window and select **Sign Off** on the record again. | | *Your temporary authorization token is not authorized to run this tool. If you believe you should be able to, try again from Quickbase or contact your app administrator.* | Quickbase didn't accept the temporary token. | Open the record in Quickbase and select **Sign Off** again. If it continues, contact your app admin. | | A message that starts *Something went wrong when we checked your temporary authorization* | The check couldn't be completed. | Try again. If it continues, submit a technical support case and include the full message. | ## Signing pad | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *Please sign here.* (below the pad) | The signer selected **Save** with an empty pad, or with a mark too short to count as a signature. Nothing is saved. | Sign in the pad with a full signature, then select **Save** again. | ## Saving | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *Please provide the required information and then click save.* *Please provide the required information and then click submit.* (when the button reads **Submit**) | A required signer field (marked with a red ***) is empty, or the terms checkbox isn't checked. Nothing is saved. | Complete every field marked with a red ***, check the terms box, and select **Save** (or **Submit**) again. | | *Quickbase related error ocurred while saving signature to Quickbase application.* followed by Quickbase's details | Quickbase rejected the update. For example, the setup token's user can't edit the record or one of the fields, a required field on the record is empty, or a signer field is a formula or lookup field. | Read the details after the message, fix the record or field, then close the window and select **Sign Off** again. | | *Error ocurred while saving signature to Quick ase application.* followed by details | Another problem stopped the save. | Close the window and try again. If it continues, submit a technical support case and include the full message. | | *Your session has expired. Please close out of this window and try again.* | The window was open too long before the signer selected **Save**. | Close the window and select the button again. | | *Your signature has been saved successfully to Quickbase.* and a **Close** button | The signature, sign-off date, and the signer's entries were saved. | Select **Close**. The window closes (or returns to the record if it can't close), and the record refreshes. | ## On a phone or tablet | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *You will be redirected in 5 seconds.* after *Your signature has been saved successfully to Quickbase.* | The signature was saved on a phone or tablet. This depends on the device, not on the button. | Nothing. After 5 seconds the window returns to the record, or to the **rdr** address if the button sets one. | ## Installation wizard: QB Signatures Setup step These messages appear when you select **Finish** on the **QB Signatures Setup** step. See [QB Signatures Setup](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-setup). | **Message** | **Cause** | **What to do** | | --- | --- | --- | | *Please select a table you would like to set up with QB Signatures.* | No table is chosen. | Choose a table in **Select Table to Setup**. | | *The usertoken selected does not have permissions to create fields in the
table. QB Signatures needs permissions to create fields in order to continue the setup.* | The wizard adds fields to the table, and the token's user can't create fields in it. | Go back to [Authorization](https://help.quickbase.com/quickbase-extensions/docs/en/step-2-authorization) and use a token for a user who can, such as an app admin. | | *Please enter a name for the new field.* | You chose **Create a Field** in a signer field drop-down but left **New Field Name** empty. | Enter a name. | For messages from the shared wizard steps, see [Quickbase Extensions installation wizard overview](https://help.quickbase.com/quickbase-extensions/docs/en/juiced-add-on-installation-wizard-overview). ## Frequently asked questions ### I selected Save and nothing was saved. Why? Look at the window: - *Please sign here.* below the pad means the pad was empty or the signature was too short. Sign again with a full signature. - *Please provide the required information and then click save.* means a field marked with a red *** is empty or the terms box isn't checked. - Any other message: find it in [Saving](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-messages#saving). ### Does Sign Off (Mobile) work with enhanced security? Yes. The installation wizard creates it so it sends a temporary token, so it works on phones and tablets when your account uses enhanced security. If it shows a message, find it on this page, for example in [Temporary tokens (enhanced security)](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-messages#temp-token). ### Can this be used on a phone or tablet? Yes. The installation wizard adds a **Sign Off (Mobile)** button that opens the signing window in a new browser window instead of a pop-up. On any phone or tablet, the window returns to the record about 5 seconds after the signature is saved. See [On a phone or tablet](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-for-quickbase-features-and-functionality#mobile). ### Why does the button say the app isn't authorized after I copied it to another app or table? Each app must be authorized for QB Signatures. Run the installation wizard for the new app (**Authorize New App** in the Extensions Portal), or use **Setup Table** for another table in an app that's already authorized. The wizard creates new buttons with the right IDs, so you don't need to copy them. See [Authorization](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-messages#authorization). ### Why does my custom heading show %20 or other codes? The heading was wrapped in *URLEncode()* inside *request=*. Inside *request=*, type the text as-is, for example *"&titledlg=Please sign to accept delivery"*, and don't use *&* in it. Use *URLEncode()* only in the plain form. See [Writing values inside request=](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-formula-url-parameters#two-ways). ### Why is my signature file named Signature_4573.gif? The button the wizard creates names files *Signature_* plus the milliseconds of the time the button was shown, and QB Signatures adds the Record ID#. In *Signature_4573.gif*, *457* comes from the clock and *3* is the Record ID#. For names such as *Signature_3.gif*, change the **fn** line in the button formula to *& "&fn=Signature_"*. See [Sample formula: Sign Off button](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-formula-url-parameters#sample-url-code). ### How do I capture two signatures on one record, such as a technician and a customer? Add a second set of signature fields and a second button on the same table. See [Capture a second signature on the same record](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-screenshots#second-signature). If each signature belongs to a separate item, such as each line of an inspection, put the button on a child table instead (see [Place signatures from related records](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-screenshots#from-related-records)). ### How do I add a terms document, or use one terms file for every record? Add **fatermsfid** to the button with the field ID of the file attachment field that holds the document. To use one shared file, store it on one record of another table and add **tdbid** and **trecid** (for now, in the plain form only). See [QB Signatures formula URL parameters](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-formula-url-parameters). ### Why doesn't the terms link open anything? The terms file attachment field is empty on that record (or on the **trecid** record). Attach the document to the field. The signer still has to check the box, even when the link doesn't open. ### How do I put the signature on an XL Docs or PDF Stamper document? The signature is an ordinary image in a file attachment field, so place that field as an image. See [Images](https://help.quickbase.com/quickbase-extensions/docs/en/xl-docs-build-a-template#images) in *Build a document template* for XL Docs and [PDF templates](https://help.quickbase.com/quickbase-extensions/docs/en/pdf-templates) for PDF Stamper. For Exact Forms Plus, see [Use signatures in documents](https://help.quickbase.com/quickbase-extensions/docs/en/signatures-screenshots). ### How do I include a signature image on an Exact Forms Plus template when the signature may not exist yet? You can place a signature on an Exact Forms Plus document with the image syntax *~i:{field ID}:{size in pixels}~*—for example, *~i:12:200~*. (See [Include images in documents](https://help.quickbase.com/quickbase-extensions/docs/en/efp-images) for more about images in Exact Forms Plus.) If the record hasn't been signed yet and you want a blank space instead, put the image syntax in a formula text field that only outputs it when the signature exists. For example, create a **Formula - Text** field that checks the signature file attachment field: ``` If(ToText([Signature File]) <> "", "~i:12:200~", "") ``` > [!NOTE] > Note > > Place the new formula field's field ID on the document template, and include it in the *clist* on the Document Templates table. Include the file attachment field that holds the signature image in the *clist* as well, with the formula field's ID before the image field's ID. So if the formula field is 23 and the image field is 12, the *clist* should contain *##.##.23.12.##.##*. ### Who shows as the signer, and why does the record say someone else modified it? QB Signatures saves every signature with the user token saved during setup, so **Last Modified By** shows that token's user, not the signer. To record who signed, ask the signer to type their name in a signer field (**fid1**), or save the Quickbase user who opened the window with **qbuserfid** and **signeradmin** (for now, in the plain form only). Because of this, signers don't need permission to edit the record. ### Can I clear or redo a signature? Before saving, the signer can clear the pad with the circular-arrows icon below it and sign again. After saving, select **Sign Off** again and sign: the new signature replaces the one in the file attachment field, and **Sign-off Date** is updated. To remove a signature completely, edit the record in Quickbase and remove the file and the date. ### How do I add QB Signatures to another table? Run the installation wizard again. In the Extensions Portal, use **Setup Table** on the app's row to go straight to the **QB Signatures Setup** step with the saved token, or **Authorize New App** for a table in a different app. See [Quickbase Extensions installation wizard overview](https://help.quickbase.com/quickbase-extensions/docs/en/juiced-add-on-installation-wizard-overview). ### The wizard won't let me finish. Why? Choose a table, enter a name for every **Create a Field** choice, and make sure the token's user can create fields in the table. See [Installation wizard: QB Signatures Setup step](https://help.quickbase.com/quickbase-extensions/docs/en/qb-signatures-messages#wizard). ### Is this a legally binding electronic signature? No. QB Signatures captures an image of a signature and records when it was saved, but it doesn't verify the signer's identity, keep a tamper-evident audit trail, or produce a signing certificate. For agreements that need a legally binding electronic signature, consider [JuicedSign](https://help.quickbase.com/quickbase-extensions/docs/en/overview-1) or Docusign for Quickbase, and check with your legal team about your requirements. If a problem continues, submit a [technical support case](https://help.quickbase.com/docs/get-help-from-quickbase-technical-support).