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#.
If an App Manager or Billing Account Administrator is departing, but still available, he or she can easily transfer ownership to someone else. To learn more, please see our Transfer Management of an Application help topic.
Instead of using Lastname: to search, use Email:, as some users do not have the Last Name and First Name values set for their user profile. Using Email: A-F returns the most inclusive list and will sum to the same number as presented in your account usage stats section.
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.
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.