Staff Notifications in Full Fabric are automated alerts that keep staff members informed about important activities, updates, and events within the platform. They help staff stay on top of relevant information, take timely action when needed, and manage their daily responsibilities more efficiently, ensuring that important updates and tasks are not overlooked.
The three ways staff hear about things
Full Fabric tells staff what is happening in three ways. Most questions come down to knowing which one you are looking at.
Channel | What it looks like | Typical examples |
Bell and Inbox | A bell with an unread count in the top bar, and a list of cards in the Inbox | A new application, a form submission, a task assigned to you |
Emails | Messages to your mailbox from Full Fabric | Task assigned, task completed, a finished export, a sync problem with your mailbox |
Notices from administrators | A coloured bar at the top of every page, or emails triggered by workflows an administrator built | A maintenance message to all staff, an email to the owner when an application is submitted |
Good to know
The Inbox is not an email client. It collects activity from across Full Fabric into one list of cards and links you to the record behind each one.
The bell and the Inbox
The notification bell
The bell sits in the top bar, to the left of the Settings gear. It shows how many notifications you have not read yet. Select it to see the latest ones.
The bell dropdown. When nothing is waiting you see "You're all caught up". "View all in inbox" opens the Inbox.
Mark all as read clears the unread count.
View all in inbox takes you to the full list.
Only some cards alert you through the bell. "Who sees a card, and who is alerted" later in this section explains which, and why.
The Inbox
Select Inbox in the left sidebar. The page opens on the All tab, with cards grouped by day. At the top right you find Customise inbox, Create task and a More actions menu with Pin to homepage.
The tabs
Each tab shows one kind of card. You only see tabs for records your role can access.
Tab | A card appears when |
Emails | An email is sent to or received from a profile you are involved with |
Tasks | A task is assigned to you, or to someone you follow |
Applications | An application is started or submitted |
Forms | A form is submitted |
Events | Someone responds to an event |
Offers | An offer is made, accepted or declined |
Lifecycle | A profile moves from one lifecycle state to another |
Documents | An applicant uploads documents to an application |
Evaluations | An evaluation is assigned to you or submitted |
Workflow messages | A workflow sends you an in-app message (see section 5). The tab was empty on our demonstration site |
Archived | Cards you or a colleague archived |
Note
If a tab you expect is missing, your role may not include access to that record type. If Evaluations cards never appear for anyone, ask your administrator whether evaluation cards are switched on for your institution.
Reading a card
Every card follows the same layout, so you can scan quickly.
Application cards: a "started this application" card and a "submitted this application" card.
A coloured label tells you the type: Application, Event, Form, Email or Task.
The title is the template, form or event name.
A sentence says what happened and when, for example "submitted this application. Created 23 hours ago."
Form and event cards also list the answers that were submitted.
A checkbox on the left lets you select several cards.
On the right, Archive and a main action button take you onward: View application, View submission, View email or Complete task.
The three-dot menu on a card offers Create task, so you can turn a card into a follow-up and link it to the right profile.
Who sees a card, and who is alerted
A card has two kinds of audience. This is the most useful idea for explaining notifications to customers.
Followers can see the card in their Inbox.
Recipients are followers who are also alerted: the bell counts the card as unread for them.
For most cards the recipients are the owner of the person's journey (for example the admissions officer who owns the applicant's class) and staff who follow that profile.
Card | Seen in the Inbox by | Alerted through the bell |
Emails | Staff who are recipients of the email, and staff who follow those profiles | No one |
Tasks | The assignee, and staff following the assignee or the task's profile | The assignee when a task is newly assigned to them by someone else |
Applications, Forms, Events | Staff with access to that record type | The journey owner and staff following the profile |
Offers, Lifecycle, Documents | The journey owner and staff following the profile | The same people |
Evaluations | The assigned evaluator; for submitted evaluations, the journey owner, followers and whoever assigned it | The same people |
These rules apply to every card:
You are never alerted about something you did yourself.
Staff whose access scope excludes the profile get nothing about it.
If a person's journey has no owner, only followers are alerted.
Several document uploads close together are grouped onto one card, with a growing count.
Good to know
Unread state is personal, so reading a notification does not mark it as read for a colleague. Archiving is shared, so archiving a card clears it for everyone who sees it.
Archive and bring cards back
Select Archive on a card, or tick several cards and archive them together.
Open the Archived tab to find cards you archived earlier.
Restore a card from the Archived tab if you need it back.
Completing a task moves its card to the Archived tab as well.
Choose what you see with Customise inbox
Customise inbox changes your own Inbox and bell. It never changes what colleagues see.
In the Inbox, select Customise inbox.
Under Tabs, switch off any card type you do not want. Turned-off tabs are hidden from the Inbox, the All tab and the bell.
Under Filter, select Add Filter + to show notifications and tasks only for matching applicants, across every tab.
Select Save changes. Changes only persist once you save them. Cancel discards them.
Tip
If a staff member says "I never see offers", check Customise inbox first. A switched-off tab hides cards everywhere, including the bell.
Other places staff see activity
The Home page has Tasks and Emails tabs with counts. From the Inbox, More actions › Pin to homepage puts the Inbox on your Home page.
Tasks and task emails
Tasks are the notification type with the most moving parts, because they use the bell, the Inbox and email together.
Create a task
In the Inbox, select Create task. You can also open the three-dot menu on any card and choose Create task to link the task to that profile.
Choose a Category (the default is Task).
Enter a Title and a Due date. Both are required.
Optionally use Link to to attach a profile, so the assignee knows what the task is about.
Choose who to Assign to, then select Create task.
What the assignee gets
A task card in their Inbox, and a bell alert if someone else assigned it.
An email telling them the task was assigned, unless they assigned it to themselves or switched that email off.
Further bell alerts when the task is due today and when it is overdue. These are sent once each, from 7am in your institution's time zone. A task assigned today is not flagged as due or overdue until the next day.
Changing the due date restarts those due and overdue alerts. A card the assignee archived stays archived.
See and filter tasks
In the Inbox, open the Tasks tab. The dropdown at the top has three views.
Assigned to me is the default.
Created by me shows tasks you gave to others.
All tasks shows everything you are allowed to see. Tasks are grouped by due date, with overdue tasks first.
Select Complete task when you finish. Completing a task archives its card.
Your task email switches
Each staff member controls two task emails.
Select your name at the bottom left, then Profile Settings.
If asked, confirm your credentials again. This is a security check.
Open the Notifications tab.
Use the two switches: Receive notification when task is assigned to me and Receive notification when task I created is completed by someone else.
Good to know
These are the only two notification switches in Profile settings. There are no frequency or digest options, and no switches for other notification types.
The task completed email goes to the task's creator and assignee, and never to the person who completed it.
The daily task reminder
Active staff with tasks to report receive a "Your tasks" reminder email every weekday morning (Monday to Friday) at 6am UTC. It is the same time for every institution and is not sent at weekends. It covers tasks due today, due tomorrow and overdue, plus tasks you created that were completed in the last 3 days. If there is nothing to report, no email is sent. It cannot be customised or switched off by users or administrators.
Note
The Tasks article in the Help Center describes the reminder as daily. Weekdays only is the current behaviour.
Tip
If a customer asks how to stop the daily reminder, tell them it is not configurable today. The two task emails in Profile settings can be switched off, but the daily reminder cannot.
Emails staff receive from the system
Some notification emails are built-in system emails whose wording administrators can edit. Others have fixed wording and are described in section 6.
Where administrators find them
Select the Settings gear at the top right.
Choose System email templates.
Search by name. The table has the columns Name, Subject and Type (Plain or Visual builder).
Note
The list holds about sixty templates and mixes staff emails with emails to candidates, referees, payers and students. The list is fixed, so templates cannot be added or deleted. Check who a template is for before you edit it.
Emails that go to staff
Template | Sent when | Who receives it |
Application submission notification | An application is submitted | The owner of the applicant's role in the related class. No owner means no email. |
Application start notification | An application is started | The owner, where your institution's workflows use this email |
Form submission | A form is submitted | The staff member chosen in the form's workflow. Replies go to the person who submitted. |
Event registration staff notification | Someone registers for an event | The staff member chosen in the event's workflow |
IMAP account deactivated | Your email sync has expired or been disconnected | The staff member whose mailbox sync stopped |
Scheduled campaign pre-dispatch notification for campaign creator | Shortly before a scheduled campaign goes out | The person who scheduled the campaign |
Error while dispatching campaign | A campaign failed to send | The person who sent or scheduled it |
Application file download, Application file download error | A requested download of application files is ready or failed | The staff member who requested it |
Sign up instructions for staff, for internal admin, for lecturer | An account is created for someone | The new user. This is an invitation, not an alert. |
The template itself does not hold a recipient address. Who receives the email is decided by whatever triggers it, such as a workflow or the person who started the action.
Workflow-driven notifications
Workflows are automations that run when something happens. Two kinds matter here.
Built-in system workflows
Full Fabric ships with system workflows that create Inbox cards, for example for evaluations, offers, document uploads and lifecycle changes. This is why cards appear without anyone setting anything up.
Administrators can see them under Workflows in the Settings menu, marked System. The Actions column shows text such as "Create evaluation inbox card", "Create document inbox card", "Create lifecycle inbox card" and "Create offer inbox card".
System workflows in the Workflows list. Evaluation rows sit just above the ones shown.
Good to know
System workflows cannot be opened or edited from this list. If a customer wants fewer cards for one person, use Customise inbox. There is no institution-wide switch to turn off a card type.
Workflows your administrators build
Administrators can add steps that tell staff about an event. According to the Help Center, the steps include:
Send email to staff, where you choose an email template and a subject.
A form submission notification to staff, and an event registration notification to staff. These send a ready-made alert.
Send in-app message (listed as "Send in-app message to staff" in the Help Center). It puts a card in the Inbox and alerts the recipients through the bell, with no email involved.
You find these in the Automation area of the relevant form, event, application template, evaluation template or lifecycle workflow. For the email steps, the person you pick must be a staff or admin user. A recipient who is not staff does not receive the email.
In-app messages from workflows
An in-app message appears on the Workflow messages tab of the Inbox. The administrator writes the title and an optional body, and can use merge tags such as the person's name. The card opens the person's profile, or their application.
The administrator chooses who receives it: the journey owner, specific staff members, or everyone holding a staff role.
Only staff who can open that profile receive it.
A recipient gets the same message for the same person at most once a day.
If nobody can be reached, the step is skipped.
Tip
For evaluations, a common setup is a workflow that emails staff when an evaluator submits. See the evaluation workflows article in Related articles.
Notices set by administrators
The staff notice bar
An administrator can show a coloured bar at the top of every back-office page. Use it for maintenance windows or announcements that every staff member must see.
Open the Settings gear › General settings › Institution › Staff notice.
Turn on Enabled.
Type the Message. Optionally switch on Centred.
Pick a Style: Red, Yellow, Purple or Green.
Check the Preview, then select Save.
Emails about your own jobs and settings
Some emails are sent automatically to the person who started an action or who owns a setting. Their wording is fixed and they have no switch. Depending on what your institution uses, staff may receive:
Sent when | Who receives it | |
Export ready or failed | A background export, such as a profile list or application export, finishes or fails | The person who ran the export |
Import started or finished | A profile import starts or finishes | The person who uploaded the file |
API token expiry | An API token is about to expire, or has expired | The person who created the token |
Email connection problems | A personal or institution email connection stops authenticating | The person whose connection failed, or whoever last updated the institution's setting |
Tip
If a staff member closes the window while an export runs, the email is how they get the file. Ask them to check their mailbox and spam folder.
Who sees what
Two people at the same institution can see very different notifications. This table covers what makes the difference.
Factor | Effect |
Role permissions | A tab, and the cards in it, appear only for staff whose role can see that record type. |
Data access scope | Staff do not get cards, alerts or emails about profiles outside their scope. |
Journey owner | The owner of a person's journey is alerted about most activity. With no owner, only followers are alerted and the submission email to the owner is not sent. |
Following a profile | Staff who follow a profile are alerted about its activity. |
Customise inbox | Turned-off tabs and filters hide cards in the Inbox and the bell for that person. |
Your own actions | You are never alerted about something you did. |
Active staff | Daily reminders go only to active staff members. |
Why didn't I get notified?
Work through this list in order. Most cases end in the first four steps.
Did you cause it yourself? You are never alerted about your own actions, including tasks you assign to yourself
Can your role see that record type? If the tab is missing from your Inbox, you will not get the card.
Is the profile inside your data access scope? If not, nothing about it reaches you.
Are you the journey owner or a follower? Others may see the card but are not alerted through the bell. Email cards never use the bell
Did you switch the tab off or add a filter in Customise inbox? Both hide cards in the bell too
Does the person have an owner? With no owner, the submission email is not sent.
For task emails, check Profile settings › Notifications. If a switch is off, that email is not sent.
For workflow emails, was the recipient a staff user? A recipient who is not staff is skipped.
Check spam and the address the email goes to. Then ask an administrator to check the template and workflow.
Common situations
Scenario | Most likely reason |
"I assigned myself a task and got no email." | Self-assigned tasks do not send an email or a bell alert. |
"A colleague archived it and now it has gone from my Inbox." | Archiving is shared. Check the Archived tab. |
"The daily reminder did not arrive." | It is sent on weekdays only, at 6am UTC, only when there is something to report, and only to active staff. |
"I see the application card but the bell stayed quiet." | The bell alerts the journey owner and followers. Everyone else only sees the card. |
"My emails stopped syncing." | Look for the "IMAP account deactivated" email, then update IMAP preferences in Profile settings. |
FAQs
Can I choose which notifications I get by email and which in the app?
Can I choose which notifications I get by email and which in the app?
Not for each type of event. Your own controls are the two task email switches in Profile settings, Customise inbox, and the profiles you follow.
Can I turn off the daily task reminder?
Can I turn off the daily task reminder?
No. It is not configurable by users or administrators.
Does the bell show everything in the Inbox?
Does the bell show everything in the Inbox?
No. The Inbox lists every card you can see, and the bell alerts you only to cards where you are a recipient. Email cards do not use the bell.
Why do two colleagues see different cards?
Why do two colleagues see different cards?
Their roles, access scopes, ownership and Customise inbox settings differ.
If I archive a card, does it disappear for my colleagues?
If I archive a card, does it disappear for my colleagues?
Yes. Archiving is shared. Read and unread state is personal.
Does completing a task remove it for everyone?
Does completing a task remove it for everyone?
Completing a task archives its card. Deleting a task is permanent.
Who receives an email when an application is submitted?
Who receives an email when an application is submitted?
The owner of the applicant's role in the related class. If there is no owner, no one receives it.
Can I edit the wording of staff notification emails?
Can I edit the wording of staff notification emails?
The system emails listed in section 4 can be edited under Settings › System email templates. The emails in section 6 have fixed wording.
What if I cannot see the Inbox?
What if I cannot see the Inbox?
The Inbox needs to be switched on for the institution and included in your role. Ask an administrator.
What is the staff notice for?
What is the staff notice for?
It shows a coloured bar at the top of every back-office page. Use it for announcements to all staff.
Quick reference
Notification | Trigger | Who gets it | Where it is configured |
Bell alert and Inbox card | Application, form, event, offer, lifecycle, document or evaluation activity | Owner and followers (bell); staff with access (Inbox) | Your own Customise inbox; ownership on the profile |
Task assigned card and email | Someone assigns you a task | The assignee | Profile settings › Notifications (email only) |
Task completed email | Someone else completes a task you created | Creator and assignee, not the person who completed it | Profile settings › Notifications |
Task due or overdue alert | A task is due today or overdue | The assignee | Not configurable |
Daily task reminder | Every weekday at 6am UTC, when there is something to report | Active staff | Not configurable |
System emails to staff | See the table in section 4 | Depends on the trigger | Settings › System email templates |
Workflow emails and in-app messages to staff | A step in a workflow runs | The staff chosen in the step (for in-app messages, also by role or journey owner) | The Automation area of the form, event or template |
Staff notice bar | An administrator publishes it | All staff | Settings › General settings › Institution › Staff notice |
Export, import and token emails | The job finishes, fails or the token nears expiry | The person who ran it or created it |
|















