
Knowledge Base
Articles In This Section
How to Create User Groups in QuickbaseAdding a new User Role in QuickbaseHow to Share with Everyone on the Internet How to Archive Records Using Role Permissions | INTERMEDIATEHow to Use and Adjust Roles in Quickbase | BeginnerHow to Switch a Client to a New Quickbase Developer How to Display Information for Certain Roles in QuickbaseConditional Filters for Record Permissions Using Roles | INTERMEDIATEHow to Add New Users to your Quickbase ApplicationSections
To deny a user access in Quickbase, you can remove them from the app, change their role to one with no permissions, or deactivate their account at the account level. The method depends on whether you want to restrict access to a single app or the entire Quickbase account.
The most common method to deny access to just one Quickbase app:
Results: User can no longer access that app but may still access other apps.
If you want to restrict (not fully remove) access:
Result: User technically has access but cannot view, edit, or interact with data.
If you want to remove access entirely across Quickbase:
Result: User cannot log in or access any Quickbase apps.
To prevent any issues once you have deactivated a user, we recommend always checking
Yes. Assign them a role with no permissions or deactivate them at the account level.
They lose access to that app but can still access others if permitted.
No. Their data and activity remain in the system.
Yes. Use roles with limited or no permissions.
If you need help with User Best Practices for Quickbase applications, Quandary Consulting Group provides Quickbase consulting and optimization services in Denver, Colorado and across the United States, helping organizations improve data quality, usability, and automation.
Resources


© 2026 Quandary Consulting Group. All Rights Reserved.
Privacy Policy