# How to use cloud\_username as filter for layer?

**URL:** https://community.qfield.org/t/how-to-use-cloud-username-as-filter-for-layer/1374
**Category:** Ask the Community
**Created:** [6 December 2025 12:00 UTC](https://community.qfield.org/t/how-to-use-cloud-username-as-filter-for-layer/1374 "2025-12-06T12:00:57Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Jeroen-GroeneBij](https://dub1.discourse-cdn.com/flex018/user_avatar/community.qfield.org/jeroen-groenebij/32/905_2.png) [@Jeroen-GroeneBij](https://community.qfield.org/u/Jeroen-GroeneBij)
#### Post date: [9 December 2025 12:17 UTC](https://community.qfield.org/t/how-to-use-cloud-username-as-filter-for-layer/1374/5 "2025-12-09T12:17:16Z")

</div>

I have created a workaround. See this topic in Advanced Use and Customization:

> [@Set user permissions per user per area](https://community.qfield.org/t/set-user-permissions-per-user-per-area/1378):
>
> Hi there, I was looking for a way to prevent users to update features outside a designated area. The idea is to use the cloud\_username variable as defining value. A cloud username is assigned to a certain area by a project manager so that user can only update features or add new features, etc. within that area. My first idea was to use the Geofencing option and apply a filter to the geofencing layer. However, that doesn’t work. QGIS can not handle variables in a filter statement. So, here is…

---

_[View the full topic](https://community.qfield.org/t/how-to-use-cloud-username-as-filter-for-layer/1374)._