# Security tip: Managing role-based permissions in Glide apps

**URL:** https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854
**Category:** Community Resources
**Tags:** security, actions, collections
**Created:** [November 12, 2024, 5:04pm UTC](https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854 "2024-11-12T17:04:02Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)
#### Post date: [November 12, 2024, 5:04pm UTC](https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854/1 "2024-11-12T17:04:02Z")

</div>

If you’re using Glide apps and need secure control over user permissions, be aware that Glide’s visibility conditions (like showing or hiding buttons for certain roles) are _not_ a security feature. While these conditions are helpful for managing the app’s appearance, they do not protect actions at the backend level.

## Key Points to Protect Your Data

1. **Row Owners for Data Protection** : Enabling “Row Owners” is effective for securing individual records (for viewing, editing, and deleting), but it doesn’t apply to adding new records.

2. **Best Practice: Separate Admin and User Apps** : For role-based security, the best approach is to create two versions of your app:

3. **Future Improvements in Role-Based Access Control** : The Glide team is exploring stronger role-based access control options to enhance backend security, though no timeline is set.

In summary, separating user roles across different apps is the most effective way to protect sensitive actions for now. Glide’s visibility settings are great for appearance, but backend security requires more. For further guidance, see Glide’s documentation on row ownership and permissions.