What staff see (and what they don't)
Short version: when staff open the wellbeing dashboard they see the cohort picture, not names. But the staff who support your cohort can also open a closer view that shows individual check-in responses, including yours, so they can reach out if you're struggling. Your private workspace is never visible to anyone, and your data never leaves your institution.
Every surface a staff member can see is listed below, so you can check it rather than take it on faith.
At a glance
| What | Who can see it |
|---|---|
| Your weekly check-in answer | The cohort total on the dashboard; your individual response to your university's support staff (logged) |
| Your daily check-in answer | The cohort total on the dashboard. Not tied to your name anywhere |
| The note you write with a daily check-in | Only you. No staff view shows it |
| A help request you raise | The staff member who handles it |
| Your tasks, notes, focus sessions | Only you |
| The wellbeing reads you open | Only you |
Your weekly check-in
When you answer the weekly check-in, your response does two things. It feeds the cohort-level viewA view of the whole group's responses combined into totals, with no individual answers shown. staff read on the Pulse dashboard: the share of a group thriving or struggling, not a list of names. And it is visible as an individual response to the staff at your university who support your cohort, so they can follow up with students who look like they are having a hard time.
On the aggregate dashboards, small groups are protected: the breakdown stays hidden until at least five students sit behind it, so a percentage can't be pointed at one person.
The individual view exists so a struggling check-in becomes a real follow-up. It is limited to support staff at your university: not other students, not another institution. And each time your record is opened it is written to a tamper-resistant audit log, so access can be reviewed. It is there to support you, not to grade you: a check-in is never a mark against you.
Your daily check-in
Separate from the weekly one, and completely optional. On Wellbeing you can note how a day went, as often as once a day, and look back over your last four weeks. Nothing asks you to. It is there for people who want to keep a record of how they are travelling and see the shape of it over time.
It is treated differently from the weekly check-in, on purpose:
- The face you pick feeds the cohort total staff read on the dashboard, the same aggregate as above: the share of a group thriving or struggling, never a list of names, and hidden altogether until at least five students sit behind it. There is no individual view of it for staff, unlike the weekly check-in.
- Anything you type is yours. It is stored so you can read it back, and one single place in the whole system can return it: your own history, to you. No staff screen, report or export includes it. If you want someone to see what you have written, you send it yourself through Help, and then it is a help request like any other.
If you write something that sounds like you are having a really hard time, the app will put support options on the screen straight away. That happens on your device, and it sends nothing anywhere. Whether to reach out stays your call.
Your help requests
When you raise a help request, a staff member reads it. That is the whole point: you wanted a person to know. They see what you wrote, the category you picked, and how urgent it looks, so the right person can respond, usually within a day.
If what you write suggests you are in danger, the request is flagged so the team treats it as urgent and reaches out quickly. The crisis path explains exactly what happens then, and the immediate support you are shown in the moment.
Your private workspace
The Workspace (your tasks, notes, focus-timer sessions, custom tags) is yours alone. Staff cannot see any of it. Neither can other students.
The wellbeing reads are private in the same way. Which articles you open, and how long you spend, is not reported to anyone. Read whatever is useful without worrying that it shows up on a list somewhere.
Common questions
Can a staff member look up my individual check-in history?
Yes. The staff who support your cohort can open your profile and see your recent check-in responses, so they can follow up if you might need support. It's limited to your institution's support staff and every access is logged. The dashboard they work from by default is the cohort aggregate, not a per-student list.
Does my university's IT department see my answers?
Your data is isolated to your institution and can't be read across tenants. General IT staff don't have a window into your check-ins; access to individual responses is limited to staff with a support role in First Six, and it is logged.
If I write something in a private note, could it ever be read?
No. That is true of both kinds of note. Notes and tasks in your Workspace are visible only to you, and so is anything you write alongside a daily check-in: one single place in the system can return those words, and it is your own history, to you. Neither is part of anything staff can open, export or report on.
What is the difference between the weekly and the daily check-in?
The weekly one is the question your cohort answers once a week during the six weeks, and your support team can see your individual answer so they can follow up. The daily one is optional, you can use it as often as once a day for as long as you like, and staff only ever see it as a cohort total, never as your answer. The daily one is also the only one you can write words against, and those words stay with you.
In one line
Staff read the cohort on the dashboard; the support team at your university can also see your individual WEEKLY responses, with every access logged, so they can reach out. Your daily check-ins reach them only as a cohort total, and the words you write with one reach them not at all. Help requests are personal by your choice. Everything in your Workspace stays with you.
Related
The fastest answer is usually one question away.