Who can see what in Lift Right?
For: Org admin
Four roles: Client, Caseworker, Org Admin and System Admin. Caseworkers see their own caseload. Administrators see the whole organization. Participants see only themselves. Administrators come in two authority tiers that see the same data but differ in what they may commit.
Lift Right has four working roles. Your role is set when you are invited and can be changed later by an administrator. What each role can read and change is enforced by the server and the database, not merely hidden from the menu.
The four roles
Role | Who it is | Sees |
|---|---|---|
Client | The person receiving services | Only their own record |
Caseworker | Carries a caseload | Only participants assigned to them |
Org Admin - Full | The organization’s administrator, full authority | Everything in their organization |
Org Admin - Program | An administrator of day-to-day operations | Everything in their organization |
System Admin | Lift Right staff | Every organization, including participant records, directly and with no approval step |
What each role can reach
Area | Client | Caseworker | Org Admin - Full | Org Admin - Program | System Admin |
|---|---|---|---|---|---|
Launch Pad | Yes | No | No | No | No |
Dashboard | No | Yes | Yes | Yes | Yes |
All Participants | No | Own caseload | Whole org | Whole org | Whole org |
Pathway (the workbench) | No | Own caseload | Whole org | Whole org | Whole org |
Programs | No | Yes | Yes, can create | Yes, view and work | Yes, with org switcher |
Referral Partners | No | Yes | Yes | Yes | Yes |
Marketplace (directory) | No | Redirected to Referral Partners | Yes | Yes | Yes |
Grants | No | No | Yes | No | Yes |
Grant reports | No | No | Yes | View and draft only | Yes |
Data and Insights | No | No | Yes | Yes | Yes |
Users and Roles | No | No | Yes | No | Yes |
Importer | No | No | Yes | Yes | Yes |
Service areas setup | No | No | Yes | Yes | Yes |
Org-wide thresholds | No | No | Yes | No | Yes |
Approvals (costs and service requests) | No | No | Yes | No | Yes |
Service catalog (pricing, funding splits) | No | No | Yes | No | Yes |
System Administration | No | No | No | No | Yes |
Business Operations | No | No | No | No | Yes |
The two administrator tiers
Lift Right has one administrator role with two authority tiers. Both tiers see the same participants, programs and reports. The difference is what each may commit on the organization’s behalf, and the pages that exist only for those decisions (Grants, Users & Roles, Approvals, Service catalog, Intake Questions) open for Org Admin - Full only.
Org Admin - Full can do everything below. This is the default for every administrator.
Org Admin - Program runs day-to-day operations and cannot do the actions below:
Withheld from Org Admin - Program | Why |
|---|---|
Create and edit grants | Contractual terms and money |
Finalise or export a funder report | Carries the organization’s signature. Viewing, drafting and saving stay open |
Set the eight org-wide flag thresholds (Baseline overdue after assignment, Intake draft stale, Review queue wait flag, Check-in gap (Needs You Today), Referral follow-up nudge, Auto-archive after exit, Auto-archive after no activity, Dismissed reminders kept for), the auto-approve limit for small costs, and the automatic sign-out time | Changes tempo for every program, not only theirs |
Invite, remove, or change staff | Personnel authority |
Create or archive programs | The organization’s structure |
Add or retire your own intake questions | One question is asked of everyone entering that part of the organization |
Approve, reject, or reverse costs and service requests; set pricing, funding splits, and standing exceptions; apply AI catalog drafts | Money leaves the building on the organization’s behalf |
Every one of these is enforced by the database or the server as well as by the screen. The Download PDF and Download CSV files of a funder report are built on the server, which refuses a program-tier administrator before any data is read. One exception remains: printing from the browser and the Excel export are built in the browser from data both tiers may read, so that rule lives on the screen only.
What does a program-level admin keep?
Everything operational: the program dashboard and every queue on it, intake review and assignment, caseload balancing, service-line approval within their own programs, referral partners and directory import, participant records and pathway work, bulk participant import, and every reporting view including drafts.
Do the two tiers see different data?
No. Breadth and authority are separate. A program-tier admin sees the same participants, programs and reports as a full-tier admin. The tier narrows what may be changed, and the pages that exist only to make those changes (Grants, Users & Roles, Approvals, Service catalog, Intake Questions) stay closed to the program tier.
Caseworker
Run and finish intakes
Work the participants an administrator assigns to them
Take baseline and follow-up readings
Work the Pathway: log services, set goals and steps, write case notes
Send referrals and record what came back
Request an additional service line for a participant, which an administrator approves
Client
Clients sign in to their own Launch Pad. They see their stage, their plan, and their pathway, and they can message their caseworker. They never see another participant’s record, and this is enforced at the database, not just in the interface.
Two-step verification
Optional for every role. Each person turns it on from their own Security page.
Which tier should each person have?
The labels describe access, not job titles, so they fit whatever your organization calls the roles. A common setup: the person who owns the funder relationship and the budget holds Org Admin - Full, and the person who runs programs day to day holds Org Admin - Program. If one person does both, Org Admin - Full is correct.
Change a tier any time in Users & Roles. Access changes on their next page load.
What Lift Right staff can see
A System Admin (a Lift Right employee) manages organizations, accounts, and setup. A System Admin can read and write every organization’s participant records directly, with no grant, expiry, or approval step.
Questions people ask
- What does a program-level admin keep?
- Everything operational: the program dashboard and every queue on it, intake review and assignment, caseload balancing, service-line approval within their own programs, referral partners and directory import, participant records and pathway work, bulk participant import, and every reporting view including drafts.
- Do the two tiers see different data?
- No. Breadth and authority are separate. A program-tier admin sees the same participants, programs and reports as a full-tier admin. The tier narrows what may be changed, and the pages that exist only to make those changes (Grants, Users & Roles, Approvals, Service catalog, Intake Questions) stay closed to the program tier.
- Which tier should each person have?
- The labels describe access, not job titles, so they fit whatever your organization calls the roles. A common setup: the person who owns the funder relationship and the budget holds Org Admin - Full, and the person who runs programs day to day holds Org Admin - Program. If one person does both, Org Admin - Full is correct.
Related
Last reviewed .