When Quickbase sends emails, it checks permissions. That is, Quickbase reviews what users have access to, based on their role. Then, the only data sent in the email is data that someone has access to.
Quickbase always checks the permissions, or access, of the email owner. By default, Quickbase also checks the permissions of recipient. Control this with the Permission and data access setting. The options for this setting include:
-
Check recipient permissions
-
Ignore recipient permissions
What permissions does Quickbase check?
Custom emails will likely contain table data. Quickbase always checks the email owner’s permissions.
When Check recipient permissions is selected, Quickbase checks the permissions of each email recipient when it sends an email. If a recipient does not have access to certain data, Quickbase does not include it in the email.
When to ignore recipient permissions
Generally, it's most secure to check permissions when sending emails. However, there are some cases when it might be beneficial to ignore recipient permissions:
- You want to send emails to non-Quickbase users
- The email will go to lots of users, and the app has very complex permissions
- Checking permissions may significantly impact how long it takes to send the email
When Ignore recipient permissions is selected, Quickbase sends data according to the email owner's permissions.
For example, if you are the email owner and you have permission to see all data in the app, Quickbase sends anything you decide to include in the email.
You must select this option to send the email to users outside of Quickbase.
BCC/CC permission checks
Your account may allow BCC/CC of custom emails.
Quickbase does not check permissions for BCC/CC recipients. Instead, it applies the permissions of the recipients in the To field to BCC/CC recipients.