General
Permissions in Gilli are determined based on roles, teams, and alert groups. The administrator assigns each user:
- a role – what kind of permissions the user has (what they can do)
- teams – whose customer information they are allowed to see
- alert groups – which AI-generated alerts you see
The combination of role, team, and alert groups determines what you see and what you can do in Gilli.
Roles
A role is a named collection of permissions. One role can include dozens of permissions related to different views and functions.
| Role (example) | Example permissions |
|---|---|
| Caregiver | Customer, alert, and logging views; alert acknowledgment. |
| Supervisor | In addition to the above, Statistics and team-level reports. |
| Doctor / Pharmacist | Diagnoses, medication, laboratory results. |
| Administrator | Administrator view: users, teams, integrations, organization settings. |
| Care and Service Needs Assessor | Creating assessments and plans. |
Individual Permissions and Roles
- Individual permission – e.g., View customer change log, Acknowledge alert, User management.
- Role – a set of permissions (e.g., "Caregiver").
Teams
A team is a group of users and customers that usually corresponds to a single work unit, such as home care in one area or a specialty.
- A user can belong to multiple teams simultaneously.
- A customer can belong to multiple teams (e.g., multidisciplinary care).
- Teams limit whose customer information you can see.
Alert Groups
Alert groups are selected lists of AI-generated alerts shown to the user. Users can have different alert groups based on their job description. For example, a physical therapist may have the same roles and teams as a home care worker, but their alert group focuses only on alerts related to these customers' physical functional capacity and its changes.
Where Can I See My Permissions?
- Open your own profile.
- Your profile shows:
- Alert groups
- teams you belong to
Administrator Tasks
The administrator manages roles, alert groups, and teams:
- Roles – creating new roles and setting permissions.
- Teams – creating teams and adding members, if this information is not provided by the source system.
- Users – assigning roles, teams, and alert groups to users.
Best Practices
- Principle of least privilege. Give the user only the permissions they need for their job.
- Roles, not individual permissions. Design permissions for roles, not for individual users.
Common Situations
"I don’t see the function I need"
The function requires a permission that is not included in your role. Ask the administrator to either add the permission to your role or create a new appropriate role.
"The customer does not appear on the list"
The customer does not belong to any of your teams. Ask the administrator to check the team assignment.
"My role has too many permissions"
Notify the administrator.