What is Client Credentials?
Your extensions sign in to Quickbase with a Quickbase user token to read and write data in your apps. Some extensions also use saved Amazon S3 or DocuSign credentials. Client Credentials is where you see and replace these credentials after setup, without running the setup wizard again.
Use it when:
A user token was deleted, regenerated, or expired in Quickbase, and your extensions stopped working.
The person who owns the token is leaving, and you want your extensions to run with a different user's token.
You need to give one app's extensions a different token from the rest.
You rotated your Amazon S3 access keys or changed your DocuSign password.
Who can use it
Only the company's Client Admin sees Client Credentials in the left menu.
Admins and Users don't see it. If they need a credential replaced, their Client Admin does it.
Open Client Credentials
Sign in to the Extensions Portal and select your company.
In the left menu, select Client Credentials. The Credentials page opens in a window inside the portal.
The page has three sections: Amazon S3, DocuSign, and your Quickbase user tokens.
Quickbase user tokens
The token table lists each user token your extensions use, one row per token:
Column | What it shows |
|---|---|
The Quickbase user who owns the token. | |
Credential (last 6 characters) | The end of the token, so you can match it to a token in Quickbase. The full token is never shown. |
Client Records | How many places in your company's account settings use this token. |
Addon Records | How many of your extension subscriptions use this token. |
Auth Apps | How many authorized Quickbase apps use this token. Select the number to see them, and to replace the token for a single app. |
List of QB Applications | Select it to see every Quickbase app the token can currently access. |
Update | Where you enter a new token to replace this one everywhere it's used. |
Before you replace a token
Create the new user token in Quickbase. See Create and use user tokens.
Give the new token access to every app that uses the old one. To see which apps those are, select the Auth Apps number. If the new token is missing access to any of them, the update is rejected.
Replace a token everywhere it's used
Find the row for the token you're replacing, using its email and last 6 characters.
In the Update column, paste the new token into the New credential… box.
Select Confirm.
The portal checks that the token is valid and can access every app the old token is used for.
If it can, the token is replaced in your account settings, your extension subscriptions, and your authorized apps. You'll see Updated credential ending "
xxxxxx" → "yyyyyy". Please reload the page to see the latest changes.If it can't, nothing is changed and you'll see Update failed: The new credential does not have access to all required apps. Missing: …, followed by the app IDs it's missing. Grant the token access to those apps in Quickbase, then try again.
Reload the page to see the updated list.
Replace a token for one app only
In the token's row, select the number in the Auth Apps column. The Authorized apps window opens. It lists each app's Record ID, Application name, and Related Add-on (the extension).
On the app's row, enter the new token under New Credential, then select Update Credential.
The new token must have access to that app.
If it does, you'll see Updated. Please reload the page to see the latest changes.
If it doesn't, you'll see New credential does not have access to the selected app.
Add your first token
If no tokens are on file yet, the page shows No existing credentials found in place of the table.
Paste a user token into Enter a fresh credential.
Select Add a new Quickbase credential.
The token must be valid and have access to at least one Quickbase app.
If it does, you'll see New credential is valid and has access to
napp(s).If it has no app access, you'll see This credential does not currently have access to any Quickbase apps. Please grant app access in Quickbase first, then try again.
Amazon S3
This section appears only if your company already has Amazon S3 credentials saved. Otherwise it reads No S3 credentials found. To add S3 credentials for the first time, see Amazon S3 options step.
To replace your keys:
Select Edit next to Access Key and enter the new key. Enter it again in Confirm access key.
Do the same for Secret Key.
Select Update S3 Credentials. When the save succeeds, you'll see Saved. Please reload the page to see the latest changes.
Both keys are required, and each must match its confirmation.
The eye icon shows or hides a key.
Select Cancel to discard your changes.
DocuSign
This section shows your DocuSign Auth Option. What you can do depends on it:
Access Tokens: select Generate Docusign refresh token to sign in to our DocuSign utility and generate a new refresh token.
User ID-PW:
Select Edit next to Password.
Enter the new password, and enter it again in Confirm password.
Select Update DocuSign Password.
If DocuSign isn't set up for your company, the section reads No DocuSign settings found.
What you can't change here
The following can't be changed in Client Credentials. For any of them, open a Quickbase technical support case:
Dropbox and Egnyte connections.
Your Amazon S3 bucket or region.