The mobile app enforces the same role settings as the web app: a team member's Scope of support, Has PHI access, Has Legal access, and the level chosen for each module under Account Settings > Permissions > Custom Roles. This reference maps each setting to what it unlocks in the app. There are two fixed experiences that no dropdown changes: participants, who get their own records and whatever is shared with them, and Super Admins, who pass every module check. Everyone else, including the General Admin, Mentor, Supporter, and Support roles your account came with, is a saved combination of the same settings, so read their role in the editor against the tables below. Participants are labelled Clients, Students, Residents, or Explorers depending on your account type.
Who can do this, and where
Roles are edited on the web only, under Account Settings > Permissions > Custom Roles, by Super Admins and roles whose Account Settings module is Administrator. Nothing about permissions is changed from the app.
A person's own mobile access is the Mobile Access Enabled switch on the Access tab of their profile on the web. Team members start with it on; participants start with it off and it is switched on when they accept their app invitation.
Each team member picks their own tab bar button in the app: tap your photo on the Home screen to open Settings, then choose under Tab Bar Button.
Part I: Participants
A participant's app is fixed. The module dropdowns never apply to participants; only the switches below do.
Area | What they see and do |
Home | Their next event, today's routines, the Equip Card button, the Mood check-in when Mood Navigator is on for them, and tiles for Goals, Pathways, Routines, Documents, Notes, Assessments, and Announcements. The Assessments and Announcements tiles are not shown on family accounts; the Pathways tile appears only once they are enrolled in a pathway. |
Schedule | Their own calendar, plus events marked open to participant registration, which they can join for one occurrence or the whole series while places remain. |
Messages | Group chat for groups they belong to, when the account has Groups. |
Contacts | The account's contact directory, when the account has that feature. |
Goals | Only goals a team member has shared with them. They can log progress on those. |
Notes and documents | Their own notes, and notes and documents a team member shared with them. |
Assessments | Their own completed responses. |
Routines | Run, build, and delete their own routines. Routines built for them appear alongside. |
Mood Navigator | Check-ins and their own history, when the account has the feature and it is enabled for them. |
Profile | Their profile and Settings (appearance, security, notifications). There is no Tab Bar Button setting for participants. |
Switch | Effect |
Mobile access | Off until they accept their invitation, or until an administrator switches on Mobile Access Enabled on their Access tab. A discharge switches it off. Without it they cannot sign in. |
Account features | Groups, Goal Tracking, Pathways, Mood Navigator, Assessments, and the contact directory each remove their area when the account does not have them. |
Sharing, per record | Goals reach a participant only when a team member turns on sharing for that goal. Notes and documents reach them only when shared. There is no blanket switch. |
Part II: Team members and custom roles
Four gates decide what a team member sees. If an earlier gate is closed, the later ones never matter.
Gate | What it does |
1. Mobile access switch | Mobile Access Enabled on the person's Access tab, on by default for team members. Off means they cannot sign in. Their account status must also be Active. |
2. Account features | Modules tied to a feature your account does not have are absent everywhere: Groups and Messages, Forms, Assessments, Mood Navigator, Goals, Employment, and Pathways. Super Admins are not exempt from this gate. |
3. Scope of support | Restricted, Designated, or Full on the role. Decides which participants they can open; every "yes" below is bounded by it. |
4. Module levels | One dropdown per module. Decides what they can do within that scope. |
Scope of support
Setting | In the app |
Restricted - Only own records | Records they created or are directly connected to. The People tab shows nobody. |
Designated - Assigned participants | The participants assigned to them under Supported Participants, plus records shared with them. The usual choice for caseload work. |
Full - All account records | Every participant in the account. |
Emergency contacts, pinned documents, and the next event on a participant's Overview follow participant access: anyone who can open the participant sees them.
Sensitive data. Has PHI access and Has Legal access apply in the app as on the web: they gate the medical and legal sections of a participant's Overview, which hold the custom fields your account placed in the Medical Information and Legal Information sections. Values in those sections are not sent to the app for a role without the switch. Super Admins have both.
The tab bar. The bar is Home, People, a middle button, More, and Profile. People needs the Participants module at Supporter or above. The middle button is chosen per person under Settings > Tab Bar Button and offers only tools that person can reach: Messages (Groups feature and Groups at Supporter or above), Schedule (Calendar at Viewer or above), Announcements (Announcements at Viewer or above), Forms (Forms at Administrator), Assessments (Assessments at Administrator), Manage Categories (Account Settings at Administrator), and Manage Groups (Groups at Administrator). The default is Messages. If the chosen tool later becomes inaccessible the button falls back to the first accessible one, and with none accessible the middle button disappears. The More grid lists the same tools under the names Schedule, Messages, Forms, Assessments, Announcements, Categories, and Groups.
Home quick actions.Fill Form needs Forms at Administrator, Assessment needs Assessments at Administrator, Announcement needs Announcements at Administrator, and Schedule Event needs Calendar at Supporter or above.
Module guide
Each row gives the lowest level that turns the feature on. Not every module offers every level; the levels listed are the ones its dropdown shows.
Participants (None, Supporter, Administrator). This is the master switch: at None the People tab is gone and every participant-scoped feature below is unreachable.
Mobile feature | Minimum level |
People tab and participant profiles, within scope | Supporter |
Edit a participant's profile, assign supporters, assign groups | Administrator. Editing the profile also needs the Team module at Supporter or above, which is checked by the server. |
Announcements (None, Viewer, Administrator)
Mobile feature | Minimum level |
Read announcements, and see who has read one | Viewer. Read receipts list only people within the viewer's scope. |
Compose and send | Administrator |
Assessments (None, Viewer, Supporter, Administrator), needs the Assessments feature
Mobile feature | Minimum level |
Assessments section on a participant's profile | Viewer |
Start an assessment for a participant | Viewer. The server asks only whether you can reach the person; the module levels govern assessment templates, not responses. |
Assessments hub in More, the Assessment quick action, and the tab bar option | Administrator |
Calendar (None, Viewer, Supporter, Administrator)
Mobile feature | Minimum level |
Schedule and event details, within scope | Viewer |
Create events, including the Schedule Event quick action | Supporter |
Edit or delete an event | Only events you created are offered for editing or deleting. Editing needs Supporter. Deleting needs Administrator for a Full-scope role; a Designated-scope role can delete events created by itself or by its assigned participants. |
Sign yourself up for an event | Not governed by this module. Any team member can join an event that allows team member registration, for one occurrence or the series. |
Check yourself in and out | Not governed by this module. The app offers check-in and check-out for yourself only, while the event's window is open. Checking other attendees in and out is done on the web. |
Documents (None, Viewer, Supporter, Administrator)
Mobile feature | Minimum level |
Documents section on a participant's profile; pinned documents on the Overview | Viewer |
Upload documents for a participant | Supporter |
Delete a document | Per document. Each document carries its own access settings, and documents generated from a form response can never be deleted. |
Employment Tracking (None, Viewer, Administrator), needs the Employment Tracking feature
Mobile feature | Minimum level |
Employment section on a participant's profile | Viewer. Read only in the app; adding and editing stays on the web. |
Forms (None, Viewer, Supporter, Administrator), needs the Forms feature
Mobile feature | Minimum level |
Forms section on a participant's profile | Viewer |
Fill a form for a participant | Viewer. As with assessments, the levels govern form definitions, not responses. |
Forms hub in More, the Fill Form quick action, and the tab bar option | Administrator |
Goals (None, Viewer, Supporter, Administrator), needs the Goal Tracking feature
Mobile feature | Minimum level |
Goals section on a participant's profile | Viewer |
Log progress on a goal | Supporter. Creating and editing goals stays on the web. |
Share a goal with the participant | Supporter. The sharing switch on the goal decides whether it appears in the participant's own app. |
Groups (None, Supporter, Administrator), needs the Groups feature
Mobile feature | Minimum level |
Messages and group chat, for groups you belong to | Supporter. At None the Messages tab and tool are hidden. |
Manage groups, and the Groups tile on a participant's profile | Administrator |
Mood Navigator (None, Viewer, Administrator), needs the Mood Navigator feature
Mobile feature | Minimum level |
Latest-mood chip on a participant's profile | Administrator. Viewer grants only the organisation-level view, which has no mobile surface. The supporter role your account came with holds a non-standard extra that shows this chip; saving that role in the editor removes it (see below). |
Notes (None, Viewer, Supporter, Administrator)
Mobile feature | Minimum level |
Notes section on a participant's profile | Viewer |
Write notes | Supporter |
Edit or delete a note | Per note. Each note carries its own access settings, set on the note. A note written in the app is saved without those settings, so it may not appear for custom roles, including the author's, until an administrator edits its access on the web. |
Pathways (None, Viewer, Supporter, Administrator), needs the Pathways feature
Mobile feature | Minimum level |
Pathways on a participant's profile and active pathways on the Overview | Viewer. Read only in the app, so Viewer and Supporter behave the same; step completion, enrollment, and discharge stay on the web. |
Routines (None, Viewer, Supporter, Administrator)
Mobile feature | Minimum level |
Routines section on a participant's profile | Viewer |
Build, edit, and delete routines for a participant | Supporter. Unusually, the Supporter level of this module includes delete. Participants can always delete their own routines. |
Account Settings (None, Viewer, Administrator)
Mobile feature | Minimum level |
Manage Categories in More, and the tab bar option | Administrator |
No mobile surface. Team, Employers, Reports, Pathway Authorizations, Pathway Authorization Invoices, and Time have no screens in the app; their levels matter only on the web. The Team module's edit permission still matters for editing a participant's profile from the app, as noted under Participants.
Two things that catch people out
A brand-new role cannot see notes and documents that already exist. Notes and documents carry their own access settings, written when the record is created for the roles that exist at that moment. A role you create today is on none of them, so it opens Documents or Notes and finds them empty no matter how high you set those modules. Only records created after the role exists include it, and only if the role's module level admits it. Plan for this before moving people onto a new role.
Saving a role rewrites every module to the level shown in its dropdown. The supporter role your account came with holds a few abilities the dropdowns cannot express. The editor shows the closest level, and saving writes exactly that level back. For the default supporter role that means Mood Navigator and Pathway Authorization Invoices show as None and Employment Tracking shows as Viewer, so saving it for any reason, even renaming it, removes the mood chip and the other extras. If a role works as you want, leave it alone; Reset to Default restores the built-in set.
Part III: Super Admins
Super Admins and Equip Admins pass every module check automatically, at Full scope, with PHI and Legal access.
Area | What a Super Admin gets |
People | The entire roster, every section of every profile, profile editing, supporter and group assignment. |
Quick actions | Fill Form, Assessment, Announcement, and Schedule Event. |
More and tab bar | Every tool and every tab bar option: Messages, Schedule, Announcements, Forms, Assessments, Manage Categories, and Manage Groups. |
Sensitive data | The medical and legal sections of every Overview, without any switch. |
What still applies to a Super Admin:
Limit | Why |
Mobile access switch | A Super Admin with Mobile Access Enabled off cannot sign in, like anyone else. |
Account features | Features the account does not have stay hidden. Bypassing module levels does not add features. |
Per-record access on notes and documents | In the app, Delete appears on a note or document only when that record's access settings include the Super Admin role, and form-generated documents are never deletable in the app. On the web a Super Admin can delete any of them. |
Ten-minute spot check, per role
Open Account Settings > Permissions > Custom Roles and pick a role people actually hold.
Confirm Scope of support matches the job: Designated for caseload work, Full only when someone needs the whole roster.
Confirm Participants is Supporter or Administrator. It is the master switch.
Walk each module dropdown against the tables above, asking whether the role should see it, do it, or manage it.
Check Has PHI access and Has Legal access are on only where needed.
For anyone who should not use the app at all, switch off Mobile Access Enabled on their Access tab rather than hollowing out the role.
Before creating a new role, check whether an existing one already fits: a new role starts with no access to notes and documents that already exist, and no report access.
Limits and what the errors mean
A team member cannot sign in to the app. Their Mobile Access Enabled switch is off, or their status is Inactive. Both are on the Access tab of their profile.
A participant cannot sign in. They have not accepted their invitation, or their mobile access was switched off, for example by a discharge. Resend the invite or switch Mobile Access Enabled back on.
The People tab is empty. The role's scope is Restricted, or Designated with no participants assigned, or the Participants module is None.
A section tile is missing from a participant's profile. That module is None on the role, or the account does not have the feature.
Notes or Documents open but show nothing. The role was created after those records; only records created since the role existed, and shared with it, appear.
A note written in the app is not in the Notes list. Notes created in the app are saved without per-role access settings. An administrator can open the note on the web and set its access so the right roles see it.
The middle tab bar button changed or disappeared. The chosen tool became inaccessible after a role change; the app falls back to the first tool the person can reach, or removes the button when there is none.
A Viewer can start an assessment or fill a form but cannot edit the template. That is by design: responses need only access to the participant, while templates follow the module level.
Levels reflect the standard options each module offers. Roles customised before this guide existed may hold non-standard combinations; Reset to Default restores the standard set for the role's type.
Account-type defaults differ: the General Admin role your account came with has PHI and Legal on everywhere; the supporter role has them on only in CRP accounts, which also give supporters full Routines and Employers access. Family accounts set most program modules to None.
Verified against the Equip code on September 17, 2026, not against a live account. Anything a screen does that is not listed here has not been checked.
FAQ
Why can a supporter see a participant on the web but not in the app?
The app applies the same scope of support and module levels as the web, so check the person's Mobile Access Enabled switch first, then the Participants module on their role. If the participant is missing from the People tab only, the role's scope is Designated and the participant is not assigned to them.
Which level lets a supporter write notes and upload documents in the app?
Supporter on Notes and Supporter on Documents. Viewer opens the sections read only. Deleting is decided per note or document by that record's own access settings, not by the module level.
Why does a new role see no notes or documents?
Notes and documents carry access settings written for the roles that existed when they were created. A new role is on none of them. Records created after the role exists, and shared with it, will appear; older ones need their access settings edited to add the role.
Can a team member fill a form or run an assessment for a participant at Viewer level?
Yes. Submitting a response only requires access to the participant, so the Forms and Assessments sections on a profile offer the button at Viewer. The Forms and Assessments hubs, quick actions, and tab bar options need Administrator.
How do I give someone the Assessments hub in the app?
Set the Assessments module to Administrator on their role. That unlocks the hub in More, the Assessment quick action on Home, and the Assessments option under Tab Bar Button. Supporter and Viewer only reach assessments from a participant's profile.
Why did the mood chip disappear from participant profiles after I edited our supporter role?
The default supporter role holds a non-standard Mood Navigator extra that the editor cannot show, so it displays as None and saving the role wrote None back. Use Reset to Default on the role to restore it, and avoid re-saving that role afterwards.
Who can check participants in and out of an event in the app?
Nobody: the app lets each person check themselves in and out while the event's window is open. Checking other attendees in and out is done on the web, by anyone whose Team module is Supporter or Administrator, for attendees within their scope.
Can I stop one person using the app without changing their role?
Yes. Open their profile on the web, Edit Profile & Settings, the Access tab, and switch off Mobile Access Enabled. Their role and web access are unchanged, and you can sign them out of the app from the same card.
Related
Set what each role can see and do
What do the role names mean?
Control which reports each role can run
Add a participant and invite them to the mobile app
