Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
Knowledge Base
When creating multiple custom access rules for a role, all conditions must be met. Is there a way to specify an OR instead of AND when creating access rules?
There are two workarounds for this - depending upon what you want to do.
SCENARIO ONE: OR conditions are in the same field.
Say you want one person to see all records where the status is "on hold" OR is "Open." Tackle this within a single access rule. To do so, create a rule.
Within the first dropdown select the Status field.
In the second dropdown select "is".
In the final criteria dropdown, select <other>. A box appears.
Type: On Hold OR Open
OR must be capitalized. (Read more about setting OR conditions for searches and matching criteria here: https://www.quickbase.com/help/matching_a_or_b.html)
SCENARIO TWO: OR conditions are in separate fields.
The workaround for this is to create two roles. Create one custom rule in the first role and create the second custom rule in the second role. Then share the application with the user or group twice: once in each role.
This method works because permissions are additive. When a user accesses an application in two roles, QuickBase grants all rights that either role allows. Read more about how this works and learn what else you need to consider when one user is in two roles: https://www.quickbase.com/help/reordering_role_priorities.html
- 37877 reads
Rate This
Similar Articles
Browse by Category
Knowledge Base Categories
- Accounts (35)
- Application (45)
- E-Mail (7)
- Fields (41)
- Forms (20)
- Formulas (18)
- General (69)
- Other Product (7)
- Pages (1)
- Product (5)
- Reports (15)
- Roles (4)
- Search (1)
- Tables (6)



Comments
alternate work-around for scenario-2
For scenario-2 cases involving text fields, create a new field that is a concatenation of the the two or-criteria fields (call is [combo]). Then, set the record-access conditon to [combo] contains "a" or "b" where "a" and "b" are the two criteria to be applied to the separate fields.
Example: Complex condition [A] = a OR [B] = b. The combo field can take the values [combo] = {xy, ax, xb, ab} where x and y are values other than the filter-criteria a and b. ax, xb and ab will all trigger a "true" condition for record access.
Post new comment