SeniorverseSeniorverse Help
⌘K
Reference

Permissions Reference

AllUpdated Jul 26, 2026

Overview

This reference lists the permission scopes that control what users can see and do in Seniorverse, grouped by module. Administrators assign permissions to each user per center from Center > Users. Use this reference to understand what each scope grants, to plan a user's access, and to troubleshoot why someone can or cannot reach a feature.

How Permissions Work

Seniorverse does not use per-feature "None / View / Edit / Full" dropdowns. Instead, each user is granted a set of scopes — a user either has a scope or does not. Where an action has different levels, those are separate scopes and the level is part of the scope name (for example, :View, :Edit, :Invite, :Delete, :Admin).

Access is resolved in three tiers:

Tier What it grants
Full Access (account level) A user marked with full access can do everything, in every module. This is the highest level, typically reserved for owners and top administrators.
Per-module full access ({Module}:FullAccess) Grants everything within a single module. Each module also has a {Module}:Limited grant that makes the module accessible; the module appears in a user's module card when they have either FullAccess or Limited for it.
Granular scopes Individual capabilities, listed in the tables below. A user sees a page or feature only if they hold the required scope (or a higher tier above).

A user with no scopes for a module cannot open it, and pages within a module are hidden when the user lacks the scope for that page.

The six modules are: Care, Reception, Outreach, Reports, Center, and Billing. Each supports {Module}:FullAccess and {Module}:Limited (for example, Care:FullAccess, Billing:Limited).

Note on scope names: Scope names are literal strings. Most Care scopes begin with Care:, but a few standalone Care scopes do not (for example, CareGoals:View, CareIncidents:View). The Outreach module's granular scopes use the historical Orm: prefix even though the module is named Outreach.


Care Module — Pages

Scope What it controls
Care:FullAccess Full access to everything in the Care module.
Care:Limited Makes the Care module accessible.
Care:Attendance Allows viewing and making changes to attendance (add, check-in/out, cancel, edit).
Care:Attendance:View Allows viewing the attendance page without making changes.
Care:Meals Access to the Meals page.
Care:Activities Access to the Activities page.
Care:Planner Access to the Planner (calendar) page.
Care:Members Access to the Members list.
Care:Tasks:View View the Tasks page.
Care:Tasks:Review Review care tasks.
Care:AdminTasks:View View administrative tasks.
Care:TaskDetail:Admin Administrative control over task detail.
Care:BenefitTypesPage:View View the Benefit Types page.
CareServices:View View Services.
CareGoals:View View the Service Plans page.
CareAssessmentTemplatesPage:View View the Form Templates page.
CareIncidents:View View the Incidents page.
Care:Deleted:View View the Deleted page (recently removed Care records).

Care Module — Members and Administration

Scope What it controls
Care:MemberEdit Open and edit a member's profile.
Care:MemberEdit:Status:Edit Allows changing a member's status.
Care:Member:Admin Allows deleting members. Members with attendance on record can never be deleted.
Care:MemberEdit:Notes:Admin Allows editing notes created by other users. Users can always edit their own notes.

Member profile sections

These scopes control which sections of a member's profile a user can see or edit. A :View scope grants read access to that section; a :Edit scope grants the ability to change it.

Scope What it controls
Care:MemberEdit:General Information:View View the General Information section.
Care:MemberEdit:Demographics:View View the Demographics section.
Care:MemberEdit:Demographics:Edit Edit the Demographics section.
Care:MemberEdit:Contact Information:View View the Contact Information section.
Care:MemberEdit:Contact Information:Edit Edit the Contact Information section.
Care:MemberEdit:Contacts:View View the member's Contacts.
Care:MemberEdit:Background:View View the Background section.
Care:MemberEdit:Custom Fields:View View Custom Fields.
Care:MemberEdit:Health Insurance:View View the Health Insurance section.
Care:MemberEdit:Benefits:View View the member's Benefits.
Care:MemberEdit:Transportation:View View the Transportation section.
Care:MemberEdit:Wellness:Edit Edit the Wellness section.
Care:MemberEdit:Diagnoses & Conditions:View View Diagnoses & Conditions.
Care:MemberEdit:Allergies:View View Allergies.
Care:MemberEdit:Vitals:View View Vitals.
Care:MemberEdit:Nurse Notes:View View Nurse Notes.
Care:MemberEdit:Advance Directives:View View Advance Directives.
Care:MemberEdit:Medications:View View Medications.
Care:MemberEdit:Profile Only Medications:View View profile-only Medications.
Care:MemberEdit:MAR:View View the Medication Administration Record (MAR).
Care:MemberEdit:MAR:Edit Record on the Medication Administration Record (MAR).
Care:MemberEdit:Task Log:View View the member's Task Log.
Care:MemberEdit:Assessments:View View Assessments.
Care:MemberEdit:Forms:View View Forms.
Care:MemberEdit:Service Plans:View View Service Plans.
Care:MemberEdit:Notes:View View member Notes.
Care:MemberEdit:Attendance:View View the member's Attendance.
Care:MemberEdit:Meals:View View the member's Meals.
Care:MemberEdit:Activities:View View the member's Activities.
Care:MemberEdit:Incidents:View View the member's Incidents.
Care:MemberEdit:Facial Recognition:View View Facial Recognition.

