# Granular user roles on registration

**URL:** <https://community.auth0.com/t/granular-user-roles-on-registration/106729>\
**Category:** Get Help\
**Tags:** sdks-quickstarts, auth0-php\
**Created:** [May 11, 2023, 10:34am UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729 "2023-05-11T10:34:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![1stevengrant](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/1stevengrant/32/47141_2.png) [@1stevengrant](https://community.auth0.com/u/1stevengrant)\
**Post date:** [May 11, 2023, 10:34am UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729/1 "2023-05-11T10:34:12Z")

</div>

Hi there,  
I have a customer who already use auth0 within their organisation.

I’m building a new app in Laravel and need to integrate against auth0.

I’ve seen the example app and I’ve managed to use this to integrate auth0 at a very base level of either authenticated or unauthenticated.

I want to introduce 2 roles of publisher and guest but given all authentication follows the same flow, I can’t see how to introduce this particular distinction.

Any ideas?

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [May 12, 2023, 6:56am UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729/2 "2023-05-12T06:56:31Z")

</div>

Hey there!

Based on what you describe what you are looking for potentially is our RBAC feature (role based access control). More about it here:

> **[Role-Based Access Control](https://auth0.com/docs/manage-users/access-control/rbac)**
>
> Understand the concept of role-based access control and how it applies in Auth0.

---

<div class="post-metadata">

**Author:** ![1stevengrant](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/1stevengrant/32/47141_2.png) [@1stevengrant](https://community.auth0.com/u/1stevengrant)\
**Post date:** [May 12, 2023, 7:08am UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729/3 "2023-05-12T07:08:59Z")

</div>

Thanks @konrad.sopala

It speaks to an API but there’s no clear indication of how to implement in a traditional server side application?

---

<div class="post-metadata">

**Author:** ![evansims](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/evansims/32/27011_2.png) [@evansims](https://community.auth0.com/u/evansims)\
**Post date:** [May 22, 2023, 5:54pm UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729/4 "2023-05-22T17:54:49Z")

</div>

Hi @1stevengrant 👋 Thanks for your question!

We just released 7.8 of the Laravel SDK last week, and revisited all our documentation in the process.

We now have some great examples of how RBAC works with the SDK, which leverages Laravel’s standard Gates and Policies APIs.

- Check out the “Access Control” section on the README at [GitHub - auth0/laravel-auth0: Laravel SDK for Auth0 Authentication and Management APIs.](https://github.com/auth0/laravel-auth0)
- Give the updated quickstart a look, which includes a demonstration of this at [GitHub - auth0-samples/laravel: Laravel 9 application demonstrating Auth0 integration, using the Auth0 Laravel SDK.](https://github.com/auth0-samples/laravel)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [June 5, 2023, 5:54pm UTC](https://community.auth0.com/t/granular-user-roles-on-registration/106729/5 "2023-06-05T17:54:56Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.