<p>Using the example in your comments, a simple solution would be to create a "Potential Jobs" Entry field and assign it to the Users field layout.</p>

<p>Whoever is doing the manually checking to find a match between tradesmen and clients would assign entries to that field that match the requirements.</p>

<p>The front-end user's dashboard would check that field to see if it has any entries in it and display them to the user.</p>

<p>You could probably get more elaborate with a Category field (that had Entry fields in it) if you want to group by more fine-grained details.</p>

CC BY-SA 3.0
2016-02-03T20:53:30.843Z
Ah okay, that could work. And in the instance that a user posted another job request, how would you show multiple instances?
JackO
CC BY-SA 3.0
2016-02-03T20:54:19.633Z
Maybe a Matrix field on the user with entry fields on that.
Brad Bell
CC BY-SA 3.0
2016-02-03T20:12:17.440Z
2016-02-03T20:12:17.440Z
Brad Bell
<p>Is it possible to show specific content or an entry for an individual user?</p>

<p>Here's what I'm trying to achieve: </p>

<p><em>A logged in user make a request to receive information on a particular service. An administrator then reviews the request and creates an entry specific for that user - whatever is contained within that entry is then displayed on the users dashboard for them to view.</em></p>

<p>How would I go about achieving this?</p>

<p>Thanks!</p>

CC BY-SA 3.0
2016-02-03T19:17:31.310Z
Is it truly unique content per user?  Or is it structured where the majority of the content is the same with some user specific variables swapped out?
Brad Bell
CC BY-SA 3.0
2016-02-03T19:23:16.613Z
The content that a user sees will be specific to them, but the content will already exist within the CMS and will be reused across users. Essentially, there will be a list of options written as entries in the CMS, when a user makes a request, what they ask for will determine what options they are presented with. Does that make sense?
JackO
CC BY-SA 3.0
2016-02-03T19:54:45.213Z
Hrm... kinda? How are you organizing the entries to know how to grab for a user? Via categories? Or via different sections? Basically once you have a user, what's the logic to grab entry A vs. entry B for them?
Brad Bell
CC BY-SA 3.0
2016-02-03T20:05:47.130Z
Here's an example - Say it was a site that allowed you to find a tradesman. The logged in user enters their requirements for a job - these preferences are then manually checked (so this doesn't need to be linked to anything). Once they've been checked, a list of relevant tradesmen would be displayed to them in their dashboard. I'm just trying to work out whether its feasible and if so, the best approach to take.
JackO
CC BY-SA 3.0
2016-02-03T20:12:30.920Z
Got it... that makes more sense.  Added an answer.
Brad Bell
<users>
User specific content
# User specific content

(Asked by: username_0 on 2016-02-03)

Is it possible to show specific content or an entry for an individual user?

Here's what I'm trying to achieve:

*A logged in user make a request to receive information on a particular service. An administrator then reviews the request and creates an entry specific for that user - whatever is contained within that entry is then displayed on the users dashboard for them to view.*

How would I go about achieving this?

Thanks!

**Tags:** users

> **Comments:**
> **username_1**: Is it truly unique content per user?  Or is it structured where the majority of the content is the same with some user specific variables swapped out?  
> **username_0**: The content that a user sees will be specific to them, but the content will already exist within the CMS and will be reused across users. Essentially, there will be a list of options written as entries in the CMS, when a user makes a request, what they ask for will determine what options they are presented with. Does that make sense?  
> **username_1**: Hrm... kinda? How are you organizing the entries to know how to grab for a user? Via categories? Or via different sections? Basically once you have a user, what's the logic to grab entry A vs. entry B for them?  
> **username_0**: Here's an example - Say it was a site that allowed you to find a tradesman. The logged in user enters their requirements for a job - these preferences are then manually checked (so this doesn't need to be linked to anything). Once they've been checked, a list of relevant tradesmen would be displayed to them in their dashboard. I'm just trying to work out whether its feasible and if so, the best approach to take.  
> **username_1**: Got it... that makes more sense.  Added an answer.  

---

## 1 answers

### Answer by username_1 on 2016-02-03. Score: 1 | Accepted answer

Using the example in your comments, a simple solution would be to create a "Potential Jobs" Entry field and assign it to the Users field layout.

Whoever is doing the manually checking to find a match between tradesmen and clients would assign entries to that field that match the requirements.

The front-end user's dashboard would check that field to see if it has any entries in it and display them to the user.

You could probably get more elaborate with a Category field (that had Entry fields in it) if you want to group by more fine-grained details.

> **Comments:**
> **username_0**: Ah okay, that could work. And in the instance that a user posted another job request, how would you show multiple instances?  
> **username_1**: Maybe a Matrix field on the user with entry fields on that.  

---