Reception Module

Scope What it controls
Reception:FullAccess Full access to the Reception module.
Reception:Limited Makes the Reception module accessible.
Reception:View View and use the Reception check-in interface.

Outreach Module

Granular Outreach scopes use the Orm: prefix.

Scope What it controls
Outreach:FullAccess Full access to the Outreach module.
Outreach:Limited Makes the Outreach module accessible.
Orm:QuickAdd:View Use the quick-add action.
Orm:Tasks:View View Outreach Tasks.
Orm:Contacts:View View Contacts.
Orm:Pipelines:View View Pipelines.
Orm:Groups:View View Groups.
Orm:Clients:View View Clients.
Orm:Organizations:View View Organizations.
Orm:Deleted:View View the Deleted page (recently removed Outreach records).

Reports Module

Scope What it controls
Reports:FullAccess Full access to the Reports module.
Reports:Limited Makes the Reports module accessible.
Reports:List:View View the list of available reports.
Reports:Attendance:View View the Attendance report.
Reports:Meals:View View the Meals report.
Reports:Members:View View the Members report.
Reports:Demographic:View View the Demographics report.
Reports:Billing:View View the Billing report.
Reports:Transportation:View View the Transportation report.

Billing Module

Scope What it controls
Billing:FullAccess Full access to the Billing module.
Billing:Limited Makes the Billing module accessible.
Billing:View View and use the Billing page.
Billing:Dashboard:View View the Billing Dashboard.

Center Module

Scope What it controls
Center:FullAccess Full access to the Center module.
Center:Limited Makes the Center module accessible.
Center:User:View Allows viewing users who have access to the center and their permissions.
Center:User:Invite Allows inviting new users to access the center and assigning their permissions.
Center:User:Edit Allows editing existing users' access to the center and managing their permissions.
Center:User:Delete Allows removing users' access to the center.
Center:ConnectUser:View Allows viewing Connect users who have member access at the center.
Center:ConnectUser:Invite Allows inviting Connect users to access center members.
Center:ConnectUser:Edit Allows editing Connect users' member access at the center.
Center:Contents:View View center Contents.
Center:Contents:Edit Edit center Contents.
Center:Setup:View View the center Setup page.

Task Roles

Task Roles are a separate mechanism from scopes. They control which care tasks a user is responsible for and can see, without changing the rest of their permissions. A user can have any number of task roles.

Task role setting Effect
Default (no task roles assigned) The user has access to all tasks.
All The user has access to everything (every task role).
One or more specific roles The user has access only to tasks that match at least one of their assigned roles.

When a task requires certain roles, a user needs at least one matching role to act on it. If a task requires no roles, everyone can act on it. This lets you route tasks (for example, medication tasks to nurses) without altering module or page permissions.


Tips

  • Prefer the smallest access that fits the job. Grant granular scopes for what a role actually needs; reserve FullAccess for administrators.
  • Module missing for a user? They need at least {Module}:FullAccess or {Module}:Limited for that module to appear.
  • Page hidden inside a module? Check for the specific page scope (for example, CareIncidents:View for Incidents).
  • Use Task Roles for task routing, not for hiding pages — page visibility is controlled by scopes.

Troubleshooting

Problem Solution
A user cannot see a module Grant {Module}:FullAccess or {Module}:Limited for that module (and confirm the module's feature is enabled for the center, where applicable).
A user cannot see a page inside a module Grant the page's scope, such as Care:Members, CareGoals:View (Service Plans), or CareAssessmentTemplatesPage:View (Form Templates).
A user cannot edit a member section they can see :View grants read access only. Grant the corresponding :Edit scope (for example, Care:MemberEdit:Demographics:Edit).
A user cannot manage other users Grant the appropriate Center:User:* scopes (View, Invite, Edit, Delete).
A user sees the wrong set of tasks Review their Task Roles — Default means all tasks, and specific roles limit them to matching tasks.