---
title: 'Laravel: 4+ Ways to Set Auth ID in Controller'
source: 'https://youtube.com/watch?v=3xD6aRdRsBE'
video_id: '3xD6aRdRsBE'
date: 2026-08-12
duration_sec: 101
---

# Laravel: 4+ Ways to Set Auth ID in Controller

> Source: [Laravel: 4+ Ways to Set Auth ID in Controller](https://youtube.com/watch?v=3xD6aRdRsBE)

## Summary

This video presents four distinct methods for automatically setting the user ID from an authenticated user in Laravel, based on a Twitter poll. It compares approaches ranging from direct array manipulation to using Eloquent relationships and model events, highlighting the flexibility and potential pitfalls of each.

### Key Points

- **Option 1: Direct Array Addition** [00:02] — The most straightforward method involves adding the user ID directly to the validated data array within the controller.
- **Option 2: Splat Operator Merge** [00:14] — A similar approach uses the splat operator (...) to merge the validated array with an array containing the user ID, offering a more concise syntax.
- **Option 3: Eloquent Relationship** [00:28] — Utilizing a hasMany relationship (e.g., User hasMany Posts), you can create the post directly through the relationship, automatically setting the user ID.
- **Option 4: Model Event / Observer** [00:43] — Setting the user ID within the model's booted method or an Eloquent observer (e.g., creating event) centralizes the logic but requires checking if the auth user exists, as it may not be present in all contexts (e.g., queue jobs).
- **Poll Results and Community Alternatives** [01:11] — A Twitter poll showed 43% prefer the Eloquent relationship method. Community members suggested other approaches like explicitly setting properties, using Laravel Actions, or DTOs.

### Conclusion

Laravel offers multiple valid ways to set an authenticated user ID, each with trade-offs. The choice depends on context and preference, reflecting the framework's flexibility.

## Transcript

if you need to automatically set user ID from authenticated user? There are at least four ways I will show in this video. Option number one, probably the most straightforward. You have the validated array and then add another
item to that array. Option number two, similar but with different PHP syntax. Instead of adding the item to the array, you use dot dot dot universally called splat operator to merge those two arrays together. The third option is to use has
many relationship of eloquent which is user then it has many posts and then create the data that assumes that in the user model you have post has many option number four is to set that user ID not in the controller but in the model
itself or similar would be eloquent observer so booted method creating event and then you set that user ID. Keep in mind if you're doing that in the model or observer you need to double check if that session o even exists because
controllers usually check that in the routes or in the middleware and in this case it's global things. So that may come from a Q job from artisan command or somewhere else. So add if statement to check the o and I ask my audience
which option do they prefer. This is the tweet and the result of the poll is option C with eloquent relationship is chosen by 43%. And also people replied with their own options. So Will is explicitly setting
the properties. Punopal is creating Laravel actions and Humbberta is voting for DTO's. So this is one of those cases in Laravel that there are so many ways to write the same thing which is a blessing and a curse at the same time.
What do you think? Which way do you prefer?