Want your team to be able to see all data but other users should only be able to see specific records associated with their account?
Use filters to control which records appear in a list. For example, only show the user their own collection of properties. No more, no less.
By default, your app comes with Team Admin and User roles. But you can create as many other roles as you like and assign them to different users. This is critical if you want to limit visibility and data access to different groups of users. For example, you may want your Finance team to be able to access different information to your Ops team.
Control which users have access to specific pages and individual sections on a page as well.
Set visibility by:
If you want, you could only show a page to users whose first name is Harry. We love practical examples.
At the database level, you can determine by user role whether users should be able to read, create or update records in each collection.
You can also choose whether each user group should have access to all records or only their own records (kind of like filters above).
Finally, you can also control their access at field level as well. Perhaps there’s some internal only fields that your users should never be able to see.