QuickBase relies on email addresses to identify user accounts. When QuickBase user accounts are created, they are initiated and confirmed via an email address. Sometimes a user may inadvertently create two or more accounts, each having a different email address. This can easily occur when users change companies and email addresses.
The QuickBase cookie stored in your browser expires after 12 hours, then prompts the user to login again.
In some cases, accounts may be configured to integrate with an internal LDAP instance, in which case the behavior may vary slightly. Check with your local IT group to determine if your QuickBase profile is integrated with your LDAP.
The security message is displayed by your browser when QuickBase attempts to display an image not hosted by QuickBase. To prevent the security message from popping up, you'll have to store the image file within QuickBase.
To do this:
1. From your My Apps page, click + Create a New App.
The reference field (aka record-picker field) in the details table when displayed read-only always displays the value of the key field in the corresponding master record. The key field in the case you cite above is the Record ID#.
First, confirm that the email address connected with your user account is the one you're checking for your password email message. QuickBase sends the password message to the same email address you used to create your user account.
Some probable causes are:
- an application manager has typed the wrong e-mail address
- the user registered with a different e-mail address
- the user has multiple QuickBase user accounts
- the user is assigned the wrong role
To resolve this problem, first check for the following issues:
Multiple user accounts belonging to one individual create confusion from time to time. For example, say you created an account using your Gmail address and someone has invited you to join their application using your corporate e-mail address. Once you sign on to QuickBase using both, you have two separate user accounts.
The simplest thing for you to do is to deny the user access to your billing account. When you put a user on the deny list, QuickBase makes sure that the user cannot log in to any applications in your account.