Quickbase

We have not had any focus on governance. Security can be as granular as you want it to be.

Security management capabilities have not been apart of my day to day work.

Data Privacy is being integrated and risk ranking for compliance is in place. We use LDAP SSO.

We have customized landing pages and access rights to various parts of our platform based on job function and responsibilities. This allows us to control access and information flow to the correct people and filter our classified information

We are Providing rights to only person where he can see his data only

Not really sure

This is application is full of security in terms of the data as it i using encryption on the database. As the Quick Base save the data on the cloud so there there will be no harm to data.

They are very secure in everything they do!

We trust that Quick Base is managing our data with the highest level of security. The system has many security features like IP whitelisting that help the user focus on the business and not about keeping up with security methods and trends, quick base does that for you.

None

We really didn't utilize any security or user management capabilities other than tying it into our employee verification systems. Our proprietary security and user management is very robust so utilizing any additional capabilities that Quick Base had really was redundant and unnecessary. As a result, it did not impact or improve business application security at all.

I know its capable but we did not do anything with this.

App Tokens and User Tokens from QuickBase are pretty powerful in combination with roles and permissions. Using these within the UiPath bots, I was able to make sure the data is inserted in a controlled and secure manner. In other places where I designed and developed QuickBase applications, we used SSO. In a Federal organization, I had used the "Everyone on the Internet" role that allows the large customer base to be able to add/modify their own data in a controlled manner. I had even implemented a custom user management and password management module within QuickBase that has all the regular provisions such as Registration, Login, Forgot Password, Auto-signoff after 8 hours of usage if the user has not signed off, etc. These measures not only saved the client money for user licenses across the world but also made sure they are in compliance with Federal security standards.

Auditing was turned on to provide detailed trail of changes at a system and data level. The amount of information provided by QuickBase through this is quite good. User permissions through groups works well, and the ability to test permissions by impersonating a user is a very powerful audit tool that prevents accidents when changing permissions.

We use QuickBase for a lot of the record-keeping requirements of our Food Safety Plan. We maintain SQF 9.0 compliance and are audited at least once every year. The auditors love QuickBase since we have access to almost any information they need very quickly. Doing trace exercises through QuickBase is a breeze. Our entire supplier verification program runs in QuickBase. I would recommend QuickBase for many requirements of a food safety plan.

Before QuickBase, much of our data was in excel format, so the security of QuickBase and the wide array of permission options that it gives is a huge step up from what we were using.

Through our Quickbase consultant, we built apps that allowed us to control user access. Each user was assigned a different layer of access to data, such as limited view, full view, edit, etc. This feature was extremely helpful in administering our small business and allowed us to tailor view/access to the right people.

In my experience, I have found it very useful in user management regulation. I really like that I am able to assign certain levels of access to specific users. Example of security would be the different access or viewing levels, from administration to participant to viewer only. This is useful in regards to sensitive information, like an employee complaint or comment.

I had a client need some of this information for their banking audit. Having QuickBase use AES-256 encryption and two data server locations helps with compliance. I've never had an IT department have issue with their security. Even the fact that Admins can not see passwords makes me feel better about their commitment to security. Users can still do dumb things, but in my mind QuickBase has checked off all the requirements needed to have the application pass security audits.

We used QuickBase to make sure that only certain employees have access to certain customer feedback. We also used it to add/remove and change permissions for certain users. We never used QuickBase for GDPR compliance although now that I think of it, it could have been used to setup rules that would ensure that certain sensitive information was not sent in customer communications.

I regularly will review the entire user list to deactivate users who have limited activity or never registered their accounts. The recent addition of the Audit capability allows me to always be able to answer any questions i have in terms of who made what changes and when. The controls native to the system allow me to lock down any fields that should not be viewed by anyone.

Our patient data is rigorously secured using Quickbase's security model. All the data we maintain is subject to HIPAA rules so this security is mandatory. We require various levels of access definitiona nd Quickbase has been able to address these needs very well.

We have leveraged the user management capabilities within Quick Base to control who has access to what data within the application. This is particularly useful when dealing with HIPAA and PHI issues.

I am not connected to this element of my company.

Security is at the core of Quick Base. Role Permissions are very granular, so for example if it easy to limit say a sales rep to see only their own customers and their orders, or to allow employees to only access data for their own division.

The role restrictions and the user tokens configured with the least access possible helped to provide right permissions needed for the functionality implemented with integrations setup