# Auto apply different permission profiles on project creation

**URL:** <https://community.sonarsource.com/t/auto-apply-different-permission-profiles-on-project-creation/69647>\
**Category:** SonarQube Server / Community Build\
**Created:** [August 11, 2022, 10:23am UTC](https://community.sonarsource.com/t/auto-apply-different-permission-profiles-on-project-creation/69647 "2022-08-11T10:23:22Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![openshift4](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/openshift4/32/33438_2.png) [@openshift4](https://community.sonarsource.com/u/openshift4)\
**Post date:** [August 11, 2022, 12:11pm UTC](https://community.sonarsource.com/t/auto-apply-different-permission-profiles-on-project-creation/69647/5 "2022-08-11T12:11:36Z")

</div>

True , but in the link that i shared, someone from SonarQube mentioned it explicitly :

> [@How to auto-apply a Permission template (with Project Key Pattern)](https://community.sonarsource.com/t/how-to-auto-apply-a-permission-template-with-project-key-pattern/23985/7):
>
> All above is still valid for cases when Name == Key. Which is our case. Please advise of this. Thanks.

" **Note that my first test didn’t work. I used a bash pattern (`com.sonar*` ) rather than a valid regular expression (`com.sonar.*` ).**"

However, if the expression was wrong, why then it worked when i made the second permission profile default?

I will try with " com.sonar.\* " and see what happens without setting the permission profile default for all projects.

---

_[View the full topic](https://community.sonarsource.com/t/auto-apply-different-permission-profiles-on-project-creation/69647)._